Intent
Name the change, proof, decision, or understanding requested. Do not substitute an easier adjacent task.
Operating discipline
Alpha Omega Sequencing (AOS).
Evidence before settlement. Alpha Omega Sequencing (AOS) binds authority, challenges the working claim and preserves the proof required to settle current state.
One reconstructible sequence
AOS is a procedure. The repository that owns the system retains product and control-plane authority.
- Intent
- Authority
- Source
- Falsifier
- Execution
- Verification
- Settlement
- Receipt
What customers can expect
Material claims begin with a named authority, exact source and evidence that could prove the conclusion wrong.
Implementation and verification remain separate states. Deployment claims require deployment evidence in addition to successful test evidence.
Settlement preserves what changed, what passed, what remains unresolved and what would reopen the work.
WHAT EACH STEP BINDS
The sequence is reconstructible after the work ends.
AOS is a procedure used across Mediator work. This page states the public meaning of each step. Product and control-plane authority stay with the repository that owns the system.
Authority
Bind the owner that may change or claim the target. A skill grants procedure. It does not take jurisdiction from the owning repository.
Source
Bind the current source, version, and observation time. Old status and model memory do not outrank current owner source.
Falsifier
State what would make the working claim wrong, then look for that evidence before treating the claim as settled.
Execution
Do the authorized work on the real path. Documentation is not implementation. A commit is not a deployment.
Verification
Re-run the proving step. Keep implementation evidence separate from deployment evidence.
Settlement
Record what changed, what passed, what remains unresolved, and what would reopen the work.
Receipt
Leave enough evidence that another reviewer can reconstruct why the result exists.
WHY THE SEQUENCE EXISTS
Each binding closes a specific way work goes wrong.
The sequence is not ceremony. Every step exists because its absence has a known, recurring failure — the kind that produces a confident result nobody can defend later.
Without intent, scope drifts
Work slides to an easier adjacent task than the one asked for, and the result answers a question nobody posed.
Without authority, no one owns it
A change or a claim is made with no bound owner, so when it is questioned there is no answerable party and no jurisdiction behind it.
Without source, memory outranks truth
Stale status or a model’s recollection stands in for the current owner’s source, and the work settles on a world that no longer exists.
Without a falsifier, a claim is never tested
Nothing is stated that would make the working claim wrong, so it is accepted because it was asserted confidently rather than because it survived a check.
Without execution on the real path, documentation substitutes for work
A commit is treated as a deployment and a description as an implementation, and the gap surfaces only when it fails in use.
Without separated verification, committed is read as proven
Successful test evidence is taken as deployment evidence, collapsing distinct states into one and hiding what has not actually been shown.
Without settlement and receipt, the result cannot be reconstructed
What changed, what passed and what remains open is not recorded, so no later reviewer can say why the result exists or what would reopen it.