Technical documentation for the services around the IHNYC Resident Council: what runs, how information moves, where trust boundaries sit, and how each product is maintained.
Explore the platform
| Area | What it covers | Start here |
|---|---|---|
| System architecture | Products, runtimes, dependencies, and service boundaries | System overview |
| Products and services | Public surfaces, operator tools, and implementation notes | Service directory |
| APIs and data | Routes, response contracts, storage, and integrations | API contracts |
| Security and access | Authentication, authorization, secrets, and recovery paths | Security model |
| Operations | Deployment, health checks, troubleshooting, and recovery | Choose a service |
| Decisions and current state | Verified repository coverage and point-in-time design records | Documentation audit |
Platform map
flowchart LR PEOPLE["Residents and guests"] --> LANDING["Resident Council website"] LANDING --> CAL["Programs calendar"] LANDING --> VOTE["Voting"] LANDING --> GAMES["IHNYC Games"] LANDING --> PUB["I-House Pub"] OPS["Authorized operators"] --> CONSOLE["RC Console"] OPS --> ADMIN["Service admin surfaces"] CONSOLE --> LANDING CONSOLE --> CAL PUB -.- BOUNDARY["Separate repository, access, and deployment"]
The services are independently deployed. A failure in one product does not imply that the rest of the platform is unavailable.
Products
| Product | Technical scope |
|---|---|
| Resident Council website | Public content, council data, support routes, and selected platform APIs |
| Programs calendar | Verified subscriptions, ICS generation, email delivery, and operator tooling |
| Resident voting | Elections, invitations, token validation, ballots, and published results |
| IHNYC Games | Events, signups, imports, results, and standings |
| I-House Pub | Public pages, displays, media systems, scheduling, and scoped administration |
Pub is a separate product
Pub code, planning, access, permissions, and deployment are independent from Resident Council systems. Its technical documentation remains here for shared search and maintenance. Equipment tutorials live on the Pub website.
Documentation structure
| Section | Use it for |
|---|---|
| Overview | System maps, current decisions, and service boundaries |
| Services | Product-specific concepts, operations, and reference |
| Platform reference | Shared API, route, security, and implementation conventions |
| About the docs | Page types, status labels, terminology, and contribution workflow |
| Legal and governance | Privacy, stewardship, terms, and organizational boundaries |
Scope and stewardship
These docs describe technology used around the IHNYC Resident Council ecosystem. The technical platform is operated by Affective Technologies LLC and is not affiliated with the Resident Council, International House NYC, or AVI Foodsystems. See Governance, IP, and Platform Stewardship.