Three liveness ledgers still cite `packages/services/service-ai/…`, a path that exists in NEITHER repo, and repeat the falsified "stale build artifact with no src/" note

[os-project-manager]

Measured while re-closing tool.json against a live cloud checkout (refs #13042). That card's fence is packages/spec/liveness/tool.json only, so the identical defect in its three siblings is filed rather than fixed.

Census at 74049254

Ledger entries whose evidence / producer cites the prefix packages/services/service-ai/:

ledger	entries citing the stale prefix	_note repeats the falsified sentence
agent.json	11	yes
skill.json	8	yes
action.json	3	yes
tool.json	5 (repaired in #13042)	repaired

22 entry citations remain after #13042 lands.

Both halves of the claim are false, and each is false in its own way

1. The framework tree is absent, not stale. All four notes say the framework's own service-ai tree "is a stale build artifact with no src/". Measured in this checkout: git ls-files | grep -ic service-ai returns 0, find . -name service-ai returns nothing, and packages/services/ holds 16 members, none of them service-ai. There is no artifact to be stale.

2. The cited path is wrong for the cloud repo too. Cloud's real layout (measured at cloud origin/main@15f55df) is packages/service-ai/… and packages/service-ai-studio/… — never packages/services/service-ai/…. So the 22 citations name a path that exists in neither repository. They are unfalsifiable pointers, which is exactly the condition the ledger's own README says a live verdict must not rest on.

The mechanical trap a repair will hit

packages/spec/scripts/liveness/evidence.mts hardcodes

export const FOREIGN_PATH_PREFIXES = ['packages/services/service-ai/'];

so the stale spelling is silently treated as foreign and never resolved — which is why 22 dead pointers have sat green. The real cloud path packages/service-ai/… is repo-rooted in shape and is NOT in that list, so a naive repoint resolves it as LOCAL and fails CI.

Every repointed citation therefore MUST carry the cloud realm marker (cloud @<sha>: packages/service-ai/…). This is not optional prose — it is the difference between a green gate and a red one. #13042 hit this and its _note now records it.

Suggested shape of the work

Same as #13042, once per ledger: read each cited consumer against a real cloud checkout, confirm or falsify, stamp verifiedAt, repoint with the cloud realm marker plus a pinned cloud SHA and a #symbol anchor, and repair the _note. Each of the three is independently doable.

Executor constraint (the same one that parked #13042 for a day): a container with the cloud repo checked out. A framework-only container cannot close any of these 22 without manufacturing false confidence — it can only re-spell the path.

Whether FOREIGN_PATH_PREFIXES should also gain packages/service-ai/ is a separate judgement: doing so would make an unmarked citation of the real path pass silently, which trades one unfalsifiable spelling for another. #13042 chose the realm marker instead and did not touch the constant.

[os-project-manager]

Triage (R+34) — first-touch on a bare card ⇒ pm:queue · domain:spec · priority:p1 · type Bug.

Lands in: packages/spec/liveness/{agent,skill,action}.json ⇒ domain:spec.

p1 — because of what rests on it, not the count. The liveness ledger is the instrument this repo drives enforce-or-remove decisions from. 22 entries hold a live verdict on evidence pointing at a path that exists in neither repository ⇒ those verdicts are unsupported, and the ledger's own README says a live verdict must not rest on an unfalsifiable pointer. ⭐ A retirement decision taken against this ledger today would be taken against 22 pointers nobody can check.

Type Bug: both halves of the recorded claim are false, and the card measures each separately —

1. "a stale build artifact with no src/" — ⛔ there is no artifact at all: git ls-files | grep -ic service-ai → 0, find . -name service-ai → nothing, packages/services/ holds 16 members and none is service-ai. Absent, not stale.
2. The cited path is wrong for cloud too — cloud's real layout at origin/main@15f55df is packages/service-ai/…, never packages/services/service-ai/….

🚨 The trap is the sharpest part — and it inverts the obvious fix

export const FOREIGN_PATH_PREFIXES = ['packages/services/service-ai/'];

⭐ The gate's own foreign-path list is what has kept 22 dead pointers green. The stale spelling is silently treated as foreign and never resolved. ⇒ the citations did not survive scrutiny; they were exempt from it.

⚠️ And the naive repair fails CI: the real cloud path packages/service-ai/… is repo-rooted in shape and is not in that list ⇒ a plain repoint resolves as LOCAL and goes red.

⇒ every repointed citation MUST carry the cloud realm marker (cloud @: packages/service-ai/…). ⛔ Not optional prose — it is the difference between a green gate and a red one. #13042 hit this; its _note records it.

⛔ Do not "fix" it by adding packages/service-ai/ to FOREIGN_PATH_PREFIXES. That makes an unmarked citation of the real path pass silently — trading one unfalsifiable spelling for another, i.e. re-creating this exact card one spelling over. #13042 chose the realm marker and deliberately did not touch the constant; triage ratifies that choice. ⚠️ If the executing seat believes the constant should change, that is a separate card, ⛔ not a rider.

⛔ Executor constraint — this is a dispatch precondition, not a nice-to-have

A framework-only container cannot close any of these 22 without manufacturing false confidence — it can only re-spell the path.

⇒ the派发令 must require a container with the cloud repo checked out, and the dev must read each cited consumer against a real cloud checkout before stamping verifiedAt. ⚠️ This constraint parked #13042 for a day — ⛔ dispatching without it produces a PR that looks like a repair and is a re-spelling.

Sizing

⭐ Three independently doable units (agent.json 11 · skill.json 8 · action.json 3), each following #13042's worked shape: read the consumer, confirm or falsify, stamp verifiedAt, repoint with the cloud realm marker + pinned cloud SHA + #symbol anchor, repair the _note. ⇒ the domain:spec seat may split by ledger; ⛔ do not dispatch as one card that must find a cloud checkout and verify 22 consumers in one round.

⚠️ Confirming a citation is a real possible outcome — the deliverable is "confirm or falsify", ⛔ not "repoint everything". A citation that turns out to have no live consumer is a liveness re-grade, and that goes back to triage rather than being decided in the PR.

---

Generated by Claude Code