Repository navigation
docs(rfc): Preserve Autopilot incident evidence - #16146
Conversation
Retain the sanitized timeout and split-brain evidence after Autopilot retirement. Record the retirement as partial until StageBoundary cleanup lands, and link the remaining generic cancellation defect to issue kirodotdev#14058.
GPT 5.6 Review (fork) — ✅ no blocking findingsReviewed Review detailsNo findings. |
Design Review (Fable 5, fork) — ✅ PASSDesign-level review of Design-Verdict: PASS Verify the appendix's live claim — the four-hour turn ceiling still skipping native I spot-checked the committed facts: [DESIGN-REVIEWED] b9117f1 Description read[DESCRIPTION-READ] a565beb8f018b4542dc335505c275a45ffea5545a764b281b386651935f1c570 That sha256 names everything this verdict read: the PR description, plus the 1 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with |
Opus 5 Review (fork) — ✅ no blocking findingsReviewed |
iamwhatever
left a comment
There was a problem hiding this comment.
Reviewed: docs-only under docs/request-for-change/. The stage-budgets RFC lands as superseded with a matching superseded-by/supersedes pair, and the retire RFC moves accepted -> partial backed by merged #15362/#15359 and audited-at 6916ba1, so no new acceptance is claimed. Evidence appendix carries no prompts, paths, URLs or credentials. Nit: assets/README.md has two H1s; the second should be ##.
Problem / Motivation
Goal: Preserve the evidence from six Autopilot timeout incidents after the feature's retirement, without overstating how much cleanup has landed.
Autopilot's 30-minute stage timeout repeatedly told users that work had stopped while native ACP work continued. The user-visible mode has since been removed, but the incident record is not on
main, the generic cancellation defect remains open, and the retirement RFC still describes the pre-removal state.Why it matters
Two recovered incidents show concrete loss of control: one successful build result became unreachable from the dashboard, and another native turn began three source writes after the dashboard said the stage stopped. Preserving sanitized evidence keeps issue #14058 grounded in observed lifecycle failures without publishing raw transcripts or project content. Accurate RFC status also prevents maintainers from treating unfinished
StageBoundarycleanup as complete.Not a goal
What changed (motivation → approach → change)
rfc-autopilot-stage-budgets.mdassets/autopilot-stage-timeout-evidence.mdrfc-retire-chat-autopilot.mdpartialbecause step 3 still hasStageBoundary/_in_stage_executionreferences undersrc/.docs/request-for-change/README.mdassets/README.mdThe superseded RFC points the remaining generic four-hour turn-cancellation defect to issue #14058 and explicitly forbids restoring the retired mode. The retirement RFC links back to that historical record.
Backwards compatibility
Compatible: this changes documentation only and does not alter runtime behavior, persisted data, configuration, or public APIs.
Tests
python3.12 scripts/docs_lint.py --test./scripts/docs-lint.sh— 394 Markdown files scanned; all documentation checks passed.git diff --checkManual verification
Verified on
mainat6916ba17fthat #15362 and #15359 are merged, issue #14058 remains open, Autopilot's visible surfaces are absent, andStageBoundary/_in_stage_executionreferences remain in 16 files undersrc/. The appendix contains no raw transcript rows, local paths, prompts, tool arguments, or credentials.Screenshots / video
N/A — this PR changes RFC and evidence text only; it has no user-visible UI delta.
Related Issues
no linked issue: This PR preserves evidence and references #14058; it does not implement or close that runtime defect.
Supersedes #15987 and #14043.
Checklist
feat|fix|docs|style|refactor|perf|test|chore|ci|build|revert: ...)