CONSTITUTION STUDIO / FICTIONAL WORKSHEET
Your rules define what software may become.
Give the fictional Cedar Queue customer a constitution. Then challenge it with a proposal, scripted evidence and a fictional owner decision.
This is a local teaching example, not a production constitution compiler or a live Apex demonstration. It executes no policy or code, creates no real evidence or signatures, collects no customer data and grants no authority. Apex's complete constitutional evolution system remains a design direction.
ACTIVE CUSTOMER RULES / FICTION
The constitution stays above the proposal.
- Scope rule
- Only handler work may be considered.
- Prohibition rule
- No extra prohibition; scope restrictions still apply.
- Evidence rule
- Separate evaluation required. Baseline comparison required. A builder claim never substitutes for separate checks.
- Preservation rule
- Legitimate notifications must be preserved. Retry protection required by the current constitution.
- Owner rule
- Explicit fictional customer owner permission required before acceptance.
ILLUSTRATIVE DECISION / NOT APEX AUTHORITY
Permission, evidence, then acceptance.
Constitutional scope: Permitted in illustration
Independent example evaluation: Scripted retry, legitimate-notification and baseline examples pass.
Hold in illustration
Governing rule: Owner rule
The separate fictional evaluation is complete, but the customer owner has not permitted this example change.
Builder proposes. Separate evaluator / fictional supplies scripted examples. The fictional customer owner holds acceptance authority. Visitors control only this worksheet; no tests execute here.
Current proposal obligation: None retained from this proposal.
COMPOUNDING CONSTRAINT / FICTION
An accepted improvement would constrain what comes next.
Reach an accepted handler example. Carry its retry requirement forward, then consider removing the retry marker. The prior fictional requirement blocks that later proposal even if the current rule is weakened or the owner selects permission.
Prior fictional requirement: None carried. Accept a handler example before continuing.
The prior example constraint is separate from a new proposal's obligation. A refused new proposal adds nothing; reset clears both. This temporary page state is not real persistent memory or an actual recorded software floor.
Inspect the resulting decision ↑