Sequence · 08 of 08 · Event to team

A delayed flight becomes one draft, and a team, and a human decision

Three things are proved here: at-least-once delivery does not start two runs, delegation only narrows, and consequential output waits for a person. Every step carries the same task id, so the Flight recorder shows one story.

A delayed flight becomes one draft, and a team, and a human decision Sequence of a delayed-flight event on the Skyport broker: the trigger bridge starts exactly one responder run through Clearance, using a task id derived from the message so a redelivery is deduplicated; the responder spawns a narrower team, a spawn asking for more than its parent has is denied and audited, and the drafts go to a human for approval in Tower. DELAYED · MSG M-42OPEN_TRIGGERED(RESPONDER)SESSION S-1 (DEDUPED)ACKLAUNCH: AGENTRUN CLAIMRUN.SPAWN(TEAM, NARROWER)CHILD OK · BUDGET RESERVEDRUN.SPAWN(WORKER, WIDER)DENIED R007 · AUDITEDHUMAN.REQUEST(DRAFT NOTICES)APPROVAL REQUESTAPPROVEDskyport-brokerflights.eventsTrigger bridgean Airframe appClearancepolicy · auditResponder runthen the teamTowerapprovalsLEGENDCallReturnAsync messageHuman approvalGoverned gate

Principle honored

At-least-once delivery needs an idempotent consumer: task_id is a hash of (agent, message id), and the trigger bridge acks only after the audit record exists.

What changes

  • A storm brake (maxPerHour) bounds a flood of delayed events.
  • The denied spawn is a fixture, and the Preflight case asserts it was denied and audited.
  • Nothing is sent to a passenger: drafts wait for approval.

What is built

Built and tested: topic matching, the dedupe key, the rate limiter, idempotent open_triggered, the narrow-only spawn and its denial. Not built: the bridge consumer and Tower's approvals.

Hangar · Autopilot · plan