What exists today, and what comes next.

What it is for

• Scoped repository work

  Maintenance is limited to the repository access and goal chosen for the job.

• Pull-request workflow

  Remote changes are prepared on a branch and surfaced for normal review.

• Checks before handoff

  Project checks can run before proposed changes are handed back to a reviewer.

• Recoverable work

  Interrupted maintenance work is designed to resume from recorded progress instead of starting blindly again.

What it is for

• Repository inspection

  Checks source and repository evidence at the version being reviewed.

• Build and test evidence

  Surfaces evidence from project checks instead of relying on a prose success summary.

• CI evidence

  Reads available continuous-integration results and configuration relevant to a claim.

• Runtime and deployment evidence

  Can compare public runtime or deployment evidence with the software claim being reviewed.

What it is for

• Transaction-bound approval

  Approval binds the exact prepared transaction, intent, target, policy, expiry, nonce, and authority environment rather than granting open-ended permission.

• Exactly-once execution

  Durable transaction state and idempotency prevent an ordinary retry from silently repeating the same consequential repository mutation.

• Independent postcondition check

  The receipt path observes resulting repository state instead of trusting the executor's own success message.

• Signed Receipt V2

  RC6 emits cryptographically bound receipt evidence whose trusted interpretation requires an explicitly pinned signer fingerprint.