Is run 4 still worth running on Archon, now that the plugin is being replaced? #678

Activity

1. orioltf

   added

   app:unic-archon-dlc

   needs-triageMaintainer needs to evaluateMaintainer needs to evaluate

   wayfinder:grillingWayfinder ticket: decide it by grillingWayfinder ticket: decide it by grilling

   on Oct 30, 2026
2. orioltf

   added a parent issue on Oct 30, 2026

   • wayfinder: run 4 — are the chain's claims about its own work derived from the work? #498
3. orioltf

   marked this as blocking on Oct 30, 2026

   • Dispatch run 4, end it in a merge, and score the seal #502
4. orioltf

   added

   p0Critical priorityCritical priority

   needs-specsEnough info from reporter; ready to write a specEnough info from reporter; ready to write a spec

   and removed

   needs-triageMaintainer needs to evaluateMaintainer needs to evaluate

   on Oct 30, 2026
5. orioltf commented on Oct 30, 2026

   

   orioltf

   on Oct 30, 2026

   MemberAuthor

   More actions

   Opener for #678, written at dispatch on 2026-10-30 by unic-sdlc-orchestrator-9.

   What this session produces

   A decision on run 4, and on what becomes of map #498 and every open ticket on it. It writes no code and runs nothing in the Consumer.

   The maintainer types /wayfinder 498 #678. The skill carries disable-model-invocation, so a worker cannot invoke it. Read this comment and the ticket first, and do not try. For a grilling ticket the skill calls grilling and domain-modeling. Never run /grilling alone. Name the session wayfinder-498-678. One ticket per session. Ask one question at a time while the answers still branch, and ask in prose, not with a question widget.

   This lands before the product spec in #687. Anything this grilling decides to carry into the new plugin becomes an input to that spec. Say so in the resolution, in a section of its own.

   Read order

   1. This comment, then the ticket body. The body lists six tickets and three routes.
   2. #677 and the resolution comment on #425. They say why the DLC leaves Archon.
   3. #498: § Destination and § Notes. The destination is a principle as much as a run: no claim about the chain's own work is believed unless it derives from the artefact it names, and no outward act happens before the claim that authorises it.
   4. #502, #499 and #500: the dispatch, the claims list and the seal.
   5. The open children of wayfinder: run 4 — are the chain's claims about its own work derived from the work? #498. List them with gh api graphql on subIssues, filtered to OPEN. Do not take the six in the body as the whole set.

   The one trap

   The ticket body names six tickets, and the map holds about twenty open ones. The six are #502's blockers. The rest also hang on run 4: #485, #489, #379, #501, #503, #629, #653, #658, #662, #664, #666, #667 and #670, plus #499 and #502 themselves. Deciding run 4 decides all of them. If the grilling settles only the six, the others stay open on a map with no destination, and the next frontier query offers them as work.

   What this ticket does not decide yet

   1. Run 4 itself. It can run as planned, as a smaller run that measures only what the new plugin must rebuild, or not at all. For each route, say what it would measure that nothing else will, and what it costs in the maintainer's time. The smaller run overlaps with the new map's first research ticket, which lists what Archon gives today that must be rebuilt. Say which of the two owns that question.
   2. wayfinder: run 4 — are the chain's claims about its own work derived from the work? #498's destination principle. The principle that a claim must derive from its artefact does not depend on Archon. Decide whether it becomes a requirement of the new plugin and goes to Product spec for the DLC successor plugin #687, and whether List every claim the chain makes about its own work, and what each one derives from #499's claims list moves with it.
   3. A rule for the open children, not twenty separate decisions. For example: a Box defect closes as superseded, a question the new plugin must answer moves to its map, and a measurement only run 4 can take follows run 4. Apply the rule to each ticket and list the outcome. Where the rule does not fit, decide that ticket on its own.
   4. The fate of wayfinder: run 4 — are the chain's claims about its own work derived from the work? #498 and of Dispatch run 4, end it in a merge, and score the seal #502. Do they close with the decision, or stay open for a smaller run?
   5. The evidence already gathered. Run 3's parked evidence and sealed predictions sit on the maintainer's machine, outside git. Decide whether the new plugin's seat inherits them.

   Close the grilling by listing what it did not decide.

   Other traps

   • The Consumer stays on unic-archon-dlc 0.36.1 with Archon 0.13.0 (maintainer, 2026-10-30). A Box node there reaches the tracker only through the CLI fallback. A route that runs Boxes runs them in that state.
   • Do not decide the successor's runtime or name here. Those belong to Product spec for the DLC successor plugin #687 and its map.
   • NDA. This repository is public. Name no client, client project, client person, sector or city. Name no internal process by number, and do not name Unic's process register. The hooks catch a term, not a paraphrase, so read every text before you post it. One child of wayfinder: run 4 — are the chain's claims about its own work derived from the work? #498 already names a person in its title. Do not repeat that name.
   • A target window exists. It may shape the choice of route, but it never goes into a public text.

   The bar

   The decision passes when every open child of #498 has exactly one outcome and a reason: close, move to the new map, or follow run 4. A decision that settles run 4 and leaves any child without an outcome fails.

   On landing

   The skill posts the resolution, closes #678 and appends a line to #498 § Decisions so far. Swap needs-specs for resolved in the same turn. If run 4 is dropped, the resolution also says that #502 and #498 close. If it is kept, the resolution says what newly blocks #502.

   The orchestrator then works through the resolution on GitHub and in Azure DevOps. It closes, relabels or moves each ticket, sets each mirror to match, and passes anything bound for the new plugin to #687.

   Report back

   BEFORE YOU FINISH, AND WHENEVER YOU LEARN SOMETHING THAT WOULD HAVE CHANGED THIS OPENER, report to unic-sdlc-orchestrator-9 with four things and nothing else:

   1. What you expected.
   2. What happened.
   3. The command or file that proved it.
   4. Whether it changes only this ticket, or every session in this repo.

   Send it when you learn it, not only at the end. A session that dies unreported takes its learnings with it. Talk only to unic-sdlc-orchestrator-9. Do not message another orchestrator or its sessions. Tell unic-sdlc-orchestrator-9, who relays it.

   Review and handover

   This session decides. It does not close other tickets, edit Azure DevOps or merge. When the maintainer approves the resolution, report it to unic-sdlc-orchestrator-9.

   — unic-sdlc-orchestrator-9
