Each product is deployed independently and owns its runtime, storage, access rules, and release path.
Product directory
| Product | State | Runtime and storage | Documentation |
|---|---|---|---|
| Resident Council website | Active | Cloudflare Pages, Functions, R2 | Public content, council data, support routes, and selected APIs |
| RC Console | Active | Cloudflare Worker, D1 | Council identity, roles, handover, publishing, and service authorization |
| Programs calendar | Active | Cloudflare Pages, Functions, D1, R2 | Subscriptions, token handling, ICS generation, email, and administration |
| Resident voting | Active | Cloudflare Worker, D1, Durable Objects | Elections, invitations, ballots, results, and audit behavior |
| IHNYC Games | Active | Cloudflare Pages, Worker API, D1 | Events, signup imports, results, standings, and administration |
| I-House Pub | Active, separate product | Cloudflare Worker, D1, R2, KV, Durable Objects | Public pages, displays, media systems, scheduling, and scoped administration |
Concepts, operations, and reference
| Product | Concepts | Operations | Reference |
|---|---|---|---|
| Resident Council website | Content and data flows | Runbook | Routes |
| RC Console | Identity and access | Access recovery | API contracts |
| Programs calendar | Architecture | Runbook | API |
| Resident voting | Voting model | Runbook | API |
| IHNYC Games | Architecture | Admin surface | API |
| I-House Pub | Architecture | Runbook | API |
| Pub scheduling subsystem | State model | Current implementation | Admin surface |
Equipment tutorials
Instructions for the projector, sound, lighting, and other physical Pub equipment live on the Pub website. This site documents the software and system architecture around those surfaces.
Development and historical systems
| System | State | Documentation status |
|---|---|---|
| IHNYC Mobile App Shell | Development | The iOS wrapper exists; Android and public release procedures do not |
| IHNYC RC Gallery | Decommissioned | Retained as a technical and migration record |
Shared conventions
Within each active service, use:
explanation/for architecture and behavior;how-to/for operations and troubleshooting;reference/for APIs, schemas, and exact configuration;design-docs/andannouncements/for point-in-time decisions and shipped changes.
For contracts shared across multiple services, use the platform reference.