HEAVY Authorization — Full Lifecycle

HEAVY Authorization — Full Lifecycle A sequence diagram generated by Archify. append REQUESTED row nothing may run await ruling GRANTED + initials DENIED read state dispatch HEAVY write results ingest result SPENT proceed w/o HEAVY read queue drain jobs Request PI ruling Execute / ingest Queue drain Agent · pipeline role · Sequence participant Agent pipeline role HEAVY Ledger · HEAVY ledger · Sequence participant HEAVY Ledger HEAVY ledger PI · only GRANT/DENY · Sequence participant PI only GRANT/DENY scheduler.py · reads ledger · Sequence participant scheduler.py reads ledger heavy_queue · orchestrate/state/ · Sequence participant heavy_queue orchestrate/state/ heavy_runner · SAS/ESAS · Sequence participant heavy_runner SAS/ESAS Cognition OS · heavy_inbox/ · Sequence participant Cognition OS heavy_inbox/ Idea · proposal artifact · Sequence participant Idea proposal artifact Legend request return security default message

PI-Only Ruling

  • • Only the PI edits the State column
  • • GRANTED is single-use and scope-bound
  • • Work outside scope is unauthorized even if idea matches
  • • A σ-only request expects DENIED

Request Contract

  • • Produces must name a sky quantity
  • • Cost column is mandatory
  • • Missing Produces or Cost → void request

Why This Gate Exists

  • • v1 ran 23 GB without merits review
  • • Every byte measured the pipeline's own error budget
  • • Terminal result: INCONCLUSIVE
  • • Gate makes PI judgment happen before compute

Queue Drain

  • • heavy_runner drains independently of tick
  • • No tick budget — 12h job timeout
  • • Products written outside worktree
  • • One runner process at a time