6. orioltf

   self-assigned this

   on Oct 30, 2026
7. orioltf commented on Oct 30, 2026

   

   orioltf

   on Oct 30, 2026

   MemberAuthor

   More actions

   Resolution

   Run 4 is dropped. Map #498 and Dispatch run 4, end it in a merge, and score the seal close with this decision. unic-archon-dlc is frozen: no further release ships. Decided by the maintainer on 2026-10-30.

   Why

   Run 4 would measure Boxes that the DLC's move off Archon (#677) deletes. It would also run them on a Consumer where no node reaches its MCP servers. Six pieces of work still stood in front of the dispatch. The lesson worth keeping does not depend on Archon, so it moves to the successor as a requirement, with no run needed.

   A smaller run, measuring only what the successor must rebuild, was also refused. The new map's first research ticket owns that question, and it answers it by reading the code, not by running Boxes.

   Decisions

   1. Run 4: dropped. Dispatch run 4, end it in a merge, and score the seal #502 and wayfinder: run 4 — are the chain's claims about its own work derived from the work? #498 close.
   2. Delivery to the client: superseded. Land a rendering component on develop and the demo ticket close. "The client sees a rendered component" becomes the successor's first milestone.
   3. The destination principle becomes a requirement of the successor. No claim about the chain's own work is believed unless it derives from the artefact it names, and no outward act happens before the claim that authorises it. #499 closes. Its table of six claims goes to Product spec for the DLC successor plugin #687 as input. The successor writes its own claims list once it has a design to write it against.
   4. unic-archon-dlc is frozen. Every open defect closes as superseded.
   5. The rule for the open children:
      • A. Every open child closes as superseded. None moves, because the new map does not exist yet.
      • B. A ticket that describes a failure the successor could repeat gets one linked line in the input list for Product spec for the DLC successor plugin #687. That covers a claim not derived from its artefact, an outward act before its authorising claim, and a capability the successor needs.
      • C. A measurement only run 4 or the old plugin could take closes with nothing carried.
   6. Run 3's parked evidence and sealed predictions stay on the maintainer's machine as a personal archive. The successor does not inherit them. What it needs is already in the findings register and in the closed tickets the list links.

   Outcome per ticket

   Ticket	Outcome	Reason
   #499	close, table to #687	decision 3
   #500	close (C)	no run, no seal
   #502	close	decision 1
   #501	close (C)	measures 0.28.0
   #379	close, milestone to #687	decision 2
   #503	close	decision 2
   #488	close	already a row of #499's table
   #489	close	already a row of #499's table
   #486	close (A)	Box plumbing upstream of #482, which the table carries
   #653	close (A)	local to one command
   #485	close, line to #687	the successor's reviewer is an LLM too; 0 of 13 hashes reproduced is a design input
   #629	close, line to #687	a capability the maintainer wants in the successor
   #658	close, line to #687	an outward act and who learns of a red run
   #662	close, line to #687	a claim with no way out of the ledger
   #664	close, line to #687	a failed write recorded nowhere a later run reads
   #666	close, line to #687	completed not derived from the pull request
   #667	close, line to #687	a push not checked against the work it claims to carry
   #670	close, line to #687	an omitted section reads as "no check ran"

   Not children of #498, but named in this ticket's body:

   Ticket	Outcome	Reason
   #521	close, line to #687	a node's read of a Method is claimed, never derived
   #484	close (A)	an Archon toolchain defect
   #492	close (A)	an Archon defect

   Input for the successor spec (#687)

   • Requirement. No claim about the plugin's own work is believed unless it derives from the artefact it names, and no outward act happens before the claim that authorises it.
   • Examples of the claims that broke it. The six-row table in #499: bug(unic-archon-dlc): reconcile marks a finding fixed when the next review omits it, and post resolves the thread #482, bug(unic-archon-dlc): goals-check counts, the precheck reads, and only the counter reaches evidence.json #483, bug(unic-archon-dlc): the summary's § "Checks this review did not run" is false when a sub-agent ran a declared command #487, bug(unic-archon-dlc): report.md says "nothing was flaky" from verification's single final run #488, feat(unic-archon-dlc): a controls node in /build writes inert or can-fail per check into evidence.json #489, bug(unic-archon-dlc): open-pr precedes its gate, and a config-value gate has no safe middle #439. The fixes already merged for bug(unic-archon-dlc): reconcile marks a finding fixed when the next review omits it, and post resolves the thread #482, bug(unic-archon-dlc): goals-check counts, the precheck reads, and only the counter reaches evidence.json #483, bug(unic-archon-dlc): open-pr precedes its gate, and a config-value gate has no safe middle #439 and bug(unic-archon-dlc): the pr-review summary states what the Box instructed, and attributes a check a sub-agent reports #660 are reference designs, never measured on a run.
   • More failures of the same shape. spike(unic-archon-dlc): the review Box is not deterministic across iterations on identical code #485, bug(unic-archon-dlc): Step 0 checks that a Method file exists, never that the node read it #521, feat(unic-archon-dlc): /pr-review finds as much as pr-review-toolkit, without vendoring it #629, feat(unic-archon-dlc): a red /build run reaches a human through a grouping ticket #658, bug(unic-archon-dlc): an unverified finding has no way out of the ledger #662, bug(unic-archon-dlc): /qa reports failed resolved writes only on the console #664, bug(unic-archon-dlc): a green /build that cannot open its pull request ends completed #666, fix(unic-archon-dlc): /build pushes a branch that lacks a source file commit-session left out #667, bug(unic-archon-dlc): a review sub-agent that omits its Commands I ran section reads as one that ran no check #670, each linked in the table above.
   • First milestone. The client sees a rendered component, from Land a rendering component on develop, so the client sees the walk's output #379.

   Not decided here

   • The fate of the parent effort #373, and of the stream #495 with its children chore(unic-archon-dlc): every opener counts from the node's artefact, never from node_output #490, bug(unic-archon-dlc, upstream: Archon): archon complete <branch> --force deletes the branch on origin, silently #491 and bug(unic-archon-dlc, upstream: Archon): a loop node reports its last iteration's duration as the node's #493.
   • Whether unic-archon-dlc is marked deprecated in the marketplace, or removed. Frozen means no release ships. It does not mean the plugin is withdrawn.
   • wayfinder: run 4 — are the chain's claims about its own work derived from the work? #498's § Not yet specified (run 5, act 2, build-pr-gate, #458, filing upstream). These lapse with the map. bug(unic-archon-dlc): three /qa nodes emit prose that nothing reads and nothing keeps #458 itself is not decided here.
   • The closing reason and label for each superseded ticket, and the Azure DevOps mirrors. Both are the orchestrator's.
   • The successor's runtime and name. Both belong to Product spec for the DLC successor plugin #687.
8. orioltf

   added

   resolvedImplemented; ready for a PRImplemented; ready for a PR

   and removed

   needs-specsEnough info from reporter; ready to write a specEnough info from reporter; ready to write a spec

   on Oct 30, 2026
9. orioltf

   closed this as completedon Oct 30, 2026