Every repository and capability the mandate names, with its constitutional status and the gate that would change it. Descriptions come from the repositories’ own READMEs; language and last push are read live from GitHub and omitted when GitHub cannot be reached.
The Operations OS the vertical applications are meant to sit on. Per the mandate it remains a platform hypothesis: identity, organizations, users, permissions, jobs, assets, documents, workflow engine, notifications, audit logs, integrations, AI tools, reporting and billing are extracted only after repeated customer evidence.
The web platform behind Ecowoods Hardwood Flooring Inc., a Toronto hardwood contractor operating since 2000: installation, refinishing, dust-free sanding, restoration, custom inlays and stair refinishing across the GTA. The repository is the single source of the facts every search engine, map service, directory and AI system resolves for this business; job management, quoting, invoicing and lead capture live in the same monorepo.
Marketing and pilot-waitlist site for an operating system for autonomous hardwood floor refinishing — early stage, pilot program forming. Hardware and software are in development; all specifications are design targets, pricing is indicative, and the ROI calculator is a transparent model with stated assumptions, not measured customer results.
Robotic wall-and-ceiling painting for contractors, positioned as a 2026 GTA pilot program on a robot-as-a-service model. The repository is the marketing site with a 3D simulator; the published figures — 4× crew output, ±2 mil thickness tolerance, 1,000+ sq ft per coat per day — are engineering targets for pilot units, not measurements.
Robot-assisted drywall finishing as a service — semi-autonomous taping, mudding and sanding supervised by trained operators, sold per finished square foot with no capex for contractors. Pre-launch, recruiting founding pilot partners in the GTA. The repository states plainly: no deployed robots, no customers, no certifications.
Enterprise platform for managing railway infrastructure and station-development projects across 14 technical departments (Fachbereiche), data-driven from a 1,298-project dataset, deployed as a static SPA. Typecheck, lint, tests and build are green end to end on main; the README records the measured state of the repository rather than an aspiration.
Named in the mandate as a related logistics repository. No public repository under this name was located in the inventory of 2026-09-05. Listed so the gap is visible, not filled with a guess.
Named in the mandate as a related capability. No dedicated public repository located on 2026-09-05. Asset and equipment tracking would be a Runway Fuel primitive (assets) if two customers ask for it.
Capability category named in the mandate. No dedicated repository; scheduling, dispatch and job documentation of this kind currently exist inside ecowoods-app. Field service is one of the six candidate wedges.
Capability category named in the mandate — the generalized form of what ecowoods-app does for one contractor. It does not exist as separate code and must not until the proving ground produces a second contractor.
Capability category named in the mandate. Dashboard capability currently exists inside bahn-project-manager (project portfolio, department reviews, station map) and in the labelled sample dashboards of the Forge sites.
This site. The control and integration surface of the Operations cluster: registry, KPI system, decision log, kill list, roadmap, weekly CEO report, cross-cluster contracts and the machine-readable index at /api/cluster/. It also carries the operator’s explainers and book manuscripts.
Machine-readable: /api/cluster/registry/. A status change is a registry edit plus a decision in the decision log; the CI guard checks that an ARCHIVE entry has a kill-list entry.