Fleet aggregator
fix(retraction): correct 13 earlier-this-session Correction callouts that were checked against a stale local branch — app-orchestration-command and os-orchestration are real on canonical origin/main (CommandCentre server + scaffold respectively), app-privategit-* license is genuinely AGPL, app-privategit-design's MCP endpoint is real; this session's local checkout diverges from canonical for these paths
@@ -17,7 +17,7 @@ short_description: "os-orchestration is the commercial-tier OS letting a single cites: [] --- **Correction (2026-08-02):** no crate named `os-orchestration` exists in the monorepo today. The real crate at this planned rename target is `os-interface` — a 4-file scaffold (`Cargo.toml`, `README.md`/`.es.md`, `src/lib.rs`) with no aggregation logic, and the rename itself has not been executed (per this archive's own `.agent/rules/project-registry.md`). This article's "PSP" (PointSav Protocol) binary-protocol claim, described below in unhedged present tense, has zero code footprint anywhere in the codebase — no crate, module, or string match for "PointSav Protocol"/"PSP" outside this article. Everything below should be read as the intended design for a not-yet-built system, not current capability. **Flagged, not resolved** — needs re-hedging to planned/intended language throughout, matching the discipline already applied to the `security/` category's unbuilt-feature findings. **Correction revised, 2026-08-02.** An earlier pass said "no crate named `os-orchestration` exists in the monorepo today" — checked against this archive's stale local branch. On canonical (`origin/main`), `os-orchestration/` is a real, registered crate (own `Cargo.toml`, `license = "FSL-1.1-ALv2"`), but its `src/lib.rs` is a 4-line placeholder ("SYSTEM EVENT: os-orchestration scaffold verified.") — no aggregation logic. The rename from `os-interface` is confirmed in-progress on canonical too (root `LICENSE`: "os-interface/ — interface module (renames to os-orchestration)"). The "PSP" (PointSav Protocol) claim remains confirmed fabricated — re-checked directly against `origin/main`, zero code footprint anywhere. Net effect: the substantive finding is unchanged (this article's described functionality isn't built) but "the crate doesn't exist" was the wrong framing — it exists as an empty scaffold, same as many other placeholder crates found this session. **Flagged, not resolved** — needs re-hedging to planned/intended language throughout. `os-orchestration` is the commercial-tier operating system that lets a single operator see, query, and command many [[totebox-archive|Totebox archives]] at once. Where [[console-os|`os-console`]] connects to one [[totebox-os|`os-totebox`]], `os-orchestration` is the hub between an operator's Console and a fleet of Toteboxes. It is what an executive views when they want the position of every property in a portfolio, every entity in a holding company, or every project in a development pipeline — a single unified answer to "what is the state of the entire estate, right now?" This article covers what `os-orchestration` does, what it deliberately does not do, how aggregation works, the commercial features it adds, and when to deploy it.