02 · Selected work

7ARCH governed delivery

A multi-agent operating system: authority lanes separate from model spend. ADE-F.T names the formalisation — it is not a SaaS binary.

Governance IP + operating method Protocol listing ≠ live router app Not an ADE-F.T SKU

“7ARCH is the operating system I run deliveries on — authority lanes separate from model spend. Cat 05 on AAAS is the public protocol listing; the Studio pack is how we actually gate work. ADE-F.T is the name for that formalisation, not a separate SaaS binary in this monorepo.”

What this is

Governed multi-agent delivery: three non-interchangeable routers (Studio authority, InfraDOME models, Marketing GTM), plus SOP, JSON, skills, HALT, and HITL. Not a single running process sold as a product.

What ADE-F.T is

Positioning / formalisation name for separate agent-authority roles and model/compute lanes. No adeft/ package, no SKU row, and no adeft.pages.dev string in the evidence tree used for this case.

Public surface

Cat 05 on aaas.ml-nightworx.io is a protocol/spec listing (url: null / empty live URL). Sell as governance IP and operating method — not as a live router application unless another repo proves it.

Do not confuse

Nocturne ADE is a visual design system. NTWX HQ/Runtime as a named product is not found in the evidence tree. Closest artefacts: Architecture Harness, Studio ops glass, Agentic Moat FastAPI.

Claimable architecture

Authority routing (Studio): locked roster — ATLAS, PROMETHEUS, SIENNA, CEDAR, ERIS, GENE, plus specialists. No model IDs on the Studio surface. Seat rules are surface-specific; the roster is not an invitation to invent a seventh Archer.

Model / cost routing (InfraDOME): archetype → primary / paid / local models and a cost hierarchy (open-weight first, paid Claude/GPT as fallback only).

ACCESS layer: LiteLLM for economics — key, model, fallbacks, timeout, retries, cache. Live only when APP_ENV=production. LiteLLM does not own offer or jurisdiction logic.

HALT / HITL: outbox stays DRAFT until approve. Commander gates on quotes, secrets, jurisdiction, and a 2+ Red compatibility override. Reflector ASTROX checks RAG ≥90%, white-label, provision dry-run, and sovereignty — then GO-LIVE ALLOWED or BLOCKED.

Layers documented as Harness / Loop / Graph. Surfaces: AAAS Cat 05 protocol, studio.ml-nightworx.io ops glass (static), Agentic Moat FastAPI (mocks unless production). Cloudflare glass convention: Pages / Worker / Cloud Run.

  • JSON routers + skills
  • Locked Studio roster
  • InfraDOME cost matrix
  • LiteLLM ACCESS
  • HITL outbox
  • ASTROX go-live gates
  • Cloudflare glass

Design decisions worth copying

  1. Split authority routing from model/cost routing.
  2. Locked Studio roster — no invented seats; surface-specific rules.
  3. HALT over guessing.
  4. HITL on irreversible commercial actions.
  5. LiteLLM = ACCESS / economics only.
  6. Pair is build-time QC, not production runtime.
  7. Hard Reflector go-live gates, including RAG ≥90%.
  8. Cat 05 commercial SKU is not the operator SOP pack — protocol versus operating system.

What this tree does not prove

  • ADE-F.T as an implemented product directory or SaaS SKU.
  • NTWX HQ / Runtime as a named product.
  • adeft.pages.dev (not in the evidence tree; do not cite from this case).
  • Production OpenRouter spend dashboards.
  • Live Cloud Run after documented HALT states.
  • That Pair / OSF agents are production runtime.

A one-line “client problem + retained role” for this programme is still an open note. Until that line exists, this page describes the operating system — not a named enterprise engagement.