Skip to main content

Operating in concept

No orchestrator recipe, no secrets file, no addresses. The cycle the product implements:

  1. Install a dedicated stack (on-prem). It stays in bootstrap: one primary host and the Architect.
  2. Interview. In the Conversation UI the Architect asks, proposes an org chart, emits a spec. The spec stays pending.
  3. Approve. A person with permission confirms. Approving does not provision; it enables deploy.
  4. Deploy. The gated arm — no published port — brings up the declared agents-host units and profiles. The Console does not claim “applied”: it checks how many hosts are alive.
  5. Commission. A human asks for work in the Conversation UI (pipeline, corpus query, assembly). They receive a deliverable with a seal and sources.
  6. Observe. Explore shows the live graph. Operate shows panels. The ontology catalog validates meaning.
  7. Retire one institution without tearing down the others.

Backups with restore proof, directed updates of concrete pieces, and an emergency switch per capability. Operational detail lives in the internal guide.