InstituteOS keeps operational knowledge in the private docs and library trees, then exports only public-safe slices into this static website. This page makes the interface explicit: authored public copy, sanitized public tables, exported graphs, public project pages, and the checks that block private material before publication.
Source Ownership
Private InstituteOS docs hold operating guidance, implementation notes, and verification records. The library tree holds registries for projects, policies, processes, communications, narratives, strategies, and graphs. The public website does not mirror those sources directly; it receives only authored public pages and exporter-produced public slices.
Export Boundary
All structured private-to-public data must pass through the InstituteOS website export pipeline or the public Open Source Map sync. The gate rejects contact details, direct private-platform destinations, private operational fields, raw task detail, nonpublic stewardship records, working documents, demos, recordings, and internal UI captures.
Best Public Interfaces
The site exposes the best public interface for each audience: curated pages for visitors, the resource directory for search and filtering, the Open Source Map for structured public rows, project pages for public project context, feeds for communications, and version metadata for provenance.
Release Checks
A public refresh is complete only after the sync/export checks, static build, internal-link check, site contract, static-security check, design-system check, and browser inspection pass. Generated root HTML is rebuilt from source, not hand-edited.