Signal factory.
Why should a repeated signal leave the factory asleep?
Why should a repeated signal leave the factory asleep?
Fit all five factory assemblies before processing work.
The gate remembers each request and revision. Repeats coalesce into the same work item, while new jobs wait in arrival order. A free desk starts work only when the fixed-hour budget allows a wake. Finished work waits for review, and the press sends only approved output to the main tray. The counter measures worker starts, so queueing and duplicates do not spend it.
Illustrative local event factory, not live GitHub, AI agents or a repository integration. Twenty-four identities are 12 request IDs × two revisions, treated as independent logical jobs. The dedup ledger lasts for the whole saved session. FIFO follows first arrival. A chosen fixed-hour policy admits at most 12 actual worker starts; queueing and duplicate signals use no wake. Next hour explicitly resets only this counter. Three physical desks take at most the selected capacity; reducing capacity lets in-flight jobs finish before new admission. Two explicit work ticks complete a job; visual cycles are scaled to four seconds and do not change work state. Approval represents a human review and passing checks; integration is an explicit local operation. Authentication, payload validation, network retries, branch-head supersession, durable transactions and real provider limits are outside this model.
Integrate two distinct request/revision jobs and deliver at least one repeat signal without creating another wake.
Complete and integrate reviewed work within the hourly wake budget.