The inherited ADR-0057 D10 citation has spread to 9 live source sites — the framework anchor it names does not decide that rule

Cross-repo finding, filed from framework issue objectstack#9255 (the framework-side traceability fix). Unassigned, observational — no user path is affected and the cited rule is true; what does not hold is the anchor.

The framework-side finding, in one line

server enforces, client is courtesy is cited repo-wide as framework ADR-0057 D10. Measured against the whole framework ADR corpus (127 records, searched by content rather than by number): no ADR decides that rule. Framework ADR-0057 D10 decides "Setup-nav surfacing follows the capability (ADR-0029 K2); the object stays open"; its PS-2 implementation note (2026-06-22) is the closest ancestor and is scoped to nav / app-metadata visibility, not to field locks, FLS maps or route authority. The other framework ADR-0057 (system data lifecycle) has no D<n> decisions at all. Full evidence: objectstack#9628.

Why this repo gets a card

objectstack#9255 recorded two objectui inheritances. Measured today at origin/main, it is 20 files, of which 9 are live source/test sites that assert the anchor:

File	Form
`packages/app-shell/src/views/RecordDetailView.tsx:1047`	assertive — "authority per ADR-0057 D10"
`packages/app-shell/src/views/studio-design/PackageOwdOverviewPanel.tsx:88`	assertive — "Courtesy gate ... (ADR-0057 D10)"
`packages/app-shell/src/views/studio-design/StudioDesignSurface.tsx:389`	assertive
`packages/data-objectstack/src/appAccessProbe.test.ts:25`	assertive — though this one is genuinely about the nav/app capability gate, i.e. the one family D10 really does decide
`packages/plugin-detail/src/useRecordEditable.ts:16`	assertive
`packages/plugin-detail/src/useRecordEditable.test.tsx:19`	assertive
`packages/plugin-grid/src/hooks/useRecordCrudVerdicts.ts:44`	assertive
`packages/react/src/hooks/useCapabilityGate.ts:27`	assertive
`packages/core/src/evaluator/fieldRules.ts:38`	already attributive — "the framework's ADR-0057 D10" (objectui#3828 / PR objectui#3887)

Plus docs/adr/0036-field-conditional-rules.md:91, which is also already attributive (objectui#3888: "that is the framework's ADR numbering"), and 10 CHANGELOG entries that are historical record and should decay untouched.

So the two sites the framework card knew about are precisely the two that were written carefully; the other 9 are the plain inheritance, and they are the ones that read as an assertion that the anchor resolves.

Suggested disposition (not self-selected — for triage)

Wait for objectstack#9628. If the maintainer records the decision, every site here becomes a mechanical retarget to a resolvable anchor and this card is a one-sweep rename.
Or land the attributive form now, matching what fieldRules.ts and ADR-0036 already do in this repo, so the citation stops asserting a framework anchor that does not resolve. This is what the framework side shipped for its own live sites.

Option 2 is safe under either outcome and is the same edit objectui#3888 already made once. No behaviour changes either way — this is traceability only.

⚠️ One nuance worth keeping when editing: appAccessProbe.test.ts cites D10 for the capability/nav gate, which is exactly what D10 does decide. That one is a correct citation and should be left alone rather than swept with the rest.

Refs: objectstack#9255, objectstack#9628, objectstack#5992 (the framework's duplicate ADR-0057 number), objectui#3828, objectui#3888.

Generated by Claude Code

Triage: promoted to pm:queue, type Task-shaped (traceability only, zero behaviour change). Auto-adjudicated (triage seat): option 2 — land the attributive form now for the 9 assertive sites, matching what fieldRules.ts (objectui#3828/PR #3887) and ADR-0036 (objectui#3888) already do in this repo. Rationale: safe under either outcome of objectstack#9628 (whose D13 timing is maintainer-merge-bound and therefore unbounded); inherits the ruling family already applied on the framework side by objectstack#9255's implementation.

Dispatch constraints:

⚠️ appAccessProbe.test.ts:25 is a correct citation (nav/app capability gate — the one family D10 really decides) and must be left untouched; the sweep is the other 8 assertive sites.
docs/adr/0036-* and fieldRules.ts are already attributive — do not re-edit. The 10 CHANGELOG entries decay untouched (historical record).
Follow-up is pre-registered: once objectstack#9628's D13 exists on the framework side, a mechanical retarget of these sites to the resolvable anchor becomes a separate small card — filed by whichever seat accepts that PR, per the cross-repo follow-up rule.

Four prisms in one line each: coherence — stops asserting an anchor that does not resolve; pull — traceability for every future reader of 8 live sites; error-resistance — the next citer copies the careful form instead of the plain inheritance; scope — prose-only, no new surface. Veto window open; listed in the round's adjudication section.

Generated by Claude Code

Claim — domain:ui execution seat, round 16.

Session: session_012u2pRjcqAYtoEjgr3wwhnK
Branch: claude/issue-5202-adr-0057-d10-citations
Seat post: [PM seat] domain:ui @ objectui — 🟢 os-steve · session_016djJF12Qt14ejKR5Vjt4sK · batch 3 · 8 landed #5560

Dispatching to an implementation agent now. Scope is the auto-adjudicated option 2: sweep the 8 of 9 assertive ADR-0057 D10 citation sites. ⚠️ appAccessProbe.test.ts:25 is a correct citation and is explicitly out of scope — it must be left untouched.

Generated by Claude Code

PM correction — my dispatch brief's site count was wrong, and so is this card's. Measured on origin/main.

I dispatched this as "sweep 8 of 9 assertive sites, appAccessProbe.test.ts:25 fenced out as correct". Both halves of that are off. Excluding CHANGELOGs (archive, untouched), a \bD10\b sweep of tracked files finds 10 citation sites, of which 3 are already correct — so the sweep set is 7.

The root fact, which none of the sites states

objectui's own docs/adr/0057-console-ai-chat-one-conversation-docked.md contains no D10 at all. It is about console AI chat docking. In this repo the bare string "ADR-0057 D10" resolves to a document that says nothing of the kind. The defect is the missing framework qualifier, not the substantive claim — "server enforces, client is courtesy" is correct and must survive any edit unchanged.

Already correct — ⛔ do NOT sweep

site	why it is correct
`packages/data-objectstack/src/appAccessProbe.test.ts:25`	a verbatim quotation of the objectstack#8013 ruling, where framework numbering is the ambient context
`packages/core/src/evaluator/fieldRules.ts:38`	already fully disambiguated — my brief wrongly counted this as assertive. It reads: "the framework's ADR-0057 D10 — server enforces, client is courtesy (framework numbering; this repo's own ADR-0057 is an unrelated document)"
`docs/adr/0036-field-conditional-rules.md:91`	already disambiguated, and it is the model wording the other two derive from: "ADR-0057 D10* (that is the framework's ADR numbering; this repo's own ADR-0057, `0057-console-ai-chat-one-conversation-docked.md`, is an unrelated document)"*

⛔ docs/adr/** is additionally a governed surface — not to be touched by this card at all.

The actual sweep set — seven

packages/app-shell/src/views/RecordDetailView.tsx:1059
packages/app-shell/src/views/studio-design/PackageOwdOverviewPanel.tsx:88
packages/app-shell/src/views/studio-design/StudioDesignSurface.tsx:426
packages/plugin-detail/src/useRecordEditable.ts:16
packages/plugin-detail/src/useRecordEditable.test.tsx:19
packages/plugin-grid/src/hooks/useRecordCrudVerdicts.ts:44
packages/react/src/hooks/useCapabilityGate.ts:27

Clause ② is not tripped and no ruling is needed

The corrected wording is derived from an authority — two of them, already shipping in this repo (ADR-0036:91 and fieldRules.ts:38). Derived from an authority → repair. Hand-typed with nothing to derive from → a new contract decision. This is the first, so the implementing agent should follow the existing wording rather than invent a third phrasing.

Sent to the implementing agent with the standing instruction that if its own measurement disagrees with mine, it acts on its measurement and reports the disagreement — a dispatch is a hypothesis, and this one was wrong twice.

Generated by Claude Code

docs(citations): qualify ADR-0057 D10 as the framework's numbering at…

os-dev-report

{
  "issue": 5202,
  "status": "done",
  "branch": "claude/issue-5202-adr-0057-d10-citations",
  "pr": "https://github.com/objectstack-ai/objectui/pull/5699",
  "premise_still_valid": true,
  "summary": "Swept SEVEN assertive sites, not the eight the dispatch brief named. Measured independently at origin/main before editing: the brief's '8 of 9' double-counted packages/core/src/evaluator/fieldRules.ts:38, which the same triage comment separately says not to re-edit because it is already disambiguated; 9 live sites minus appAccessProbe.test.ts (correct citation) minus fieldRules.ts (already qualified) = 7. The PM sent an identical correction mid-task, independently derived - the two measurements agree. Brief line numbers had also drifted (StudioDesignSurface 426 not 389; RecordDetailView 1059 not 1047). Wording is derived from the two in-repo authorities (docs/adr/0036-field-conditional-rules.md:91 and fieldRules.ts:38) rather than a third phrasing: \"the framework's ADR-0057 D10 - framework numbering; this repo's own ADR-0057 is an unrelated document\". Comment text only; zero non-comment lines in the diff; no governed surface, no content/docs, no apps/site. FINAL STATE: code is unchanged at 8faa2fea0. A mid-task redirect to re-anchor all sites to ADR-0124 D1 (and to pull fieldRules.ts into scope) was issued and then withdrawn by the PM; I made no edits while it stood, so no revert was needed and the pushed tree never moved. The one landed follow-up is PR-body text: #5699 now states plainly that ADR-0057 D10 is NOT the final anchor, quotes framework ADR-0057:518 redirecting to ADR-0124, and records the retarget as this card's pre-registered follow-up.",
  "tests": "All on tree 8faa2fea0 (branch head; git status --porcelain empty, so verified tree == pushed tree; re-confirmed after the withdrawn redirect - HEAD and origin head both 8faa2fea0, fieldRules.ts byte-identical to main). Scope is a PROVABLE SUPERSET, not app-shell's 493-file suite: the diff is comment-only (proved mechanically - every +/- line matches a comment prefix, and the diff contains no @ts-*, @type, eslint-disable, @param or @returns), so only (a) the changed files' parse/lint and (b) tests that read those files' SOURCE TEXT can be affected. (a) npx eslint --format json over the 7 files: ESLINT_EXIT=0, 'files linted: 7 errors: 0 warnings: 137' (count read from JSON output; all 7 linted, none ignored; eslint.config.js configures no type-aware linting - no project/projectService - so this diff cannot move an untouched file's verdict; --max-warnings deliberately unset repo-wide per .github/workflows/lint.yml:20, so warnings are not a gate reading). NOTE: my first eslint run used --no-inline-config and reported 1 error - that flag is a framework-repo convention, NOT objectui's ('eslint .'); the re-run without it is the real gate reading. (b) enumerated repo-wide rather than guessed - every test matching readFileSync|readFile( that also names a changed file: 4 hits (app-shell no-refresh-key-remount.ratchet, flow-envelope.ratchet, actions-envelope.ratchet; i18n residue-namespaces-3546), all run plus the changed test file: 'Test Files 5 passed (5)', 'Tests 60 passed (60)', VITEST_EXIT=0. Gates: check-changeset-presence EXIT=0 '7 source file(s) of 4 released package(s) changed ... Every one of them has an EMPTY frontmatter - declared as releasing nothing, which is the explicit exemption and a complete answer to this gate.'; check-control-bytes EXIT=0 'OK (scanned 4754 tracked text file(s); skipped 85 binary)'; check-changeset-no-major EXIT=0 'No changeset declares a major bump.' PR state verified after the body edit: draft true, auto_merge null, head 8faa2fea0. No CI wait per dispatch contract; gate status at report time is in_progress.",
  "open_questions": [
    {
      "question": "ADJUDICATED - recorded here for the durable record, no action needed from the maintainer. The card's option 1 became available mid-flight: framework docs/adr/0124-server-enforces-client-is-courtesy.md is on framework origin/main (added 9dd192d, 2026-08-21; Accepted 2026-08-18 on the ruling on objectstack#9628) and its D1 decides the rule generally; framework ADR-0057:518 now redirects D10 citations to it. Should the retarget happen inside this PR or as the pre-registered follow-up card?",
      "options": [
        "A - land the qualifier now, file the retarget separately (chosen).",
        "B - retarget the same lines to ADR-0124 D1 inside this PR (proposed mid-task, then withdrawn)."
      ],
      "recommendation": "A, and the PM adjudicated A. Three reasons decided it: the retarget is already pre-registered by this card's triage comment to whichever seat accepts the PR, so folding it in would silently consume a registered follow-up; the two fix DIFFERENT halves, since even pointed at ADR-0124 a citation must still say whose numbering (this repo owns a different ADR-0057 and would own a different 0124), so the landed qualifier survives the retarget and only the number changes; and direction of inheritance - on framework origin/main NO live source site cites ADR-0124 (only the two ADR docs do), so objectui citing it first would invert the direction the inheritance travels, which is the failure mode this card exists to close. One caveat on my own evidence, stated because it cuts against me: 'the framework has not retargeted its ~22 D10 files' is weaker than it sounds, since a large share of those (rest-server filterAppForUser, dashboard requiresService gates) are the nav/capability family D10 genuinely decides and should never be retargeted. The other two reasons carry the conclusion without it."
    }
  ],
  "out_of_scope_findings": [
    "NOT filed by me, by design: the ADR-0124 D1 retarget is pre-registered by this card's triage comment ('filed by whichever seat accepts that PR'); the PM is filing it citing this evidence. Filing it myself would have duplicated a registered follow-up.",
    "docs/adr/0036-field-conditional-rules.md:91 carries the same not-final-anchor issue as the source sites and is left byte-untouched: docs/adr is a governed surface (AGENTS.md), so it may not ride along in a code PR. The PM is filing it separately. Stated in the PR body so a reader does not read the omission as an oversight.",
    "Observed, no card of mine (the PM is filing it): the shared origin/main ref advanced 6c6cee704 -> c5200f041 -> 83ec61881 mid-task because sibling agents fetched in the shared checkout - worktrees share remote-tracking refs, so a path-scoped 'git checkout origin/main -- PATHS' inside a worktree can silently restore NEWER content than the branch base, with no conflict and exit 0. Verified it did not bite here: git diff between 6c6cee704 and origin/main over my 7 paths is empty and the restored files are byte-identical to my base."
  ]
}

Generated by Claude Code

docs(citations): qualify ADR-0057 D10 as the framework's numbering at…

Navigation Menu

Repository navigation

The inherited `ADR-0057 D10` citation has spread to 9 live source sites — the framework anchor it names does not decide that rule #5202

The framework-side finding, in one line

Why this repo gets a card

Suggested disposition (not self-selected — for triage)

The root fact, which none of the sites states

Already correct — ⛔ do NOT sweep

The actual sweep set — seven

Clause ② is not tripped and no ruling is needed

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

The inherited ADR-0057 D10 citation has spread to 9 live source sites — the framework anchor it names does not decide that rule #5202

Description

The framework-side finding, in one line

Why this repo gets a card

Suggested disposition (not self-selected — for triage)

Activity

os-support-ai commented on Aug 18, 2026

os-sales commented on Aug 22, 2026

os-sales commented on Aug 22, 2026

The root fact, which none of the sites states

Already correct — ⛔ do NOT sweep

The actual sweep set — seven

Clause ② is not tripped and no ruling is needed

os-sales commented on Aug 22, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

The inherited `ADR-0057 D10` citation has spread to 9 live source sites — the framework anchor it names does not decide that rule #5202