Each service is deployed independently and owns its runtime, storage, access rules, and release path.
Active Resident Council products
| Product | Runtime and storage | Documentation |
|---|---|---|
| Resident Council website | Cloudflare Pages, Functions, R2 | Public content, council data, support routes, and selected APIs |
| RC Console | Cloudflare Worker, D1 | Council roster, positions, terms, handover, and publishing |
| Resident voting | Cloudflare Worker, D1, Durable Objects | Elections, invitations, ballots, results, and audit behavior |
| IHNYC Games | Cloudflare Pages, Worker API, D1 | Events, signup imports, results, standings, and administration |
Concepts, operations, and reference
| Product | Concepts | Operations | Reference |
|---|---|---|---|
| Resident Council website | Content and data flows | Runbook | Routes |
| RC Console | Identity and council access | Access recovery | API contracts |
| Resident voting | Voting model | Runbook | API |
| IHNYC Games | Architecture | Admin surface | API |
Separately stewarded IHNYC products
| Product | Stewardship boundary | Canonical documentation |
|---|---|---|
| House Desk | Independent repository, Access application, roles, data, and release path | House Desk docs |
| Pub | Independent repository, Access application, roles, venue systems, and release path | Pub docs |
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 |
For contracts shared across Resident Council services, use the platform reference. For shared Affective Technologies identity, routing, and operator patterns, use the shared platform docs.