Repository navigation
Closed
Copy link
Labels
needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.Human-in-the-loop required; autonomous sessions must not resolve items carrying this.
Description
Parent
Source: PLAN Phase 0, topic emil-kowalski-upstream-sync
Depends on
Outcome
An upstream change that is 90 to 100 percent clear reaches an agent without the owner, and only a change that needs a decision stops for them.
Demo: a drift issue for a clear change is admitted with no owner step, and a drift issue that needs a decision is held for the owner.
Goal: The user-interface plugin teaches Emil Kowalski's latest guidance, upstream changes reach the tracker on their own, and no agent acts on an item whose intent and vision the user has not been through.
- Intent (why, in the user's words): "If its 90-100% clear on what needs to be done/integrated... I'd rather not be involved"
- Vision (where this heads): The user-interface skills teach current, researched craft. Upstream changes reach the tracker on their own. Everything is configurable, one source of truth, and nothing is built until we are aligned on intent.
- When goals conflict, prefer: alignment over throughput
Decisions
- Q68: a separate ticket after the filer ships. Intake triage reads a drift issue's upstream diff as data and admits it when what to do is clear; anything needing a decision goes to the owner as
needs-human.Until this ships, every drift issue stays(superseded 2026-11-16, below)needs-human. - Q33:
drift issues carry(superseded 2026-11-16, below)needs-humantoday; this ticket narrows that for clear changes only. - 2026-11-16, owner, typed in the hub session (7b7eebe2): the blanket
needs-humanhold on drift issues comes off now, without waiting for the admission route or a plan approval. Verbatim, 15:26Z, standing direction section 10: "Holds that guard against our own actors (path holds, trust-path holds, person-approval holds, bot-author holds, pin/repin ceremony) are friction, not security boundaries, and come off now." At 18:20Z the owner typed "YOU DO THIS FOR ME:" above a pasted hub status list whose feat(upstream-drift): admit drift issues whose change is clear without the owner #14215 line, written by the hub, read "removing the hold the drift check puts on every issue it files". Earlier the same day (Q190 (a), "go w/ recommendations"), drift issues are re-audited by an agent with take, adapt or reject per change. A change needing a decision still stops for the owner: a take or adapt that would change a skill's design is filed as its ownneeds-humanissue and not applied (docs/contracts/upstream-drift/README.md, "One case goes to the owner"). That route now meets done-when item 3's intent; the filer's ownneeds-humanlabel is no longer the hold. Admission of drift issues to the issue lane (done-when items 1 and 2, the bot-author admission rule) stays open here. - 2026-11-16 19:2xZ, owner, typed in the hub session (278ecf3e), answering hub question Q195 "How should an issue the upstream-drift workflow files reach an agent?": "go w/ recommendations". Decision: option (a), which also counts as the owner-approved plan for done-when item 1. A trust rule scoped to the drift-issue shape, like PR feat(pr-pipeline): accept an upstream-drift issue as the spec of its own re-audit #16561's: author github-actions[bot] (id 41898282), the body never edited or edited only by that bot, the exact
Upstream drift:title, and the hex-pin lead line. It applies in.github/scripts/maintenance-audit-lane-runs/triage-sweep.mjs(the github-actions[bot] skip),.github/scripts/intake-triage/admit.mjscriteria 7 and 9, and the intake bot list in.github/workflows/intake-triage.yml. The resolve-issue spec for such an issue is built from a fixed template that reads none of the issue body. Rejected: (b) filing drift issues as the lanes App (adds an App token to the drift workflow); (c) a listed human files one issue naming the drift issues.
Key interfaces
None yet. This ticket goes through the full chain (interview, explore, research, design, plan, spec) before any build, because these are open:
- How triage judges "clear": a change that needs no reasoning or decision about what to take or reject.
- The admission rule that refuses bot-authored issues, and the fact that an issue opened with a workflow token starts no triage run. Loosening the rule for this one issue type is the owner's decision.
- How triage reads upstream text safely. Drift issue bodies hold only names, paths and hashes today, so triage has nothing to judge from.
- The merge limit: a review finding holds a merge only when it is a CRITICAL security finding, so a planted instruction blocks a merge only if the security lane rates it CRITICAL.
Done when
- The chain has run and the owner approved a plan for this route.
- A drift issue for a change needing no decision is admitted with no owner step.
- A drift issue for a change needing a decision carries
needs-humanand is not admitted.
Out of scope
- Which upstreams are watched, and the filer's issue format.
- Any change to how
docs/upstreamrecords are written.
Metadata
Metadata
Assignees
Labels
needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.Human-in-the-loop required; autonomous sessions must not resolve items carrying this.
Type
Fields
No fields configured for Feature.
Activity
fix(upstream-drift): strip a legacy needs-human when reopening a drif…
refactor(upstream-drift): drop a provenance comment on the reopen edit
feat(intake-triage): carry trusted drift issues through every author …
fix(work-unblock): unpark a trusted drift issue once its blocker closes