SweeAIunreleased · TypeScript

The supervision layer for a fleet of agents — specified, not built.

The problem

A fleet produces a supervision problem long before it produces a scaling one. Ten concurrent runs generate more status than a person can read. The useful surface is not a dashboard — it is a ranked queue of the runs that genuinely need a human, arriving where a person already looks.

The one-way arrow

SweeAI is the product; Swee is the company. Under the product sits SweeOS, the orchestration layer. SweeOS hosts a harness and calls SweeTrust for enforcement. That second arrow points one way only, because a guard the guarded thing controls is not a guard.

Whose code is on the right

The orchestration layer is not built, so it has no API to print here. What is beside this is SweeTrust’s, because it is the half of the arrow that exists: a sink declares the tier each argument must reach, and SweeOS may call it. There is no method on it that widens what it requires.

What it does not do

There is no execution engine, and that is a decision rather than an omission — ADR-002 concluded it should be bought. The supervision client is designed through the skeleton plane and no further, and the adoption flow, which is the actual thesis, has not been started. The monorepo is private and nothing is on npm, so a visitor can verify none of this.

Specified · orchestration layer unbuilt · monorepo private, nothing published

Request

// SweeOS may CALL a sink. It owns no appetite.
const pay = makeSink({
  name:     'pay',
  requires: { to: 'verified' },
  mode:     'enforce',
  log, execute,
})

pay({ to: Sourced.fromChannel(iban, 'email') })

Response — the interesting branch

{
  ok: false,
  refusal: '⚠ pay refused: to requires
            verified but is
            UNTRUSTED (channel:email)',
  receipt: { decision: 'refused', … },
}

There is no widen(). An orchestrator that could raise its own required tier would be the thing it was built to constrain.

What SweeOS may and may not do

may call
a sink, and read whatever comes back
may host
the harness, the schedule, the glue
may not widen
no method raises a required tier
may not invert
SweeTrust imports only node:crypto

A dependency — and the arrow that must not exist

SweeOSorchestration · scheduling — NOT BUILTSweeHarnessthe resident harness it hostsSweeTrustmandate · gate · verifybuilt · independentmay askmay not reconfigureNO ARROW POINTS BACKSweeTrust never depends on SweeOS — that is what makes it a cageA dashed outline means specced, not shipped.The grammar makes unbuilt things visible so adiagram cannot overclaim by drawing them alike.Orchestration may ask whether an action ispermitted; it may not widen the answer. A guardthe guarded thing controls is not a guard.
The dashed outline is doing honest work. SweeOS is specced and not built, and the grammar makes that visible rather than a footnote. An architecture diagram that renders unbuilt things identically to shipped ones is how portfolios overclaim without lying in any single sentence. Hover any dotted term for its definition.