Monthly execution control with token-based closure, record-backed progression, and governed forward movement.
Each execution must move from pending to submitted to token issued. Payment alone does not authorize progression. Progression is granted only through closed execution records and issued tokens.
The client may submit execution artifacts, but progression remains locked until each execution record is reviewed and closed through token issuance.
First governed execution for the active monthly cycle. Client must submit the required action to begin recorded forward movement.
Second execution slot in the active cycle. Progress continues only by tokenized closure, not by assumed effort.
Third execution slot. Submission must include declared completion before token issuance becomes available.
Final execution slot for the cycle. Full progression eligibility requires closure of all four execution records.
Submitted artifacts are used as reference only. Token issuance represents client-declared completion of execution. The system records acknowledgement, not verification of real-world outcomes.
Payment does not equal progression. Subscription state and progression state are separate. PSEQ advances only through issued token records inside the active cycle.