SignalBox: the tracker is the state machine

SignalBox: the tracker is the state machine An architecture diagram generated by Archify. Operator · the trigger · Architecture component Operator the trigger Production tracker · the state machine · Architecture component · no queue Production tracker the state machine no queue standing service · polls every 45s · one box: service + release seam · single instance standing service polls every 45s single instance 12 watchers · fixed order · one box: service + release seam 12 watchers fixed order deploy seam · atomic activate · one box: service + release seam deploy seam atomic activate release pointer · what this box runs · one box: service + release seam release pointer what this box runs prompt revision · note + components · automatic steps, human gates prompt revision note + components panel compose · design + action · automatic steps, human gates panel compose design + action deterministic check · can only refuse · automatic steps, human gates · replaced a 38% model deterministic check can only refuse replaced a 38% model video generate · re-reads approval · automatic steps, human gates video generate re-reads approval episode cut · latest-approved · automatic steps, human gates episode cut latest-approved ComfyUI · workflow per stage · Architecture component ComfyUI workflow per stage provenance gate · recorded vs sent · Architecture component · reports, never blocks provenance gate recorded vs sent reports, never blocks Versions · at Pending Review · Architecture component Versions at Pending Review Note + status polled, not pushed runs 12 in order names the release atomic, with rollback note + prompt rebuilds revised prompt, requeued workflow template candidates parks, or leaves unapproved frames and clips mismatch posted as a Note published back, awaiting a person one box: service + release seam automatic steps, human gates Legend Backend Database Cloud Security External

The central decision

  • • The production tracker IS the state machine
  • • No queue, no job file, no second admin tool nobody opens
  • • Every arrow reads or writes a tracker field
  • • So the record of what ran lands where the production already looks

Every gate is a person

  • • A deterministic check can only REFUSE, never approve
  • • It parks the work and says why; the decision stays with a human
  • • The one step that costs GPU time re-reads the approval on the way in
  • • Nothing self-approves, and that is the product

Why it is auditable

  • • Provenance is written by the code that sent the prompt
  • • A mismatch is posted as a Note, and reports rather than blocks
  • • A vision QC gate measured 38% and was switched off, not tuned
  • • A canary is proven to trip before any clean result is believed