Spun out of #13003 by the domain:spec seat (session session_01LpRNHxWZgSUgVnFT9mQQo4) per ruling comment 5458356183 and ACCEPT 5458682782, so the anchor-adoption worklist can close honestly on the framework-reachable population. Dedup: targeted semantic search returned a populated 16-result set with no open card covering tool.json re-closure — no duplicate exists.
Why this is its own card
packages/spec/liveness/tool.json's six live entries all cite packages/services/service-ai/… — the closed cloud runtime. Measured during #13003 batch 2 (PR #13038): that directory does not exist in this repo's checkout at all (packages/services/ holds 16 members, none of them service-ai), and the evidence scanner classifies the prefix as foreign, so the file has zero local citations and zero anchorable pointers — the path#symbol grammar cannot reach it by design, and no batch running in a framework-only container can re-close it without manufacturing false confidence. All six entries are undated (verifiedAt absent) with no honest way to date them from here.
The work (needs a reader with the cloud repo checked out)
- Re-close each of the six entries against the cloud repo's actual service-ai code — read the consumer, confirm the claim, stamp
verifiedAt; where the gate's guidance applies, re-attribute with a realm marker or re-classify under ADR-0049 instead.
- Repair the file's
_note: it claims the framework's own service-ai tree "is a stale build artifact with no src/" — measured in batch 2, that tree is now absent outright, so the note is stale twice over.
The fix lands in this repo (the ledger file is packages/spec/liveness/tool.json), so the card lives here; the executor requirement is the cloud checkout, not a different landing repo. Routing suggestion for triage: domain:spec (the ledger is spec governance data); the dispatching seat must pick a container/dev with cloud repo access.
Refs: #13003 (worklist; batch-2 report documents the measurements) · PR #13038 (the batch that established the facts) · #12516 (anchor grammar).
Spun out of #13003 by the
domain:specseat (sessionsession_01LpRNHxWZgSUgVnFT9mQQo4) per ruling comment 5458356183 and ACCEPT 5458682782, so the anchor-adoption worklist can close honestly on the framework-reachable population. Dedup: targeted semantic search returned a populated 16-result set with no open card covering tool.json re-closure — no duplicate exists.Why this is its own card
packages/spec/liveness/tool.json's sixliveentries all citepackages/services/service-ai/…— the closed cloud runtime. Measured during #13003 batch 2 (PR #13038): that directory does not exist in this repo's checkout at all (packages/services/holds 16 members, none of themservice-ai), and the evidence scanner classifies the prefix as foreign, so the file has zero local citations and zero anchorable pointers — thepath#symbolgrammar cannot reach it by design, and no batch running in a framework-only container can re-close it without manufacturing false confidence. All six entries are undated (verifiedAtabsent) with no honest way to date them from here.The work (needs a reader with the cloud repo checked out)
verifiedAt; where the gate's guidance applies, re-attribute with a realm marker or re-classify under ADR-0049 instead._note: it claims the framework's own service-ai tree "is a stale build artifact with nosrc/" — measured in batch 2, that tree is now absent outright, so the note is stale twice over.The fix lands in this repo (the ledger file is
packages/spec/liveness/tool.json), so the card lives here; the executor requirement is the cloud checkout, not a different landing repo. Routing suggestion for triage:domain:spec(the ledger is spec governance data); the dispatching seat must pick a container/dev with cloud repo access.Refs: #13003 (worklist; batch-2 report documents the measurements) · PR #13038 (the batch that established the facts) · #12516 (anchor grammar).