Skip to content

docs(rfc): withdraw the conductor PR land-tracking RFC - #37608

Merged
iamwhatever merged 1 commit into
mainfrom
docs/withdraw-rfc-pr-land-tracking
Nov 15, 2026
Merged

iamwhatever merged 1 commit into
mainfrom
docs/withdraw-rfc-pr-land-tracking

Conversation

@iamwhatever

Copy link
Copy Markdown
Contributor

What

Mark docs/request-for-change/rfc-conductor-pr-land-tracking.md (merged by #36753) as withdrawn, and update its row in docs/request-for-change/README.md. Docs only; no code, no behavior change.

Why

#36753 recorded an accepted decision to:

  • keep a PR work item open until its pull request lands (a pr_checks bar stored as pr_merged, an awaiting_land read state);
  • have the work-ledger probe read every open PR item in one batched GraphQL PR-state probe per tick and wake the conductor on merged, closed, conflicting or red;
  • give a forced quiet-floor wake a bounded per-item digest of live gateway facts.

Its phase A code PR, #36914, was closed unmerged by the repository owner on 2026-11-14. The owner's ruling: "over-engineered; too specific to the PR type." Nothing from the RFC is built on main.

Leaving the document at status: accepted would tell future readers, agents, and the First Principles lane (which reads this field from the base branch as a product-shape decision) that this design is still agreed and waiting to be built. Someone could pick it up and implement it again. This PR makes the record match the ruling.

This mirrors #37170, which recorded the owner's withdrawal of the host_pressure parts of rfc-work-ledger-resource-pressure.md and of the person-wait release. The difference: those RFCs were only partly withdrawn, so they kept in-progress / implemented with a withdrawn note. This RFC is withdrawn in full.

Why a new status value

None of the six existing values in the README's Status vocabulary fits an RFC that was accepted and then dropped in full before implementation:

Value Why it does not fit
draft It was accepted, not merely proposed.
accepted / in-progress / partial / implemented Each says the design is agreed or being built. That is the misreading this PR removes.
superseded Requires superseded-by to name a replacement. Nothing replaces this one.

So this PR adds one row, withdrawn: accepted, then dropped before implementation, nothing replacing it, body kept for history. It is also added to the README's list of statuses that are not a decision for the First Principles lane (next to draft and superseded). No script or checker hard-codes the status list (checked scripts/, .github/, tests/), so nothing else changes.

Changes

Checks

  • ./scripts/docs-lint.sh: all documentation checks passed.
  • python3 scripts/docs_lint.py --test: self-test passed.

The repository owner ruled the PR-specific land-tracking machinery over-engineered and closed its phase A code PR #36914 unmerged. Mark rfc-conductor-pr-land-tracking.md withdrawn so it no longer reads as an accepted decision, and add a withdrawn row to the RFC status vocabulary. Docs only; no behavior change.
@iamwhatever
iamwhatever requested review from a team and KiroCrewCaptain as code owners November 15, 2026 13:31
@github-actions github-actions Bot added the readiness: checking Automated validation is still running label Nov 15, 2026
@github-actions

Copy link
Copy Markdown
Contributor

First Principles Review (Opus 5.5) — ⏭️ skipped

Revision 55a2398a2d027a43b225fd1f8506783e59f17c6d ships no reviewable capability (docs, tests or generated files only), so there is nothing to inventory. Does not block merge.

@github-actions

Copy link
Copy Markdown
Contributor

UX Review (Opus 5.5) — ⏭️ skipped

Revision 55a2398a2d027a43b225fd1f8506783e59f17c6d touches no user-facing surface (no changes under website/ or committed screenshots), so the UX review was skipped. Does not block merge.

@github-actions

Copy link
Copy Markdown
Contributor

Design Review (Opus 5.5) — ✅ PASS

Design-level review of 55a2398a2d027a43b225fd1f8506783e59f17c6d — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS does not.

Design-Verdict: PASS

Nothing blocks: this is a docs-only status change, and withdrawn falls outside the four decision statuses the First Principles prompt counts, so it already reads as a non-decision.

[DESIGN-REVIEWED] 55a2398

Description read

[DESCRIPTION-READ] 8ebf162fa15ab8e37b3d39f8b1761bdb6361270f94efb0b6099fe341174cfbe1

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 .github/scripts/pr-description-capture.sh over the same inputs; if it differs, the description or that evidence changed after this verdict was formed and any finding drawn from either is unproven.

@iamwhatever

Copy link
Copy Markdown
Contributor Author

RFC change to show the actual status of feature

@iamwhatever
iamwhatever merged commit fd4c0d3 into main Nov 15, 2026
38 of 40 checks passed
@iamwhatever
iamwhatever deleted the docs/withdraw-rfc-pr-land-tracking branch November 15, 2026 13:33
@github-actions

Copy link
Copy Markdown
Contributor

GPT 6.1 Review — ✅ no blocking findings

GPT 6.1 completed its review of 55a2398a2d027a43b225fd1f8506783e59f17c6d and found no blocking issues.

This comment is updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] 55a2398

False positive or not applicable? A repository writer can comment:
/ai-review override gpt 55a2398a2d027a43b225fd1f8506783e59f17c6d false-positive: <reason, 20 to 500 characters>

@github-actions

Copy link
Copy Markdown
Contributor

Opus 5.5 Review — ✅ no blocking findings

Reviewed 55a2398a2d027a43b225fd1f8506783e59f17c6d — this comment is updated in place on each push.

Review details

No findings.

[OPUS-REVIEWED] 55a2398

Verdict parsed from the review's SHA-scoped output markers for commit 55a2398a2d027a43b225fd1f8506783e59f17c6d.

False positive or not applicable? A repository writer can comment:
/ai-review override fable 55a2398a2d027a43b225fd1f8506783e59f17c6d false-positive: <reason, 20 to 500 characters>

@github-actions github-actions Bot removed the readiness: checking Automated validation is still running label Nov 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant