Studio Pulse Live turns selected work evidence into a bounded public-safe proposal. Signal Machine presents the exact proposal for approve or decline; Studio remains the durable producer and controls any accepted receiver attempt.
The recurring work
Useful public updates must be derived from authorized work evidence without exposing private activity, weakening the approval boundary, or allowing a temporary decision relay to become the publisher.
What the system handles
What remains human
Signal Machine is the temporary authorization relay. It records the exact choice but does not publish or call the website receiver; Studio Pulse Live owns durable history, execution state, and public verification.
Operating mode
Operating integration · evidence-bound public proof
Studio prepares a bounded proposal, Signal records the exact human decision, and only Studio can enter the separately commissioned one-attempt receiver path.
What has actually passed
Founder-built operating proof, not a customer case study.
The Signal decision view uses synthetic data in the real interface. The public result is read-only captured evidence, and the composed hero is explicitly a multi-surface evidence overview.
Current limitations
The running Studio process's exact source commit, the production receiver row, and the current website build identity were not observed. Raw images can remain during active or retryable work and are deleted after durable terminalization or explicit discard—not immediately.
Pattern this could support elsewhere
A human-authorization pattern for preparing narrow public or external actions while keeping decision evidence, execution ownership, and reconciliation in the durable producer.
START WITH THE WORK