[joemooney]

Dedicated autonomy and trust guides cover operator/guided/drive/drain, the separate decide stop, override limits, current-head review evidence, CI/holds and authority boundaries. The autonomy page reuses the landing selector. Corrected links reach the review process and locate the selector on the autonomy page. Claims were checked against current main including merged PR #3090.

Validation at author head 8f1027e26a0c4ed5ad9c509c05f21c90a0f433f1: make check-ci-fast completed all 35 gates successfully at this exact head. Guide output was rebuilt from its source and shared template; this change adds no runtime authority or deployment behavior. Author checks provide no independent approval or merge-hold clearance. Advisor review and bottom-up integration remain required.

[joemooney]

Review: PR-3099 @ a742a2c

Acceptance criterion	Status	Evidence
Four delivery choices map to operator/guided/drive/drain; decide is outside the ladder and can't be overridden; one-shot override claims match source/help	✅ verified	aida-core/src/models.rs:578-610 (variants and ladder rank), do_dispatch.rs:202-275 (classify_mode_override, human_contract), aida do --help (--mode is never persisted; loosening needs --force; decide can never be overridden)
Grants/mandates, exact-commit review, CI and holds, exceptions and limits; drain doesn't imply authority or deployment	✅ verified	aida mandate start --help (8h default, 24h max, TTY start/stop, operator-only never covered); GATE_PROTECTED_PATHS (.aida/config.toml, gate/); docs/review-process.md:237+ (solo-human self-approval); trust guide and SVG say a mode grants no authority and merge isn't deployment
Bounded selector reused, accessible original graphics, working cross-links	✅ verified	build.py copies the landing <section id="autonomy"> verbatim and adds app.js. ARIA tablist and keyboard handling come from app.js. trust.svg has role=img plus title/desc. All link targets exist. A rebuild in a temp copy reproduces all 5 generated pages byte-for-byte
Alpha/Linux, shared Unix user, harness differences, merge vs deployment stated; claims rechecked after the other lane lands	✅ verified	trust guide "Know the boundary". PR #3090 merged (5fbe1e3) and is an ancestor of this head, so claims were checked against the post-#3090 tree

CI: PR checks (merge-hold-gate) green, mergeStateStatus: CLEAN. The full Build workflow didn't run because the base is the stacked -108 branch. Ran make check-ci-fast locally: 35/35 gates passed (no cargo; docs-only).

Non-blocking notes

• The <img> alt for trust.svg is the generic "Trust diagram; details follow in the source guide" (build.py convention). The SVG's richer <desc> isn't exposed through <img>.
• The source links in autonomy.html/trust.html (../../aida-cli-lib/..., ../review-process.md) resolve in the repo but go outside the showcase root if docs/showcase/ is hosted on its own.

Verdict: Approved.

[joemooney]

Final-round author update at 8f1027e26a0c4ed5ad9c509c05f21c90a0f433f1.

Merged the final corrected predecessor and regenerated affected guide/library artifacts. No new slice-specific content edits; final approval/base-only attestation remains the advisor’s decision.

All lower-stack fixes are included by ordinary merges; no rebases or force pushes. These are author checks, with no independent-review or hold-clearance authority.

Validation: make check-ci-fast completed all 35 gates successfully at this exact head

[joemooney]

Included in PR-3103, which merged the approved stack 107-113 to main as one PR (advisor 11:35).