Promoted
Act
Bounded work survives its oracle and earns a scoped promotion decision.
Krucible contains the attempt, exposes it to real rejection authority, and preserves a record precise enough for a stranger to inspect what was promoted, refused, held, or quarantined.
Promotion is earned, narrow, and revocable.
One boundary. Four honest outcomes.
The product is separation: what may advance, what must stop, what still belongs to a human, and what cannot leave containment. Failure remains visible because a system that never refuses has not proved that its boundary works.
Promoted
Bounded work survives its oracle and earns a scoped promotion decision.
Rejected
An independent oracle catches the defect and the system gives authority back.
Human-gated
Policy, access, or ambiguity stays with an accountable person by design.
Quarantined
A dirty environment or unsafe attempt is preserved without entering the trusted lane.
How authority gets earned
Name the authority envelope, target world, mission class, budget, and prohibited actions before execution.
Compilers, tests, deployments, reviewers, and accountable humans get the power to say no.
Claims remain attached to attempts, evidence, costs, refusals, critics, and the world state that made them true.
Repeated proof widens a revocable lane. A later rejection can close it immediately.
What the first proof showed
In a synthetic Salesforce laboratory proof, Krucible kept three materially different outcomes separate. The claim is bounded to that demonstration—not generalized autonomy or production trust.
PROVED
The promoted result remained attached to its run, oracle evidence, and promotion decision.
PROVED
The rejection immediately revoked the earned automation lane instead of hiding the failure.
PROVED
Standing in one automation lane did not confer authority over security or policy.
The operating thesis