gnomonlearn
Docs/RDF projection review gaps

RDF projection review gaps

Versioned draft snapshot

RFCs, reference catalogs, and evidence reflect Spec 3b2e3e7a114fb826b1445d39a48756b8fff629cd. Counts and pending/status notes belong to that snapshot. Read the dated project update for later progress.

Source repositories are private during staging. Links marked “repository access required” need access to the linked repository.

This is a trace and gap record from the pinned draft specification. It does not establish proof or implementation conformance.

Current source-alignment summary (2026-10-17)

After the owner-approved RFC-0053 owner and index-policy adoption at baseline 8e20a7edc92e8c033aded8010542798245bb3d90, the ledger has 6,962 reviewed nodes, 4,703 matches, 2,259 mismatches, and zero unreviewed nodes. The actual combined adoption records 58 repaired references, four scoped literals, 47 source-review closures, and eight retained affected semantic holds. Its actual comparison preserves all 38 displayed query results and records five changed complete relations. The earlier RFC-0006 ClaimStatus adoption record retains the exact one-literal correction, owning review, unchanged query results, and passing available gates. These are source-alignment findings; they establish no new proof, runtime conformance, or release acceptance. The three RFC-0029 cache-contract holds and 715 citation mismatches remain open. The actual data-only source-owner refresh (repository access required) resolves the generated-reference hold: the unchanged pinned data emitter refreshed RFC-0029/0038/0041 reference catalogs from already-approved Lean data, with fresh Turtle retained in its evidence archive. It imports no Kernel or logical proof premises and establishes no proof, normative release, or published-framework adoption. Dated sections below retain their historical counts and scope.

Section relationship range audit (2026-10-03)

The domain ontology gives domain#assertedBy an rfc:NormativeStatement range and domain#appearsInSection an rfc:Section range. Twenty-three inherited domain nodes used assertedBy with an emitted section IRI. Their source projections now use appearsInSection with the same section target; the 19 existing source-bound reviews were refreshed. This changes one RDF predicate per node and preserves every subject and target IRI. The separate ModuleLifecycle section correction is recorded in RFC0005_LIFECYCLE_PROPOSAL.md.

tools/check_kg_links.py now enforces both ontology ranges against the regenerated RFC Turtle. It exposed 24 older appearsInSection links to subsection IRIs absent from the emitted RFCs: one in RFC-0018, one in RFC-0021, eleven in RFC-0023, and eleven in RFC-0036. The authored subsections exist, but the catalog emits their parent sections. The RFC-0018, RFC-0023, and RFC-0036 links now target those parent sections. The RFC-0021 input binding was linked to §3.1 even though its definition is in §5.1; it now targets emitted §5. These 24 subjects retain their IRIs and appearsInSection predicate; only target IRIs change. The local range and link gate passes. External RDF consumers still need review before release. The gate now checks that all 4,194 claims:derivedFromSection links target rfc:Section and all 2,584 domain:definedIn links target rfc:Document. Six claims:supportsRule links have a separate range mismatch documented in SUPPORTS_RULE_RANGE_PROPOSAL.md; that predicate awaits the owner choice before its range is made a release gate.

This is a chronological audit. Earlier sections record the verdict and RDF state at their respective checkpoints. Current source-alignment totals appear in the summary above.

Checked against regenerated RFC Turtle from the pinned Lean sources on 2026-10-01. Run python3 tools/check_lean_corpus.py --framework-root /path/to/fastverk-spec --out-dir generated/turtle, then python3 tools/check_kg_links.py --turtle-dir generated/turtle.

Historical section IRIClaim referencesReviewed target
https://gnomon.sh/rfc/RFC-0010#sec-82015 security claims → emitted sec-8a; five Knowledge Index claims → emitted sec-9b.
https://gnomon.sh/rfc/RFC-0010#sec-93Versioning and migration claims → emitted sec-10, matching authored §10.
https://gnomon.sh/rfc/RFC-0015#sec-82Draft bundle guard claims → emitted sec-11 Invariants, where the guard is restated in authored §11.
https://gnomon.sh/rfc/RFC-0036#sec-06Five platform alignment claims → emitted sec-1 Purpose, which adopts the alignment note; the two-table shape claim → emitted sec-4 Core Entity Types.

The 31 references were in checked-in kg/turtle-claims/RFC-*.ttl projections. The domain projection’s definedIn references all resolve. The original claim/domain projection generator and source rules were not present in the extracted spec tree.

The owner chose to update claim links to emitted sections. kg/claim-section-map.ttl records each old and new section IRI, and python3 tools/reconcile_claim_links.py --write applies the reviewed mapping to the protobuf source files and regenerates Turtle. Run without --write to check drift. The check also requires each mapped target’s generated section title to remain an authored top-level heading in that RFC. Claim subject IRIs remain stable; only derivedFromSection object IRIs change. The old target sections were absent from regenerated RFC catalogs, so no alias is claimed.

kg/proto/projection.proto now defines the source boundary for 55 claim and 55 domain projections. kg/source-claims/ and kg/source-domain/ were seeded from the inherited Turtle. python3 tools/check_projections.py --write deterministically emits the Turtle; without --write it fails on byte drift. The initial import preserved all original RDF triples except one correction: RFC-0006/sec-4/fqn-format had rdf:type :Identity even though the node’s claimKind was :Identity and every other claim node was typed :Claim. It is now typed :Claim. Subsequent owner-approved RFC-0035 ClaimStatus reconciliation changes the domain and claim projections further; CLAIM_STATUS_MIGRATION.md records that semantic diff. Serializer order alone accounts for other Turtle text changes.

Owner: spec. The technical projection regeneration and byte-drift gate are restored from a new protobuf source, but the original SPARQL rules are still unavailable. PROJECTION_CONSUMERS.md records the observed local consumers and measured query/count changes. Acceptance before normative release: review the seeded source facts against the current authored RFC sections and Lean catalogs, confirm the rdf:type correction and the 31 link changes with RDF consumers, and formally adopt the protobuf sources as the maintained authoring boundary or restore the original rules. The release gate remains red until that semantic and consumer review is complete.

RFC-0019 publish and registry invariants

The owner-approved publish sequence, dry-run boundary, and registry.scopes routing rules now have explicit Lean invariants and three corresponding domain invariant nodes. Their source-bound projection reviews match the authored RFC-0019 clauses and Lean summaries. The new RDF subjects add 15 domain triples. The ledger now has 499 of 6,948 nodes reviewed: 84 mismatches and 6,449 unreviewed. This source alignment does not establish CLI or resolver behavior or clear external RDF consumer review.

RFC-0000 §1 normative-keyword review

The five §1 claims for MUST, MUST NOT, SHOULD, SHOULD NOT, and MAY match the five definitions in narrative/rfc-0000.md §1. Each points to the emitted domain/invariant/normative-keywords node, and each derivedFromSection points to emitted RFC-0000#sec-1. The Lean catalog’s normative-keywords invariant enumerates the same five terms. No RDF fact or IRI change is needed for this reviewed slice. This review covers those five claims and their shared domain node only; it does not clear the remaining RFC-0000 projection facts or external consumer review.

Those six reviewed nodes now have source-bound verdicts in kg/projection-reviews.textproto. tools/check_projection_reviews.py binds each verdict to the exact protobuf node, authored RFC, and Lean catalog with SHA-256 hashes. The checker rejects stale or duplicate verdicts; CI runs it, and tools/check_release.py requires complete, matching reviews across 55 claim and 55 domain projection files. This ledger records semantic review of local sources; external RDF consumer review remains a separate release blocker.

RFC-0000 §2 canonical-term review

Eleven further claim nodes were compared against the authored §2 term table and the RFC-0000 Lean catalog. The first pass found three formal omissions: Command as a synonym for action, permission for implementations to extend EvidenceType registries, and a query’s composition of compute declarations. Lean normative statement b9 already prohibited query writes, but did not encode that separate composition fact. The RFC-0000 Lean catalog now has Command and Query terms and the missing EvidenceType clause; its reference catalog was regenerated from the pinned Lean framework. The 17 source-bound verdicts were re-reviewed against the changed Lean hash and now match. This establishes local source alignment, not runtime conformance or proof of the behavioral claims. Another 6,928 nodes remain unreviewed.

RFC-0000 §§3–5 structure review

Ten more projection nodes were checked against the authored RFC and Lean catalog. The precedence, framework-purpose, and Q&A companion facts align; the four framework-purpose claims are design statements, not verified runtime behavior. Two nodes abbreviate the seven mandatory RFC section titles: sec-5/required-rfc-sections uses Resolution rules, Failure modes, Security, and Compatibility in its claimValue, and the required-rfc-structure domain summary makes the same abbreviation. The authored §5 and Lean statement b0 spell out Resolution/evaluation rules, Failure modes and diagnostics, Security and authorization considerations, and Compatibility and migration. Lean’s separate invariant summary also uses the abbreviated forms. The two projection reviews are marked mismatched; the claim and domain IRIs remain unchanged. Correcting the literals would change RDF consumer-visible values. An in-memory comparison replacing only those two literals changed no result rows in the 16 checked-in claim queries; external queries and persisted values remain unverified. The proposed full wording is the authored §5 and Lean b0 wording quoted above. The ledger now has 27 reviewed nodes, two mismatches, and 6,918 unreviewed.

RFC-0000 §6 diagnostic review

Six more claim nodes align with the authored diagnostic policy and Lean catalog: major-version changes to code meaning, stable meanings across versions, legacy short-code aliases, allocation ownership, the runtime R prefix, and retired-code non-reuse. These are source-alignment verdicts, not evidence that compiler emitters implement the policy. The universal M format statement conflicts with the F, L, and R allocations in the same section, so the format and exception claims remain unreviewed pending the diagnostic namespace decision recorded in narrative/rfc-0000/QA.md. The ledger now has 33 reviewed nodes, two mismatches, and 6,912 unreviewed.

RFC-0000 §§7–8 closure and MCP review

Eleven claim nodes and five domain invariant nodes align with the authored closure and MCP clauses and their Lean catalog statements or summaries. The review covers authorization before mutation, agent authorization parity, diagnostic fidelity, deterministic operation ordering and MCP/CLI parity, resource paths, prompts, and forward-only rollback. These are source-alignment verdicts; they do not establish that a runtime or MCP server enforces the clauses. The ledger now has 49 reviewed nodes, two mismatches, and 6,896 unreviewed.

RFC-0000 §9 principal review

Thirteen claim nodes and two domain invariants align with the authored principal taxonomy and Lean terms or normative statements. This covers six principal trust labels and seven explicit escalation or taxonomy rules. The source review does not settle the open QA questions about a fixed Derived rank for MCP clients or System operations outside workflows; the RDF nodes for those disputed relationships remain unreviewed. It also does not prove that runtime authorization or audit logging enforces the authored rules. The ledger now has 64 reviewed nodes, two mismatches, and 6,881 unreviewed.

RFC-0000 §9.4 audit review

The six principal-specific audit claims and their shared domain invariant match the authored §9.4 table. The Lean catalog contains the audit-by-principal invariant and supporting evidence for several rows; its summary does not encode every field or the Runtime User policy granularity. These seven source-bound reviews establish that the projection represents the authored audit contract, not that runtime logging implements it. The ledger now has 71 reviewed nodes, two mismatches, and 6,874 unreviewed.

RFC-0000 principal taxonomy domain review

The six trust-capability nodes, seven principal-type nodes, reserved System actor declaration, and System workflow invariant align with the authored §2 and §9 taxonomy. The Lean catalog contains matching principal terms, the System actor term and workflow invariant, and selected trust-level evidence; it does not separately formalize every capability summary. These 15 reviews check source meaning only. They do not establish enforcement or audit behavior in the runtime. The ledger now has 86 reviewed nodes, two mismatches, and 6,859 unreviewed.

RFC-0000 canonical-term domain review

Fifteen domain type nodes had matching definitions in the authored §2 term table and the Lean term catalog. Their definedIn links were also checked against the RFC cross-references in §2, including Action type, Claim, FlowType, Kernel, and Storage manifest. This first slice brought the ledger to 101 reviewed nodes, two mismatches, and 6,844 unreviewed.

RFC-0000 canonical-term formal completion

Nine authored §2 terms that lacked Lean catalog entries now have term records: Module, Install plan, View, Aspect, Semantic facet, Presentation facet, Facet, Kind, and Principal. The RFC-0000 reference catalog was regenerated from the pinned framework, and all 55 Lean RFC modules compiled. Existing RFC-0000 review hashes were refreshed after checking that the Lean edit only added those terms and left the previously reviewed definitions intact. Five more domain type nodes and nine domain declaration nodes now have source-bound reviews covering their summaries and definedIn links. This does not prove runtime conformance or review the remaining RFC-0000 phase nodes. The ledger now has 115 reviewed nodes, two mismatches, and 6,830 unreviewed.

RFC-0000 phase ownership review

All seven RFC-0000 domain phase nodes (boot-time, build-time, compile-time, install-time, parse-time, runtime, and static-check) claim definedIn RFC-0000. Neither authored RFC-0000 nor its Lean catalog defines those phases. Each node is therefore reviewed as a source mismatch; the inherited RDF triples are unchanged. The corpus gives narrower leads: RFC-0040 §8 and RFC-0044 for build-time ingestion, RFC-0008 for parsing, RFC-0016 for static migration checks, and RFC-0005/0010 for install and runtime behavior. Those leads do not by themselves establish one canonical owner for each general phase. Before changing the seven definedIn triples, define the phase vocabulary in an authored RFC and Lean catalog, identify its consumer queries and persisted results, then regenerate and compare the RDF and site outputs. The ledger now has 122 reviewed nodes, nine mismatches, and 6,823 unreviewed.

RFC-0001 §§1–3 module-authoring review

The RFC-0001 Lean folder convention term used module.gnomon where the authored contract requires module.gnm. The Lean source was corrected and its reference catalog regenerated. Eleven claim nodes from §§1 and 3 were then reviewed against the authored prose and the corrected Lean catalog. They cover manifest identity, DSL syntax, folder discovery, explicit-listing scope, and five module invariants. The §1 ownership-boundary claim is supported by the prose and Lean’s RFC-0006 reference, though Lean has no separate rule for that boundary. These reviews establish source alignment, not parser or compiler behavior. The ledger now has 133 reviewed nodes, nine mismatches, and 6,812 unreviewed.

Inherited source-filename literal review

The filename projection inventory identifies 16 claim/domain nodes across nine RFCs whose text literals use .gnomon source filenames where their authored clauses use .gnm. All 16 have source-bound mismatch verdicts in the historical review at this point. The later correction and exact query comparison are recorded below and in FILENAME_PROJECTION_GAPS.md. External literal consumers remain unverified. At this historical checkpoint the ledger had 149 reviewed nodes, 25 mismatches, and 6,796 unreviewed.

RFC-0001 file and module-type domain review

Nineteen domain file nodes match the predefined filename table and special module.gnm, tests.gnm, and migrations.gnm rules in authored RFC-0001 §4. The module declaration and three module-type nodes also match §4 and the Lean module and module-type terms. Lean’s folder-convention term defines class-named discovery in general; it does not independently list every one of the 19 filenames. These 23 source-bound reviews do not establish compiler discovery behavior. The Governance file-class node containing policies.gnomon remains a documented mismatch. The ledger now has 172 reviewed nodes, 25 mismatches, and 6,773 unreviewed.

python3 tools/report_domain_links.py now keeps kg/domain-link-inventory.textproto synchronized with the checked-in claim and domain projections. The protobuf schema records the referring claim IRIs and same-tail emitted candidates for each missing target. Authored decisions in kg/domain-link-reviews.textproto are copied into the inventory only when the target is still absent and its complete referring-claim set matches the reviewed fingerprint. The report also checks that each review names an existing numbered section in its authored RFC. At this checkout, 1,111 claimSubject/claimObject links point to 518 domain IRIs with no emitted domain node. Of those target IRIs, 144 have an emitted node with the same case-insensitive final path segment. These are review candidates, not automatic aliases: a symbolic subject can legitimately have no domain projection node, and a shared final segment can name different concepts. The RFC-0006 ClaimStatus links were a reviewed example: four links used two absent IRIs and now target its emitted declaration. A second reviewed case is RFC-0020: two gnomon.subscribe claim subjects used a non-emitted operation IRI although the RFC defines the same API and the domain projection emits its named declaration. Those links now target https://gnomon.sh/domain/declaration/gnomon.subscribe. The same RFC’s seven SubscriptionHandle.pause, .resume, and .close claim subjects likewise describe the methods emitted as domain/field/SubscriptionHandle/{pause,resume,close}. Their links now target those three nodes. The method names and behavior were checked against the RFC’s handle API and each emitted field summary. The inventory is a source review queue and a CI drift gate. For each candidate, confirm the authored RFC meaning, Lean declaration, query behavior, and RDF consumer impact before changing an IRI. Retain intentional symbolic references with an explicit disposition rather than creating empty domain nodes to make the count vanish.

RFC-0000 §8’s six domain/module/mcp claim subjects now have an INTENTIONAL_SYMBOLIC disposition. The section and Lean catalog describe MCP as the machine interface for authoring and lifecycle operations; neither declares a Gnomon module named mcp. The domain projection instead emits the MCP contract’s invariants. These six claim IRIs and their RDF target remain unchanged. RFC-0046’s GNOMON_ENV and GNOMON_SECRETS_CACHE_TTL claim subjects are also reviewed as intentional symbolic references. The authored RFC names both as runtime environment variables, and the Lean catalog records their behavior; neither is a Gnomon declaration or an emitted domain node. Their historical /declaration/ IRIs and four referring claims remain unchanged. RFC-0017’s L0010, L0020, L0022, and L0030 claim targets are also reviewed as intentional symbolic diagnostic-code references. The authored LSP behavior and Lean diagnostic catalog identify all four codes; none is a domain decision declaration. RFC-0008’s Q3-draft-marker target names the design question resolved by the draft modifier, rather than a domain declaration. Its authored §11.2 and Lean catalog agree, while the domain projection separately emits the draft capability. These claim links remain unchanged. RFC-0029’s error.ignore, error.terminal, and error.transient claim subjects are also intentional symbolic references to the error classes in its §7 mapping table and §8 fallback, not emitted capability declarations. Their four claim links remain unchanged. The Lean catalog records the general mapping rule but does not enumerate the table rows or §8 fallback; that formal coverage gap remains open. These eleven reviewed targets leave 507 missing targets needing source review; external RDF consumer review remains open.

RFC-0047 AuditLogEntry candidate

RFC-0047 §3.1 declares AuditLogEntry as a structured record. Its Lean catalog source repeats that schema, and the domain projection emits https://gnomon.sh/domain/type/AuditLogEntry as a DataType with the same FQN. Six RFC-0047 claim links (five claimSubject, one claimObject) instead target absent https://gnomon.sh/domain/declaration/AuditLogEntry. The proposed correction points those six objects at the emitted type node; the claim subjects and prose stay unchanged. In a local in-memory RDF comparison, 15 of 16 checked-in claim query result sets were unchanged. The reservation-claims.rq row for reserved-for changed from an unbound FQN to AuditLogEntry; no row was added or removed. This comparison does not cover external RDF consumers or stored query results. The six source links remain unchanged pending the owner’s decision on this identity change.

RFC-0001 §4 manifest and import claims

Eleven more claim nodes were reviewed against the authored manifest and imports rules and the current Lean catalog. Nine match the source contract: module FQN identity, the single manifest declaration, import-key and semver forms, resolved-version lockfile recording, the manifest’s exclusion of inline declarations, required module type, circular-import rejection, and exclusion of other top-level declarations.

Two seeded nodes mismatch their sources. The M01065 empty-list warning applies to any present empty objects, operations, or agents list, but its RDF claimSubject identifies only objects. The imports-may-be-empty node is typed as a default value with defaults-to, although RFC-0001 §4 only permits the block to be empty or omitted when there are no upstream dependencies; it defines no defaulting operation. Their source-bound findings are in kg/projection-reviews.textproto. The exact triple proposal and local query comparison are in RFC0001_CLAIM_MODEL_PROPOSAL.md. The protobuf and emitted RDF remain unchanged pending correction and external consumer review. The ledger now has 183 reviewed nodes, 27 mismatches, and 6,762 unreviewed at that point.

RFC-0001 §4 agent and module-type claim review

Three additional claim nodes were compared with authored §4 and the Lean catalog. All three preserve part of the intended prose but misstate a consumer-visible RDF relationship:

  • agent-model-must-resolve attaches the model-resolution rule to the module agents file-list field. The authored and Lean rule applies to each agent declaration’s model reference.
  • ai-actor-requires-agent also attaches its rule to the agents file-list field. The authored and Lean M01054 trigger is an action declaration that names an AI actor without a resolvable agent.
  • backend-only-no-views forbids view and route, while authored §4 and Lean M01002 forbid composition and view. The view/route pair belongs to the separate ui-only M01003 requirement.

The source-bound ledger marks these mismatches without changing any RDF triples or IRIs. Repair requires choosing existing or new domain identities for the two declaration-level subjects, correcting the backend-only literals, then measuring local and external consumer effects before publishing. The ledger now has 186 reviewed nodes, 30 mismatches, and 6,759 unreviewed.

RFC-0001 §4 file taxonomy and folder-convention review

Twenty-one further claims were checked against authored §4 and the Lean catalog. Nineteen align at source level, including co-location and extraction, concept-folder cardinality and leaf layout, one-class-per-file, Governance subdivision, FQN inheritance, imports, manifest-first parsing, and conventional test and migration discovery. Source alignment does not prove the compiler enforces those rules.

Two nodes narrow a rule that the authored §4 applies to both Schema and Operations files. explicit-listing-naming-recommendation describes both file classes but points only at field/module/objects. forbidden-generic-filenames likewise attaches the six-name M08703 ban only to objects, although it applies to explicit-listing files generally. The ledger marks both as mismatched and leaves their RDF unchanged.

A counterfactual moving both claimSubject objects to the emitted declaration/module node changes three of 16 local claim-query result sets. cross-rfc-claims.rq changes the module row’s claim count from 36 to 38; exclusions.rq moves one row from module.objects to module; and implicit-conflicts.rq gains one heuristic row joining this filename rule with an unrelated RFC-0008 must-not-use claim on the broad module subject. That last row is not evidence of a normative conflict; it shows that the generic module subject may be too broad for this query. A dedicated explicit-listing file identity may be needed. The proposal and external consumer review must settle the subject before any RDF update.

The ledger now has 207 reviewed nodes, 32 mismatches, and 6,738 unreviewed.

RFC-0001 §5 validation-rule review

Nine §5 claims were checked against the authored validation rules and Lean catalog. Eight align at source level: backcompat intent values and deferred validation, required concept manifests, FQN identity and import matching, deferred policy-affecting detection, staged rollback checking, and semantic version validation. Source alignment does not establish compiler conformance.

path-must-resolve describes M01064 for every path in any present objects, operations, or agents list, as authored §5 rule 7 and Lean do. Its claimSubject is only field/module/objects, so an RDF consumer traversing subject identity sees an objects-only rule. The seeded RDF is unchanged. The correction must choose a subject that covers all three lists and measure local and external query effects before publication.

The ledger now has 216 reviewed nodes, 33 mismatches, and 6,729 unreviewed.

RFC-0001 §§6–9 diagnostics, security, and migration review

Thirteen further claims were checked against authored §§6–9 and the Lean catalog. Ten align at source level, covering MCP validation equivalence, authorization and policy rules, migration guidance, deprecation, legacy format handling, and M01070/M01071 behavior.

Three need reconciliation. The §6 diagnostic-shape claim includes a suggested fix when available, as the authored RFC does, but the Lean proposition and its justification list only severity, code, message, and source location. The MCP coercion claim includes the authored requirement to surface diagnostics for invalid directionality, mutability, or composition references, whereas its Lean proposition only prohibits silent coercion. Both Lean rules need their conditional consequence represented before the generated normative catalog can be treated as equivalent to authored §6.

The §9 diagnostic-allocation claim correctly states RFC-0001’s M01000–M01999 ownership, but its RDF claimSubject is domain/declaration/module. That assigns a specification-level namespace to module declarations. The correction needs an RFC or diagnostic-namespace identity and a review of local and external RDF consumers before changing the public subject triple.

The ledger now has 229 reviewed nodes, 36 mismatches, and 6,716 unreviewed.

RFC-0001 §4 remaining claim coverage

The ten remaining §4 claim nodes were checked against the authored manifest rules and Lean catalog. Eight align: module type values, objects path and declaration rules, list-order compilation, operations entry shape, and the rollback checkpoint and dependency rules.

Two lifecycle/diagnostic claims have subjects narrower than their text. rollback-hints-q2-vs-phase1 attaches a phase-split rule for both rollbackCheckpoint and rollbackDependsOn only to the checkpoint field. unrecognized-file-warning attaches M07902, which applies to unrecognized concept-folder files, to module.gnm itself. Their RDF triples remain unchanged. A shared rollback-hint identity and a concept-folder/file identity are candidate subjects; query and external consumer effects need measurement.

All 82 RFC-0001 claim nodes now have source-bound reviews. The ledger covers 239 of 6,945 projection nodes: 38 mismatches and 6,706 unreviewed (including 32 RFC-0001 domain nodes).

RFC-0001 domain projection and cross-RFC class taxonomy

All 32 previously unreviewed RFC-0001 domain nodes were checked against the authored RFC and its Lean catalog. Thirty align locally. Two summaries are wrong: field/action/backcompat calls the optional authoring intent a Phase-1 field, although §5 allows authors to set it in Q2 and defers only prior-version validation; invariant/exactly-one-module-declaration says “zero or more” produces M01060, which incorrectly includes the valid one-declaration case. Their source protobuf and emitted RDF remain unchanged pending semantic and consumer review.

The local file-class nodes reproduce RFC-0001 §4.1, but that section disagrees with RFC-0008 §4.1: RFC-0001 puts api and serve in Surface, while RFC-0008 puts them in Operations; RFC-0008 also adds aspect and model to Governance and separates Migrations, which RFC-0001’s table omits. RFC-0001’s Objects List mentions enum, while RFC-0008’s Schema class does not. The local source-bound verdict does not resolve these cross-RFC conflicts. See FILE_CLASS_CONTRACT_PROPOSAL.md for the contract decision and migration gate.

Every RFC-0001 claim and domain node is now source reviewed (82 claims, 56 domain). The ledger covers 271 of 6,945 nodes: 40 mismatches and 6,674 unreviewed elsewhere.

RFC-0002 §§1–4 bundle and metadata review

Twenty-seven RFC-0002 claim nodes were checked against authored §§1–4 and the Lean catalog. Twenty-five align with those local sources, covering the bundle goals, determinism and identity invariants, storage-manifest requirement, and the section-presence table. These source verdicts do not settle the reopened companion QA or prove compiler behavior; source hashes will invalidate them if the authored bundle contract changes.

Two §4 claim nodes overstate the source. diagnostics-required-may-be-empty uses defaults-to [], while §4 only permits an empty diagnostics array and does not define default insertion. source-fingerprint-derivation asserts a SHA-256 over concatenated raw file bytes, while §4 says only “SHA256 of all source files in lexicographic order” and leaves framing, paths, and exact algorithm unspecified. The latter also conflicts with the prior semantic-AST QA answer, now reopened in BUNDLE_CONTRACT_PROPOSAL.md. The seeded RDF triples remain unchanged pending a versioned fingerprint decision and consumer review.

The ledger now covers 298 of 6,945 nodes: 42 mismatches and 6,647 unreviewed.

RFC-0002 §§5–6 identity and generated-only rule review

Fifteen more RFC-0002 claims were checked. Four §5 identity claims align with the authored and Lean sources. required-identity-fields narrows a per-object requirement to the compiled-bundle subject, so its RDF relationship is still misleading.

The authored §6 only points readers to the generated diagnostics catalog. Eight section-linked claims about aspect merge, diagnostics, facets, and serialization add rules that appear in Lean but not in authored §6. They remain source mismatches pending a decision to author those rules in the RFC or remove the unsupported projections. The other two §6 claims enumerate reproducibility categories and M02150–M02154, which are actually authored in §11. The owner’s previously approved section-link policy applies: their stable claim IRIs now link to emitted §11. A local in-memory comparison of all 16 checked-in claim queries found no changed result sets for those two link moves; external query and stored-result effects remain unverified. The map now covers 33 reviewed section-link corrections, and the protobuf-backed Turtle was regenerated.

The ledger now covers 313 of 6,945 nodes: 51 mismatches and 6,632 unreviewed.

RFC-0002 §7 storage manifest review

Twenty-one §7 claim nodes were checked against the authored storage-manifest contract and Lean catalog. Twenty align with the local sources. The bitemporal-write-prohibition node has the right prose but an incorrect RDF relationship: its subject is the runtime-only invariant and its object is a compiled bundle, whereas §7.3 prohibits application code from writing valid_time or system_time directly. Correcting this relationship requires a consumer-aware RDF change; the source triple is retained for review.

The authored storage schema also needs a decision: §7.1 requires migration operations, and §7.2 defines a storage.migration identity, but the object_type enum omits migration and the normative §7.3 example provides no migration entry shape. This gap is tracked in the RFC companion QA and bundle contract proposal.

The ledger now covers 334 of 6,945 nodes: 52 mismatches and 6,611 unreviewed.

RFC-0002 §§8–11 security, compatibility, and diagnostics review

All twenty-one remaining RFC-0002 claim nodes were reviewed. Fourteen align with the authored sections and Lean catalog. Seven have prose close to the source but assign an RDF relationship to the wrong subject: §8 makes the policy envelope responsible for compiler behavior and uses it for all authorization artifacts; §9 makes BundleFormatVersion responsible for reader rejection and compatibility-mode lifetime; §10 makes the compiled bundle responsible for reproducibility reporting and its release discussion target, and describes the storage manifest rather than DDL generation as the reported item. These relationships need a coordinated model change and RDF consumer review. The M02165 §11 claim matches that section, while the authored §7.4 M02156 conflict remains open in the companion QA.

All 84 RFC-0002 claim nodes now have source-bound verdicts. Its 65 domain nodes have not yet been reviewed, so this is not a full RFC-0002 projection approval. The ledger covers 355 of 6,945 nodes: 59 mismatches and 6,590 unreviewed.

RFC-0002 domain node review

All 65 RFC-0002 domain nodes were checked against the authored RFC and Lean catalog. Fifty-three align with those local sources. Twelve need resolution:

  • Three envelope declarations (action, claim, and policy) have RDF kindClass: Composition, while the Lean bundle-section catalog classifies their plural section forms as Operations.
  • Five Diagnostic.* fields assert required or optional field shape absent from authored §4 and the §6 diagnostic pointer.
  • The aspect-merge and diagnostic-order invariants include detailed rules found in Lean but absent from authored §6.
  • The bitemporal invariant says all application writes violate M07630, dropping the authored §7.3 condition that the writes be direct and outside the Gnomon API.
  • The recreate invariant repeats §7.4’s M02156 warning, which conflicts with §11’s M02165 allocation for the same condition.

All 149 RFC-0002 claim and domain nodes now have source-bound verdicts. This does not approve the 31 mismatches or settle the open bundle schema questions. The ledger covers 420 of 6,945 nodes: 71 mismatches and 6,525 unreviewed.

RFC-0026 §3 mode-constraint relationship review

Ten §3 claim nodes were checked against the authored gRPC mode rules and Lean catalog. The general compile-time M26615 rule and the RFC-0020 stream integration link match their sources. Eight other nodes state a rule specific to unary, server-streaming, client-streaming, or bidi-streaming in claimText, but their RDF claimSubject is the generic operation.mode field. As RDF relationships, that makes operation.mode simultaneously require streaming and non-streaming return shapes and permits an unrestricted input schema alongside the one-Stream-field constraint. The source rules are conditional on the selected mode; the triples omit that condition. The source-bound ledger marks these eight relationships as mismatches while retaining the historical triples for consumer review.

An RDF correction should represent the selected mode as the subject or an explicit condition, retain the stable claim IRIs, and compare query results and external consumers before publication. All 18 RFC-0026 domain nodes were checked against the authored slot table, mode rules, status handling, TLS guard, and Lean catalog; their local source relationships match.

The remaining 48 claim nodes were reviewed against RFC-0026 §§1–2 and §§4–8. Five more RDF relationships lose the source’s subject or condition: rpc: and service: are required on each gRPC operation, while is-required-on points to the registering module; the api-key/basic interceptor fallback is conditional but requires targets the module generally; and the development-only permission and compiler warning apply to tls: none, while their RDF subjects are the generic client.tls field. The status taxonomy, remaining auth mappings, diagnostic phases, and scope exclusions align with their local sources. In total, all 76 RFC-0026 nodes have verdicts: 63 match and 13 have relationship mismatches. This does not establish implementation of those draft rules or approve the mismatched triples. At that review point, the ledger covered 496 of 6,945 nodes: 84 mismatches and 6,449 unreviewed. The exact candidate subject/object replacements, seven new domain identities, and sixteen-query counterfactual are in RFC0026_RDF_MODEL_PROPOSAL.md.

RFC-0020 subscription delivery and deduplication claims

The owner chose delivery within the scope fixed at open intersected with current grants, an explicit overflow exception, and deduplication only after callback acknowledgement. Authored RFC-0020 and its Lean catalog now agree. Three seeded claim nodes still used older, broader wording: §2 eventual delivery omitted effective scope and overflow; §4 at-least-once delivery was unconditional; and §4 deduplication did not distinguish acknowledged IDs from rejected attempts. Their claimText and claimValue literals were corrected in kg/source-claims/RFC-0020.textproto and the Turtle was regenerated. All three claim IRIs, subjects, predicates, and section links stayed stable; six literal triples changed. Source-bound reviews now match each node to the authored clause and Lean statement. This is local projection alignment, not evidence of runtime enforcement or external RDF consumer compatibility. Before release, compare stored/query consumers against the six literal changes and retain the prior preview for rollback. The current ledger covers 502 of 6,948 nodes: 84 mismatches and 6,446 unreviewed.

RFC-0020 scope and goal claims

The two §1 and six remaining §2 claim nodes now have source-bound matching reviews. The §1 relationships preserve the runtime-only syntax boundary and the cross-module read-scope exclusion. The §2 relationships preserve explicit overflow signaling, entity-local event order, observable lifecycle changes, the RFC-0007 query overlay, read-scope checks at open and delivery, and silent filtering outside that scope. Each was checked against the authored RFC and Lean catalog. No RDF fact or IRI changed. These eight reviews establish local source alignment only; they do not prove runtime enforcement. The ledger now covers 510 of 6,948 nodes: 84 mismatches and 6,438 unreviewed.

RFC-0020 §3 API and event-shape claims

All 14 §3 claim nodes now have source-bound reviews. Twelve match the authored API and event shapes and their Lean evidence. The explicit readScope override node had applied the agent-specific declared-permissions rule to every principal. Its two RDF literals now state the general authorization check at open and the narrower agent rule from §8; the claim IRI, subject, predicate, and section link are unchanged. The owner approved these subscription-scope semantics earlier. External RDF consumers still need review of the changed literals before normative release.

One §3 relationship remains mismatched: the eventId claim says the field is the RFC-0010 event-log identifier, but its identified-by RDF object is the generic runtime phase. No event-log domain identity exists in the current projection, so that object should be modeled with its consumer impact before changing the triple. The ledger now covers 524 of 6,948 nodes: 85 mismatches and 6,424 unreviewed. These reviews assess source alignment, not runtime conformance.

RFC-0020 §§4–5 delivery and lifecycle claims

Ten remaining §4 claim nodes now have matching source-bound reviews covering callback acknowledgement, retry after rejection, consumer idempotency, per-entity order, cross-entity ordering limits, the query match criterion, and the 10,000 acknowledged-ID deduplication window. Nine §5 nodes match the authored three-state lifecycle, including pause and resume transitions, closed-state behavior, and queue disposal. The RDF facts are unchanged. These reviews do not establish implementation or proof of the delivery guarantees. The ledger now covers 543 of 6,948 nodes: 85 mismatches and 6,405 unreviewed.

RFC-0020 remaining claims and domain nodes

All 29 remaining §6–§11 claim nodes and all 30 domain nodes now have source-bound verdicts. The overflow, event-log, security, diagnostic, and invariant claims mostly match the authored RFC and Lean catalog. One §6 literal had promoted advice to consumers needing full history into a universal replay requirement; it now preserves the authored condition. The SubscriptionOptions.readScope domain summary now distinguishes general authorization at open from the narrower agent declared-permissions bound. Those two corrections change one Turtle literal each, with stable node IRIs and section links. External RDF consumer review remains required.

Five RFC-0020 relationships remain mismatched: §3 identifies eventId by a generic runtime phase rather than the RFC-0010 event log; §8 makes the RFC-0008 read-scope relationship a self-reference; §10 applies fixed-at to effective scope even though current grants can narrow it; and two domain types claim ownership by RFC-0007 or RFC-0008 although those RFCs do not define the named GnomonQuery or ReadScopeDescriptor types. Their source facts remain unchanged pending a coordinated identity and consumer review. All 73 RFC-0020 claim nodes and 30 domain nodes have now been reviewed, with 98 matching and five mismatched verdicts. The ledger covers 602 of 6,948 nodes: 89 mismatches and 6,346 unreviewed. This does not establish runtime conformance or release readiness.

The proposed exact triple replacements, missing runtime type definitions, and local query counterfactual are in RFC0020_RDF_MODEL_PROPOSAL.md.

RFC-0019 §§1–4 registry and publish review

Thirty-one RFC-0019 claim nodes now have source-bound verdicts. Twenty-five match the authored RFC and Lean catalog, including the seven-step publish sequence approved by the owner. The inherited publish-step-order claim value still placed digest computation after registry uniqueness lookup; it now lists build and digest computation before that lookup. Its claim IRI, subject, predicate, and section link are stable. An in-memory before/after comparison found no changed result sets in the 16 checked-in claim queries; external RDF consumers of the literal remain unverified.

Six relationships remain mismatched: the two §1 scope exclusions use the manifest as subject rather than the RFC or registry protocol; §2 points the manifest sufficiency rule at registry.getManifest instead of resolution and assigns the HTTPS protocol rule to the manifest; §3 assigns the five-endpoint requirement to the manifest rather than the registry implementation; and §4 assigns deterministic compilation to Sha256Digest rather than the bundle build. These source relationships are retained pending a coherent registry domain model and consumer review. The ledger now covers 633 of 6,948 nodes: 95 mismatches and 6,315 unreviewed.

RFC-0019 authentication, routing, yanking, and domain review

The remaining 34 RFC-0019 claim nodes and 45 previously unreviewed domain nodes now have source-bound verdicts. All 65 claims and 48 domain nodes have been reviewed: 92 match and 21 have relationships that need correction or source reconciliation. The §5–§10 claim review found six more mismatches: Bearer transport and the two credential kinds are assigned only to scoped tokens; an example expiresAt field is promoted to a mandatory cardinality; §8 and §10 disagree on whether M01911 covers resolution as well as publish; and two diagnostic reservations are assigned to the registry manifest.

The domain review found nine mismatches. The registry configuration, JSON manifest, and token record are typed domain#NamedDeclaration, which the ontology defines for a Gnomon declaration instance. Four scoped-token field nodes and the ScopedToken record shape derive from a JSON example rather than a normative field schema. The gnomon-lint-semver node assigns L01401 to RFC-0014, whose current authored lint code for the same breaking-change condition is M14800. This cross-RFC code conflict must be reconciled with the diagnostic namespace decision before publication. The token module-ID summary was also respelled from authorised to authorized; this changes one Turtle literal without changing its meaning or IRI. External RDF consumers have not been checked for that literal.

The ledger now covers 712 of 6,948 nodes: 110 mismatches and 6,236 unreviewed. Source review does not prove registry CLI or server behavior.

RFC-0000 projection review complete

The final 20 RFC-0000 nodes now have source-bound verdicts. Fourteen match the authored diagnostic exception table, principal operation table, and Lean invariants. Six expose unresolved internal source conditions: three claims and one domain invariant present M-format or 1,000-code allocations as universal despite the F, L, R, and RFC-0011 exceptions; two MCP trust claims give Derived a fixed rank even though trust must come from the authenticated backing identity. The nodes retain their inherited facts pending the diagnostic and principal-taxonomy decisions in RFC-0000’s Q&A.

All 74 RFC-0000 claim nodes and 68 domain nodes have now been reviewed: 127 match and 15 mismatch their current sources. This is a source-alignment inventory, not approval of the conflicting rules or proof of implementation. The ledger covers 732 of 6,948 nodes: 116 mismatches and 6,216 unreviewed.

RFC-0003 §§1–4 composition review, first slice

Twelve RFC-0003 claim nodes covering semantic view authoring, the four execution layers, core resolution invariants, extension-point injection, priority ordering, and the default Claim widget now have source-bound verdicts. Each projection fact matches the current authored RFC and Lean catalog. RFC-0003 §4.1 itself remains ambiguous: it requires every aspect contribution to declare priority: Int while assigning 0 when priority is omitted. The companion Q&A records both first-release choices and recommends an optional source field with a required effective integer value. No normative priority rule or RDF triple was changed. The ledger now covers 744 of 6,948 nodes: 116 mismatches and 6,204 unreviewed.

RFC-0003 §§4–5a claim mapping and diagnostics review

Forty more RFC-0003 claim nodes now have source-bound verdicts. The first 20 cover ClaimFieldProps, read-only display, ActionType-backed writes, widget overrides, layout hints, and nesting; each matches the current authored and Lean sources. The next 20 cover routing, sublayout references, execution layers, compilation, and identities. Eighteen match their cited source; two relationship mismatches remain: sublayout-reference-scope assigns a rule about sublayout entries to all layout.regions entries, and identity-export-to-bundle assigns an all-layer identity rule only to widgets. Their RDF facts remain unchanged pending a source-model repair.

The authored §5 widget-resolution rule also names every region entry as a widget, while §4.2 permits sublayouts in the same list. The companion Q&A now records another first-release diagnostic collision: its layout-fetch answer reserves M03225, which authored §5a and Lean already allocate to missing default widget kind. No code or catalog identity changed. The ledger now covers 784 of 6,948 nodes: 118 mismatches and 6,164 unreviewed.

RFC-0003 remaining claim review

The final 28 RFC-0003 claim nodes now have source-bound verdicts. Twenty-three match authored §§5–9 and the Lean catalog. Five relationship or condition mismatches remain: the Sensitive-field warning omits its active-policy qualifier; widget identity incorrectly includes typed prop references; the policy-preservation relationship names routes but not pages; and two compatibility-adapter claims use ui-runtime rather than the adapter or legacy mapping layer as subject. The source facts remain unchanged for those five pending model repair. The last claim had a stray colon in its value, direct composition: authoring; its protobuf source now reads direct composition authoring, and Turtle was regenerated. This replaces one RDF literal without changing the claim IRI or triple count.

Every RFC-0003 claim node is now reviewed (80 total); its 49 domain nodes remain to be checked. The ledger covers 812 of 6,948 nodes: 123 mismatches and 6,136 unreviewed. Projection drift and all 16 claim queries pass. The broader semantic-consistency check still reports the known cross-RFC term definition drift, including View between RFC-0000 and RFC-0003; this source-bound review does not resolve it.

RFC-0003 domain projection review complete

All 49 RFC-0003 domain nodes now have source-bound verdicts. Forty reproduce the authored definitions and Lean catalog. Nine are mismatched or expose an internal source conflict: claim-field is promoted from a built-in widget kind to NamedDeclaration; sublayout is typed as a declaration kind although the RFC defines a reference; aspectContribution.priority is marked required while §4.1 also defaults omission; layout.regions omits permitted sublayout references; the policy-preservation invariant is attached only to route; two nesting invariants attach to a sublayout declaration instead of the layout graph; migration equivalence attaches to view rather than the module and compiled bundle; and policy monotonicity attaches to a sublayout reference rather than the nested layout policy envelope. No RDF relationships were changed in this review.

Every RFC-0003 projection node is now reviewed (80 claims, 49 domain). The ledger covers 861 of 6,948 nodes: 132 mismatches and 6,087 unreviewed. Projection drift and all 16 checked-in claim queries pass; the semantic release gate still fails on the documented source and cross-RFC conflicts.

RFC-0004 §1 and §10–12 aspect contract review

The first 25 RFC-0004 claim nodes now have source-bound verdicts. Twenty-one match the authored and Lean contracts; four expose source errors or conflicts. The presentation-facet syntax link points to §10 even though Authoring Shape is §11. The extend dependency/slot warning and missing-import diagnostic each have incompatible triggers within authored §10 and §12. The M04314 override-conflict claim selects the equal-specificity condition in §§5.2/7, while §5.1 says any two overrides on one field error. The source triples remain unchanged. RFC0004_MERGE_CONTRACT_PROPOSAL.md also records the companion Q&A’s incompatible merge modes and M04810/M04811 assignments for first-release owner review. The ledger now covers 886 of 6,948 nodes: 136 mismatches and 6,062 unreviewed.

RFC-0004 phase, merge, and presentation claim review

The remaining 48 RFC-0004 claim nodes now have source-bound verdicts. Thirty-eight match their authored and Lean rules; ten retain mismatches or internal source conflicts. The M08704 ownership relationship attaches to the extend rule rather than the diagnostic; two aspect-only relationships omit facet scope; the guarded and override M04314 trigger disagrees across §§5.1, 5.2, and 7; the facet-conflict use of M04311 collides with its missing-field definition; RFC-0002 ordering alignment is promoted from SHOULD to MUST; and the legacy mapping and sunset relationships point to facets or aspects rather than the compatibility contract. The exact diagnostic and section-link choices are in the updated RFC0004_MERGE_CONTRACT_PROPOSAL.md. All 73 RFC-0004 claim nodes are reviewed; its 33 domain nodes remain open. The ledger covers 934 of 6,948 nodes: 146 mismatches and 6,014 unreviewed.

RFC-0004 domain projection review complete

All 33 RFC-0004 domain nodes now have source-bound verdicts. Twenty-six match authored definitions and Lean entries; seven remain mismatched. Three fields (aspect.contribution, facet.appliesToKind, and facet.sections) are marked required in RDF without an explicit omission rule in authored §11. Two invariants attach a rule applying to both aspects and presentation facets only to aspect. The extend dependency invariant repeats the M04810 trigger conflict in §10/§12, and the override operation selects the equal-specificity interpretation despite §5.1’s broader wording. The exact first-release decisions and tests are in RFC0004_MERGE_CONTRACT_PROPOSAL.md. No domain triples changed.

Every RFC-0004 projection node is now reviewed (73 claims, 33 domain). The ledger covers 967 of 6,948 nodes: 153 mismatches and 5,981 unreviewed. Projection drift and all 16 checked-in claim queries pass. The normative release gate remains open on these and other documented conflicts.

RFC-0005 lifecycle, diagnostics, and install-plan review

The first 30 RFC-0005 claim nodes now have source-bound verdicts. Twenty-eight match the authored and Lean lifecycle or diagnostic rules. Two expose source scope conflicts: bc_risk is mandatory for every typed entry in §4a while §5 puts risk/impact annotation in a SHOULD list, and the plan-level declared-versus-installed diff is assigned to an individual InstallPlanEntry subject. The owner chose authored §4a per-agent activation atomicity for the first release. RFC-0005’s companion Q&A now aligns with that choice and defers its unsupported M0/M1 rollback and five-part quality-gate claims. The remaining authored bc_risk and activation-action ambiguities and failure-test requirements are in RFC0005_LIFECYCLE_PROPOSAL.md. No RDF triples changed. The ledger covers 997 of 6,948 nodes: 155 mismatches and 5,951 unreviewed.

RFC-0005 typed operations, model, cache, and rollback review

The remaining 61 RFC-0005 claim nodes now have source-bound verdicts. Forty-six match the authored and Lean rules; 15 relationships or source conditions remain mismatched. The all-required entry metadata selects §4a over §5’s SHOULD risk wording. Several nodes attach plan-level scheduling, typed-taxonomy, model-registration, cache-key, or transition-policy rules to individual entry fields or unrelated operations. The Q2 self/plan rollback recommendation is represented as an exclusive scope restriction. The exact model action enum and changed-model register/update trigger are still internally inconsistent in §4a/§5a and are tracked in the updated RFC0005_LIFECYCLE_PROPOSAL.md. No claim triples changed during this review.

Every RFC-0005 claim node is now reviewed (91 total); its 50 domain nodes remain open. The ledger covers 1,058 of 6,948 nodes: 170 mismatches and 5,890 unreviewed. Projection drift and all 16 claim queries pass; the normative release gate still fails on these and other documented gaps.

RFC-0005 domain projection review complete

All 50 RFC-0005 domain nodes now have source-bound verdicts. Thirty-eight match the authored and Lean contract; 12 are mismatched. The Install Operator principal is typed as a capability, and ModuleLifecycle uses assertedBy with a section IRI where the ontology requires a normative statement. The six-value activation action and unconditional agent_id requirement select unreconciled agent/model entry shapes. Required bc_risk facts choose §4a over §5’s SHOULD wording. Several enforcedBy fields add compile-time, install-time, RLS, or DB-trigger mechanisms absent from the cited clauses. The owner-approved per-agent activation rule itself is preserved. The first-release action-specific protobuf and RDF recommendation is in RFC0005_LIFECYCLE_PROPOSAL.md.

Every RFC-0005 projection node is now reviewed (91 claims, 50 domain). The ledger covers 1,108 of 6,948 nodes: 182 mismatches and 5,840 unreviewed. Projection drift and all 16 claim queries pass; no RDF triples changed in this review.

RFC-0006 Claim and status-flow review, first slice

The first 30 RFC-0006 claim nodes now have source-bound verdicts. Nineteen match authored and Lean rules; 11 retain mismatched relationships or conditions. The owner approved MUST for AI-produced or AI-modified fields and SHOULD for document-extracted or rule-inferred fields unless another rule requires a wrapper. RFC-0006 §4.5, the staged JSON publication rule, M06520 Error severity, and draft RFC-0055 now express that choice. Compiler and storage conformance remain unverified. Several projection links attach a schema-edit impact to a declaration rather than the edit, or attach a declaration-kind rule to only entity. The flow-transition removal condition conflicts with §8’s unconditional MAJOR classification. Details and acceptance tests are in RFC0006_CLAIM_WRAPPER_PROPOSAL.md. Two Stage 0/1 claim-text literals changed to include the M06520 publication failure; their generated Turtle was regenerated. Other reviewed RDF relationships remain unchanged.

The ledger covers 1,138 of 6,948 nodes: 193 mismatches and 5,810 unreviewed. Projection drift and all 16 claim queries pass; the normative release gate remains open.

RFC-0006 value types, entities, facets, and JSON review

The next 30 RFC-0006 claim nodes have source-bound verdicts. Twenty match the authored and Lean contracts; ten have mismatched subjects or missing conditions. The declaration-kind exclusion and FQN identity point only to entity instead of all declarations. Enum value naming and published-value edits attach to the enum declaration rather than the value or edit. The @epistemic diagnostic reverses its non-JSON condition. Facet evaluation order points to source rules instead of compiled invariants. The reversible marker is attached to every transition instead of regressive ones, and the inline enum restriction is attached to all enums. The reserved-name claim attaches the prohibition to the built-in JSON type rather than a user declaration.

RFC-0006 §4.A’s unconditional M06530 warning conflicted with §4.5’s annotated-JSON suppression. The authored text now limits M06530 to unannotated JSON on an AI-produced entity during import preflight; M06520 still blocks publication of any unwrapped AI field. The Stage 0 and M06530 claim-text literals and generated Turtle were aligned. The M06530 RDF diagnostic relationship remains mismatched because its subject is generic JSON and omits the preflight, annotation, and AI conditions. No RDF identities changed.

The ledger covers 1,168 of 6,948 nodes: 203 mismatches and 5,780 unreviewed. Projection drift and all 16 checked-in claim queries pass; the normative release gate remains open.

RFC-0006 remaining claim review and enum keyword conflict

The remaining 42 RFC-0006 claim nodes now have source-bound verdicts. Twenty-one match authored and Lean clauses; 21 remain mismatched. Several mutation, null-boundary, flow-audit, FQN, and self-explanation relationships attach a conditional rule to a broad field, invariant, or entity node. The three-layer authoring claim strengthens SHOULD-like prose to MUST and narrows all domain concepts to entities. The ClaimStatus regression claim omits the explicit flow-transition requirement. The exact type versus enum source conflict, 50 legacy sample declarations, and first-release options are in RFC0006_ENUM_KEYWORD_PROPOSAL.md. No RDF triples changed in this review.

All 102 RFC-0006 claim nodes are reviewed; its 90 domain nodes remain open. The ledger covers 1,210 of 6,948 nodes: 224 mismatches and 5,738 unreviewed. Projection drift and all 16 checked-in claim queries pass; the normative release gate remains open.

RFC-0006 declaration-kind domain review

The first 30 RFC-0006 domain nodes now have source-bound verdicts. Twenty-eight match the authored declaration taxonomy and named ClaimStatus flow. The separate type and enum declaration-kind nodes retain mismatch verdicts because §4.B and §4.8 disagree on whether they are distinct; the enum node also describes inline enums as named declarations. The first-release choice and the 50 sample type declarations are documented in RFC0006_ENUM_KEYWORD_PROPOSAL.md. No RDF triples changed in this review.

All 102 RFC-0006 claim nodes and 30 of its 90 domain nodes are reviewed. The ledger covers 1,240 of 6,948 nodes: 226 mismatches and 5,708 unreviewed. Projection drift and all 16 checked-in claim queries pass; the normative release gate remains open.

RFC-0006 domain projection review complete

The remaining 60 RFC-0006 domain nodes now have source-bound verdicts. Fifty-three match authored and Lean definitions; seven remain mismatched. The facet.requires summary selects facets only where §4.2 alternates between prerequisite fields or facets and facet names. The AI action invariant asserts compile-time enforcement not specified by §3. Five scalar summaries add representation guarantees absent from §4.A: currency code, fixed-precision decimal, opaque identifier, instant timestamp, and US-state code. The owner and first-release acceptance criteria are recorded in RFC0006_SCALAR_TYPES_PROPOSAL.md. The Lean JSON term definition was aligned with the approved AI wrapper rule; it now excludes only structural value validation and preserves other compiler rules. Regenerated references remain in sync. No RDF triples changed in this domain review.

Every RFC-0006 projection node is now reviewed (102 claims, 90 domain). The ledger covers 1,300 of 6,948 nodes: 233 mismatches and 5,648 unreviewed. Projection drift and all 16 checked-in claim queries pass; the normative release gate remains open.

RFC-0007 storage and identity claims, first slice

The first 25 RFC-0007 claim nodes now have source-bound verdicts. Nine match the authored and Lean storage rules; 16 attach conditional diagnostics, versioned schema edits, or instance obligations to broad type, declaration, or field IRIs. The stable-UUID relationship incorrectly identifies the id field by itself. These remain mismatches rather than claims of runtime behavior.

RFC-0007’s inline Claim<T> JSON example previously used inferred as a nested claim status. It now uses pending, a canonical RFC-0006 ClaimStatus state, while the enclosing gnomon’s separate epistemic_status may be inferred. Authored prose, Lean evidence, the inferred-status claim literal, and generated Turtle were aligned. The ClaimStatus guard now checks the example, projection column, and base-table distinction. See CLAIM_STATUS_MIGRATION.md. This corrects one RFC-0007 claim literal without changing its IRI. Runtime storage conformance remains unverified.

The ledger covers 1,325 of 6,948 nodes: 249 mismatches and 5,623 unreviewed. Projection drift and all 16 checked-in claim queries pass; the normative release gate remains open.

RFC-0007 claim projection review complete

The next 30 RFC-0007 claim nodes have 13 matches and 17 mismatches against authored storage, projection, and embedding clauses. The remaining 37 claim nodes have 20 matches and 17 mismatches against temporal, merge, derivation, and relation clauses. All 92 RFC-0007 claim nodes now have source-bound verdicts; its 68 domain nodes remain open. No RDF triples changed in this review.

Several RDF relationships attach conditional operations to broad type, declaration, or field nodes. The relation-cardinality claim says only one and many are allowed, although RFC-0006 §4.3 also allows zero-or-one; RFC-0007 §9 gives examples rather than an exhaustive rule. The via requirement likewise promotes an example to a universal requirement. A separate M07622 collision proposal records two incompatible diagnostic triggers in RFC-0007 §§7.1 and 8.

The ledger covers 1,392 of 6,948 nodes: 283 mismatches and 5,556 unreviewed. Projection drift and all 16 checked-in claim queries pass; the normative release gate remains open.

RFC-0007 base-table and derivation domain review, first slice

The first 25 RFC-0007 domain nodes now have source-bound verdicts. Twenty-two match the authored base table, storage support tables, identity, and derivation descriptions. Three derive fields (input, method, and produces) carry isRequired: true in RDF although RFC-0007 §8 only shows them in examples and does not state a universal requirement. They remain mismatches pending an explicit declaration contract. No RDF triples changed in this review.

All 92 RFC-0007 claim nodes and 25 of its 68 domain nodes are reviewed. The ledger covers 1,417 of 6,948 nodes: 286 mismatches and 5,531 unreviewed. Projection drift and all 16 checked-in claim queries pass; the normative release gate remains open.

RFC-0007 domain projection review complete

The remaining 43 RFC-0007 domain nodes have 39 matches and four mismatches. The qualifier summary names roles, weights, and contextual constraints that the authored RFC does not define. Relation cardinality asserts a required, exclusive one/many field despite RFC-0007 §9 using examples and RFC-0006 §4.3 also allowing zero-or-one. Relation to and via are likewise marked required in RDF although §9 only shows them in examples. No RDF triples changed in this review.

Every RFC-0007 projection node is now reviewed (92 claims, 68 domain). The ledger covers 1,460 of 6,948 nodes: 290 mismatches and 5,488 unreviewed. Projection drift and all 16 checked-in claim queries pass; the normative release gate remains open.

RFC-0008 language claim review, first slice

The first 43 RFC-0008 claim nodes now have source-bound verdicts. Forty-one match the authored extension, file class, naming, visibility, policy, and rule compilation clauses. The unified-dsl node says every declaration kind has unordered optional block properties, but RFC-0008 §6.0 explicitly lists five structural exceptions. The entity meaning node requires the property on every entity under §3, while §6.17 permits omission with a warning. Both remain mismatches. RFC-0001’s declaration-class grouping and RFC-0006’s type/enum keyword conflict remain separate cross-RFC issues; matching RFC-0008’s own text does not settle them. No RDF triples changed in this review.

The ledger covers 1,503 of 6,948 nodes: 292 mismatches and 5,445 unreviewed. Projection drift and all 16 checked-in claim queries pass; the normative release gate remains open.

RFC-0008 operations and grammar claims, second slice

The next 47 RFC-0008 claim nodes have 46 matches and one mismatch. The declaration-form node asserts that every construct follows keyword Name { slot* }; parameterized invariants, flow ... for Entity, and apply are authored exceptions. Action phase ordering, client error classes, mutation effects, model roles, and field sugar match their clauses. No RDF triples changed in this review.

The ledger covers 1,550 of 6,948 nodes: 293 mismatches and 5,398 unreviewed. Projection drift and all 16 checked-in claim queries pass; the normative release gate remains open.

RFC-0008 remaining claim review and file layout conflict

The remaining 47 RFC-0008 claim nodes have 45 matches and two mismatches. The universal meaning claim is incompatible with structural declaration forms and §6.17’s entity warning. The fixed class filename claim conflicts with §§4-5’s concept-based names; §7’s fixed filename table also omits several declaration kinds and places mutation under Operations despite §3 and §6.21 classifying it as Schema. Parser, manifest, visibility, and desugaring claims otherwise match authored clauses. No RDF triples changed.

All 137 RFC-0008 claim nodes are reviewed; its 79 domain nodes remain open. The ledger covers 1,597 of 6,948 nodes: 295 mismatches and 5,351 unreviewed. Projection drift and all 16 checked-in claim queries pass; the normative release gate remains open.

The source-discovery choice exposed by §7’s fixed filename table is prepared in RFC0008_FILE_LAYOUT_PROPOSAL.md, with checked-in corpus impact and first-release acceptance criteria.

RFC-0008 declaration domain review

The first 36 domain nodes are reviewed: 35 newly reviewed and the project manifest node reviewed earlier. The action summary treats optional execute and post-commit after as one required unit; the entity meaning summary selects §3 over §6.17; enum is defined in §8.17 but omitted from §3’s Schema class; and the test summary says expect where §6.0 requires then. The previously reviewed project.gnomon literal still conflicts with project.gnm. The procedure summary also exposes a §6.25/§14 conflict: procedure preconditions perform actor authorization while §14 reserves authorization logic for policy files. The related claim verdict was corrected.

The remaining 43 domain nodes have 37 matches and six mismatches. Universal required meaning conflicts with structural exceptions and §6.17. Mutation effects is marked required although §6.21 only warns when absent. Two authorization nodes select opposing §6.25 and §14 rules; the entity meaning invariant repeats the §3/§6.17 conflict. The view rule assigns invariants to policy despite §6.12 defining named invariant declarations. No RDF triples changed in this review.

Every RFC-0008 projection node is now reviewed (137 claims, 79 domain). Six claim nodes and 12 domain nodes retain mismatches. The ledger covers 1,675 of 6,948 nodes: 307 mismatches and 5,273 unreviewed. Projection drift and all 16 checked-in claim queries pass; the normative release gate remains open.

RFC-0009 agent and evidence claims, first slice

The first 40 RFC-0009 claim nodes now have source-bound verdicts: 31 match and nine mismatch. Several RDF relationships attach a general AI authoring rule to the agent declaration, or make the Claim class the subject of an AI-output-only diagnostic. The protocol-set claim makes an entire permissions block protocol-only although §9.3 also derives invokable ActionTypes from it. The source claim demands a known model ID for every claim despite §5 also allowing document references. These are projection mismatches, not evidence that the runtime enforces the contract.

RFC-0009 §9.1 previously used estimated and inferred as values of a Claim<T> field’s status. The authored rule, Lean catalog, and RDF text now identify those as the enclosing gnomon’s epistemic_status, preserving the separate RFC-0006 ClaimStatus flow and the existing RDF subject IRIs. See CLAIM_STATUS_MIGRATION.md. Generated references were refreshed. The 29 existing RFC-0009 proof-link source hashes were refreshed; their findings and theorem hashes are unchanged, and no proof was upgraded.

The ledger covers 1,715 of 6,948 nodes: 316 mismatches and 5,233 unreviewed. Projection drift and all 16 checked-in claim queries pass; the normative release gate remains open.

RFC-0009 projection review complete

The remaining 28 claim nodes have 22 matches and six mismatches. Model-version and stale-derivation rules are attached to agent rather than the model or derivation. The model declaration claim also promotes training provenance and calibration from conditional (if known / if available) to mandatory. Field-level anomaly policy is attached to a policy declaration, and agent-only sanitization is made a general Claim obligation.

All 52 domain nodes now have verdicts: 35 match and 17 mismatch. agent and policy are marked Surface despite RFC-0008 classifying them as Governance. Four AI-output evidence fields are marked required on general Claim<T>; draft is modeled as a gnomon EpistemicStatus instead of an authoring modifier. Agent-only authoring and sanitization rules are attached to broader types or the wrong declaration, and several enforcement phases are stronger than the authored source. No RDF triples changed in this review.

Every RFC-0009 projection node is now reviewed (68 claims, 52 domain): 15 claim mismatches and 17 domain mismatches. The ledger covers 1,795 of 6,948 nodes: 339 mismatches and 5,153 unreviewed. Projection drift and all 16 checked-in claim queries pass; the normative release gate remains open.

RFC-0009 declaration-class correction

The two kindClass facts for agent and policy now read Governance, as RFC-0008 §§3-4 requires. Their IRIs and other properties are unchanged. Two RDF triples changed, so consumers grouping declarations by class will now place these declarations under Governance. Their source-bound reviews were rechecked and changed to matches. RFC-0009 now has 15 claim mismatches and 15 domain mismatches; the global ledger still reviews 1,795 of 6,948 nodes, with 337 mismatches and 5,153 unreviewed. Projection drift and the 16 claim queries pass; the normative release gate remains open.

RFC-0010 canonical IR claims, first slice

The first 32 RFC-0010 claim nodes have 29 matches and three mismatches. The determinism claim omits a rule fixing extracted_at across identical source runs. The direct-mutation relationship narrows an all-components rule to the surface. The API-endpoint mapping puts an actor constraint on ActionType, while RFC-0008 §6.10 gives action no actor and §6.25 owns authorization in procedure. These need authored contract reconciliation; no RDF triples changed in this review.

RFC-0010 §4.6’s normative Rust struct / persisted rkyv contract differs from the workspace preference for protobuf boundary DTOs. The concrete first-release choices, performance tradeoff, and acceptance criteria are in RFC0010_IR_SERIALIZATION_PROPOSAL.md.

The ledger covers 1,827 of 6,948 nodes: 340 mismatches and 5,121 unreviewed. Projection drift and all 16 checked-in claim queries pass; the normative release gate remains open.

RFC-0010 storage, runtime, ABI, and security claims

The remaining 65 RFC-0010 claim nodes have 58 matches and seven mismatches. The persistence validation rule is attached to the entire runtime rather than the persistence adapter. The authored text alternates between reducers per mutation and per ActionType, and between runtime and kernel ownership of procedure authorization. It also calls the kernel entirely generated while allowing hand-authored extensions. Two ABI claims require freeing output buffers that the signatures identify as caller-provided. The proposed first-release resolution and boundary tests are in RFC0010_KERNEL_ABI_PROPOSAL.md.

Every RFC-0010 claim node now has a verdict (97 claims: 87 matches, ten mismatches). Its 78 domain nodes remain unreviewed. The ledger covers 1,892 of 6,948 nodes: 347 mismatches and 5,056 unreviewed. Projection drift and all 16 checked-in claim queries pass; the normative release gate remains open.

RFC-0010 domain projection review complete

All 78 RFC-0010 domain nodes now have source-bound verdicts: 53 match and 25 mismatch. Ten compiler-internal Knowledge Indexes are typed as NamedDeclaration, and the KnowledgeIndex trait is typed as DeclarationKind; both ontology classes denote authoring declarations. Eleven inferred effect kinds carry effectIsMutating values that RFC-0010’s EffectKind enum does not define. The deterministic IR invariant has no stable rule for its extracted_at timestamp. The persistence-adapter invariant points at the entire runtime, and the gnomon_kernel_free node inherits the contradictory output ownership rule documented in the kernel ABI proposal. No RDF triples changed in this review.

Every RFC-0010 projection node is now reviewed (97 claims and 78 domain). The ledger covers 1,970 of 6,948 nodes: 372 mismatches and 4,978 unreviewed. Projection drift and all 16 checked-in claim queries pass; the normative release gate remains open.

RFC-0010 compiler-index and effect classification correction

The eleven compiler-internal index nodes now use domain:CompilerIndex, a specific subclass of DomainEntity that does not imply an authoring declaration. The obsolete kindClass "Meta" on KnowledgeIndex was removed. The eleven effectIsMutating flags on inferred effect kinds were removed because RFC-0010 enumerates their identities without defining a mutating classification. The effect nodes and their summaries remain.

This changes eleven RDF class triples, removes one kindClass triple, and removes eleven boolean triples. The emitted RFC-0010 domain projection falls from 339 to 327 triples. Any external query grouping the indexes as declarations, or filtering those effect kinds by effectIsMutating, will change results. No deployed RDF consumer is known; local projection and link checks and all sixteen claim queries pass. The 22 source-bound node reviews were refreshed and now match. The ledger still covers 1,970 of 6,948 nodes, with 350 mismatches and 4,978 unreviewed. The unrelated term-definition drift gate remains red.

RFC-0010 persistence-adapter identity correction

RFC-0010 §5.3 assigns the no-validation rule specifically to the persistence adapter. The claim subject and domain invariant target now point to a new gnomon-persistence-adapter runtime component, linked to gnomon-runtime with componentOf. The ontology distinguishes RuntimeComponent from a module. Both corrected nodes and the new component have matching source-bound reviews. The claim and invariant IRIs remain stable; their subject/object relationship changes. The domain projection gains five triples.

The ledger covers 1,971 of 6,949 nodes: 348 mismatches and 4,978 unreviewed. Projection drift, RDF links, and all sixteen checked-in claim queries pass. The normative release gate remains open.

RFC-0011 annotation projection and diagnostic identities

All 58 claim and 28 domain nodes now have source-bound verdicts. Twelve claim relationships and five domain relationships mismatch the authored RFC. Several claims attach system-wide grammar or decorator behavior to annotation-facet; one links the kernel exclusion to the RFC-0010 document instead of the kernel. Two domain nodes classify the inline annotation block and decorator syntax as top-level declaration kinds. The complete findings are in the review ledger; no speculative RDF relationship repair was applied for these.

Three RFC-0011 Lean statements and three claim nodes used M08780, M08781, or M08782 for annotation conflicts, missing co-required facets, and circular requires chains. Those codes are RFC-0008 draft, deprecated, and experimental-reference diagnostics. The RFC-0011 prose and Lean diagnostic catalog already define M11800, M11801, and M11802 for the annotation rules. The Lean statements, derivation text, claim source, generated reference, and claim Turtle now use the existing M118 codes. A KG link gate checks that diagnostic claim objects resolve to emitted diagnostic identities. The proof citations remain reviewed mismatches; correcting a diagnostic ID does not prove the underlying behavior.

An RFC-0007 derivation fragment still named a field status after its authored rule became gnomon epistemic_status; its heading and deferred explanation now match the emitted rule. The assembled 724-entry derivation inventory has no missing or orphaned entries. The RFC-0011 source change also refreshed 132 source-bound proof review records: two statement hashes for corrected codes and shared theorem-file hashes affected by two explanatory comment edits. No theorem proposition or verdict changed.

The ledger covers 2,057 of 6,949 nodes: 365 mismatches and 4,892 unreviewed. Projection drift, RDF links, the 16 claim queries, Lean corpus regeneration, and proof-link reviews pass. Normative release remains blocked by the remaining mismatches and other independent gates.

RFC-0011 annotation identity corrections

The projection now distinguishes the compile-time annotation system and its merged AnnotationMap from the annotation facet declaration. Claims about the whole grammar extension, decorator formatting and desugaring, kernel exclusion, selector grammar, and merge target use the appropriate subjects, objects, or wording. The inline annotations block and @ decorator are typed SyntaxForm rather than top-level DeclarationKind. Five domain invariants now target the specific metadata map, constraint field, or whole system that the authored rule governs.

These edits change eight claim properties, replace two RDF class triples, remove two kindClass triples, and add two four-property domain identities. Thirteen source-bound reviews changed from mismatch to match; both new nodes have matching reviews. Four RFC-0011 claim relationships still mismatch: parser skip behavior, the facet/aspect comparison target, the M08774 informational conflict relationship, and the compiled-bundle metadata target. Those require precise relation modeling and remain open. No RDF subject IRI was removed. The ledger covers 2,059 of 6,951 nodes: 352 mismatches and 4,892 unreviewed. Projection drift, RDF links, and the sixteen checked-in claim queries pass; the normative release gate remains open.

RFC-0011 parser and facet/aspect projection correction

The §10 parser behavior now has a GnomonParser domain subject rather than an annotation-facet subject. The §2 pull/push comparison now names the whole annotation system and records both modes as a value; the individual facet pull and aspect push claims remain separately queryable. Both corrected claims and the new parser node have matching source-bound reviews. The RFC-0011 domain graph gains five triples; no existing claim or domain subject IRI was removed. Two RFC-0011 claim mismatches remain: M08774’s informational conflict relationship and the compiled-bundle metadata destination.

The authored contract has related first-release choices beyond RDF: an older parser’s skip behavior is underspecified, §4 repeats incompatible decorator grammar, §5.1 says both “silently” and M08774 Info, and the companion Q&A places annotations in UI composition_envelopes despite §5.3 assigning them to declaration metadata. The consequences and acceptance criteria are in RFC0011_ANNOTATION_CONTRACT_PROPOSAL.md.

The ledger covers 2,060 of 6,952 nodes: 350 mismatches and 4,892 unreviewed. Projection drift, RDF links, and the sixteen checked-in claim queries pass; the normative release gate remains open.

RFC-0012 tooling security projection review

The three RFC-0012 §9 claim nodes and two no-execution invariant nodes match the authored security clauses and Lean catalog. The capability node gnomon.fmt.no-execution does not: its summary calls every --print-* flag a pure syntactic transformation, while §5.2 emits a post-semantic-analysis symbol table and §5.3 emits a post-merge annotation map. The no-execution requirement remains valid. Its source-bound review is mismatched pending a narrower RDF summary; the public IRI need not change. The broader formatter, decorator, CLI, diagnostic, and LSP provenance choices are recorded in RFC0012_FORMATTER_CONTRACT_PROPOSAL.md.

The ledger now covers 2,066 of 6,952 nodes: 351 mismatches and 4,886 unreviewed. Projection drift and RDF links still pass; the normative release gate remains open.

RFC-0012 formatter, grammar, and compiler-flag projections

Eighteen more RFC-0012 domain nodes and fifteen claim nodes have source-bound reviews. The domain nodes cover authored formatter properties, grammar conformance, compiler flags, and the explicit transfer of LSP ownership to RFC-0017. The fixture domain node follows §6.3’s expected canonical AST; the companion Q&A’s expected diagnostic JSON remains an unresolved source conflict. The textDocument/formatting claim matches §7’s historical summary and must not be treated as a normative LSP rule from RFC-0012.

Two claim relationships mismatch even though their text follows the prose. print-desugared-output-passes-fmt-check puts must-pass on the round-trip invariant rather than the emitted .gnm output or its compiler operation. rfc-0012-retains-fmt-and-flags assigns formatter, compiler-flag, and CI ownership to the formatter alone. Correct subjects or model the three surfaces separately; keep their claim IRIs stable where only properties change.

The ledger now covers 2,099 of 6,952 nodes: 353 mismatches and 4,853 unreviewed. Source alignment does not establish tool implementation or the missing grammar CI gate. Normative release remains blocked.

RFC-0012 formatter relationship and diagnostic review

Thirty-eight further RFC-0012 claims were checked against §§1, 3, 4, and 10 and the Lean diagnostic catalog. Twelve relationship mismatches attach an RFC-wide scope or compiler-flag compatibility rule to a single formatter or flag; use an invariant as the actor that emits, normalizes, or preserves source; target a parse-time phase instead of a parse tree; or attach an unformatted-file violation to the positive AI-formatting invariant. These claim texts largely quote the RFC, but the RDF relationships do not express the authored subject and condition. The existing project.gnomon literal mismatch remains open.

The F12701 claim matches §4.5 and Lean. F12702’s once-per-file emission rule is unsupported by either source, and the F127x/F128x range claims reserve more codes than the authored prose or Lean catalog establishes. Eleven claim nodes and four domain nodes remain in this RFC’s review queue because they depend on the pending canonical-output, decorator, or CI-flag decisions in RFC0012_FORMATTER_CONTRACT_PROPOSAL.md.

The ledger now covers 2,137 of 6,952 nodes: 368 mismatches and 4,815 unreviewed. These are source-bound verdicts, not implementation conformance.

Grammar-section citation correction

RFC-0008’s normative EBNF is in §8, not §9. RFC-0008 §8.0 and RFC-0012’s tooling and extraction clauses now cite §8. The RFC-0012 Lean statements, derivation comments, source claims, domain summary, Turtle, and reference catalog were updated from the same correction. Exactly five RDF literals on three reviewed nodes changed; no claim or domain subject IRI changed. The 16 checked-in claim queries still pass against regenerated Turtle. This corrects the source pointer only; GRAMMAR_EXTRACTION_GAPS.md records the still-missing PEG validation and fixture gate.

The RFC-0008 and RFC-0012 narrative/Lean edits refreshed 294 source-bound projection review hashes without changing verdicts. Fifty provenBy reviews were rebound to their amended RFC narrative, three statement hashes to the amended Lean clauses, and 132 theorem-file hashes to an updated explanatory comment in the shared LanguageAndTooling theorem file. The proof and projection verdict counts remain 716 and 368 mismatches respectively.

RFC-0014 lockfile field review

Four RFC-0014 domain fields match the authored module-versioning contract and Lean catalog: the lockfile dependency id, exact version, and SHA-256 digest fields in §7.2, plus the required import version: constraint in §5. The alias-preservation invariant’s summary also matches §10 and Lean, but its RDF invariantOf points at the imports declaration. Renaming a public declaration is not an import constraint; this relationship is marked a source mismatch. Its subject IRI and claim references remain unchanged while the correct relationship and consumer impact are reviewed. The lockfile authority and staleness conflict found in the same review is recorded in RFC0014_LOCKFILE_PROPOSAL.md. The ledger now covers 2,142 of 6,952 nodes: 369 mismatches and 4,810 unreviewed.

Reviewed source-filename correction

The 16 .gnomon source-filename literals identified above, plus one RFC-0032 leaf-directory literal found during the correction, now use the authored .gnm spellings in protobuf sources and regenerated Turtle. Their subject and predicate IRIs are unchanged. Matching Lean/example typos were corrected, and the RFC-0014 reference was regenerated from Lean. Four affected Lean reference and Turtle target pairs built with Bazel. The 16 checked-in claim queries returned the same 550 rows before and after the correction; KG links, grounding, projection drift, corpus links, and source-bound review checks pass. All 17 verdicts now match their sources. Other review verdicts are unchanged; the ledger covers 2,143 of 6,952 nodes with 353 mismatches and 4,809 unreviewed. Exact-literal RDF consumers and destination CI remain unverified; see FILENAME_PROJECTION_GAPS.md.

RFC-0014 operations and shared domain identities

Twelve more RFC-0014 operation and type nodes were checked against the authored version-constraint and CLI clauses and matched their sources. The ledger now covers 2,155 of 6,952 nodes: 353 mismatches and 4,797 unreviewed.

The review exposed 197 domain IRIs reused across RFC projections. One has conflicting RDF classes and 20 have conflicting canonical FQN literals. The new domain identity audit records the cases and acceptance criteria. The strict release gate rejects these conflicts; the informational audit runs in corpus CI while source repairs are pending.

RFC-0044 compile-time transform identities and cache ordering

All 30 RFC-0044 domain nodes now have source-bound reviews. Eight match the authored and Lean type or invariant facts. Twenty-two mismatch because build-system components, the transforms: manifest entry, its fields, or their invariantOf links are modeled as language declarations. RFC-0044 §7 explicitly separates this build-time concept from the runtime data transform. The shared declaration/transform IRI has three incompatible kindClass values across four RFC projections. Section 5.4 also hashes a sorted projector list despite §§3.5 and 5.2 making projector order observable. The exact contract changes and consumer checks are in RFC0044_TRANSFORM_PROPOSAL.md.

The domain identity audit now checks kindClass as well as RDF class and FQN. It reports 23 class-of-declaration conflicts in addition to one RDF class conflict and 19 FQN conflicts. The source-bound ledger covers 2,394 of 6,952 nodes: 416 mismatches and 4,558 unreviewed. Generated RDF triples have not changed in this review.

RFC-0025 HTTP binding semantics and domain identities

All 34 RFC-0025 domain nodes now have source-bound reviews. Twenty-three match the authored HTTP slots, effect, module, types, and invariants. Eleven mismatch: outbound auth: values and per-field binding modifiers are typed as declarations, client is assigned Surface rather than its canonical Operations class, and Bytes and Map claim definitions absent from RFC-0008. The domain model proposal records the identity changes and consumer checks.

The authored RFC and Lean also conflict on path modifiers versus URL template tokens: the same combination used in the normative example is classified as M25514, while token synthesis and M25515 are inconsistent. The path binding proposal gives the first-release rule and diagnostic tests. The projection’s duplicate-location invariant remains a literal source match pending that contract decision. The ledger now covers 2,428 of 6,952 nodes: 427 mismatches and 4,524 unreviewed. No RDF triples changed in this review.

RFC-0031 GraphQL introspection adapter identities and cache

The remaining 32 RFC-0031 domain nodes are reviewed, completing its 33-node domain projection. Nine newly reviewed nodes mismatch: four build-time auth modes are typed as capabilities, and five diagnostic codes are typed as source declarations. The previously reviewed Stream<T> owner link also mismatches RFC-0020. The other 23 new nodes match authored and Lean facts.

RFC-0031 §10 and RFC-0024 §6.3 promise offline cache reuse while the shown lock entry contains no complete generated schema or snapshot locator. The live hash omits selected GraphQL root names, even though those names select operations. RFC0031_GRAPHQL_PROPOSAL.md specifies a pinned snapshot and explicit refresh contract for owner review. The literal cache invariants remain source matches until that authored contract is reconciled. The ledger covers 2,460 of 6,952 nodes: 436 mismatches and 4,492 unreviewed. RDF triples are unchanged.

RFC-0017 language server domain identities

The remaining 33 RFC-0017 domain nodes now have source-bound reviews, completing its 34-node domain projection. Nineteen new nodes mismatch: gnomon.lsp is typed as an importable module though §4 defines a CLI language-server component; six invariants point to that module IRI; eleven LSP protocol methods are typed as algebra operation kinds; and authoring-time is typed as a diagnostic phase without an authored phase definition. The earlier project.gnm declaration/file collision remains a mismatch. The other fourteen new nodes match their sources.

The authored RFC additionally forbids LSP-only codes while defining L status codes, and prohibits all non-rule data under .gnomon-cache/ while RFC-0044 requires transform cache entries there. RFC0017_LSP_PROPOSAL.md records scoped diagnostic, cache, and RDF corrections. The literal invariant nodes remain source matches until the authored contract is reconciled. The ledger covers 2,493 of 6,952 nodes: 455 mismatches and 4,459 unreviewed. Generated RDF triples are unchanged.

RFC-0016 migration rollback and domain review

All 37 RFC-0016 domain nodes now have source-bound reviews. Thirty-six match the authored and Lean migration facts. The declaration/migration summary mismatches the conditional rollback rule: it describes an unconditional forward/rollback pair. The literal preserve-rows-on-rollback invariant matches §4.3, but the preserveRows directive is undefined and the §10 drop: true footnote conflicts with historical retention. The AddField default rule also needs reconciliation with BackfillFrom on live rows. RFC0016_ROLLBACK_PROPOSAL.md records the exact contract choices and acceptance checks. No generated RDF triples changed. The ledger covers 2,530 of 6,952 nodes: 456 mismatches and 4,422 unreviewed.

RFC-0022 workflow domain identities

All 42 RFC-0022 domain nodes now have source-bound reviews. Twenty-one match the authored workflow facts. Twenty-one mismatch: five nested coordination forms are typed as declaration kinds, eleven event-log names as effect kinds, and five grammar/runtime concepts as named Gnomon data types. The domain model proposal records class and consumer changes for owner review. Existing authored workflow behavior conflicts remain in WORKFLOW_CONTRACT_PROPOSAL.md. Generated RDF triples are unchanged. The ledger covers 2,572 of 6,952 nodes: 477 mismatches and 4,380 unreviewed.

RFC-0024 I/O primitive and adapter identities

All 46 RFC-0024 domain nodes now have source-bound reviews. Twenty-two match literal authored facts. Twenty-four mismatch: three RFC-0008 call-site kinds and four later adapter modules claim RFC-0024 ownership; nested operation is typed as a top-level declaration; adapter.call is asserted as an effect without an authored definition; two adapter functions are typed as algebra operations; and thirteen interface, token, grammar, file, or example nodes are typed as named Gnomon data types. The domain model proposal gives the ontology, provenance, protobuf interchange, and consumer acceptance checks. The RFC-0024/0031 offline lockfile conflict remains a separate authored contract question. Generated RDF triples are unchanged. The ledger covers 2,618 of 6,952 nodes: 501 mismatches and 4,334 unreviewed.

RFC-0028 OpenAPI adapter identity slice

All 48 RFC-0028 domain nodes now have source-bound reviews. The gnomon.io.openapi module identity matches. Seven nodes mismatch authored identity or ownership: three auth schemes are typed as permission capabilities, client is marked Surface and adapter-only despite its Operations class, adapter.call is typed as an effect, gnomon.io.http claims RFC-0028 ownership, and openapi(path) is typed as a runtime operation. Eighteen invariant nodes match source rules; four mismatch diagnostic code scope or the openapi(path) target identity. Of the 18 client-slot and type nodes, nine match and nine mismatch shared ownership, canonical FQN, core Binary coverage, or compiler interchange identity. The proposal records the shared IRIs, M28802/03/04 conflicts, recommended first-release model, and consumer checks. Generated RDF triples are unchanged. The ledger covers 2,666 of 6,952 nodes: 521 mismatches and 4,286 unreviewed.

RFC-0030 Protobuf adapter identities and interchange

All 40 RFC-0030 domain nodes now have source-bound reviews: 26 match and 14 mismatch. The mismatches include the previously reviewed Stream<T> ownership gap, a compile-time adapter function typed as a runtime operation, compiler interchange typed as author-writable values, undefined Binary and misclassified void, adapter-specific summaries on shared slots, four gRPC modes versus RFC-0024’s two-value interface, and a transitive lockfile hash sorted by absolute checkout path. The proposal records the ABI, type, hash, RDF, and consumer decisions. Generated RDF triples are unchanged. The ledger covers 2,705 of 6,952 nodes: 534 mismatches and 4,247 unreviewed.

RFC-0032 build-layer domain review

All 57 RFC-0032 domain nodes now have source-bound reviews: seven match and 50 mismatch. The mismatches include seven Bazel rules typed as Gnomon declaration kinds, three Bazel providers typed as named Gnomon declarations, four build actions typed as Gnomon effects, four Bazel rule sets/extensions typed as Gnomon modules, five internal artifact or provider types typed as Gnomon Value data types, 25 Bazel attributes and provider slots typed as Gnomon declaration fields, and two invariants with incomplete input scope or the wrong fingerprint comparison. The source and RDF relationship evidence is in RFC0032_DOMAIN_MODEL_PROPOSAL.md. No source triples or subject IRIs changed. The ledger now covers 2,762 of 6,952 nodes, with 584 mismatches and 4,190 unreviewed.

RFC-0033 API surface domain review

All 40 RFC-0033 domain nodes now have source-bound verdicts: 28 match and 12 mismatch. Authentication scheme tokens, illustrative error names, a generated handler stub, and two conceptual version/scheme types are typed as authored declarations or Gnomon Value types even though the RFC does not declare them as such. The separate omitted-auth policy gap is recorded in RFC0033_API_MODEL_PROPOSAL.md. No source RDF triples or subject IRIs changed. The ledger now covers 2,802 of 6,952 nodes, with 596 mismatches and 4,150 unreviewed.

RFC-0034 server-binding domain review

All 44 RFC-0034 domain nodes now have source-bound reviews: 24 match and 20 mismatch. The mismatches cover compiled artifacts and a nested binding block typed as authored declarations, four server adapter modules whose owning RFCs have not yet authored the advertised extensions, five adapter slot types typed as Gnomon Value types, unconditional requiredness on five protocol-specific slots, the client-streaming return shape, and two misattached or conflicting invariants. The contract and consumer acceptance criteria are in RFC0034_SERVER_BINDING_PROPOSAL.md. No RDF source triples or subject IRIs changed. The ledger now covers 2,846 of 6,952 nodes, with 616 mismatches and 4,106 unreviewed.

RFC-0035 core standard-library domain review

All 61 RFC-0035 domain nodes now have source-bound reviews: 60 match and one mismatch. The ValidationError.fields RDF field collapses an authored List<FieldViolation> to one FieldViolation and asserts requiredness absent from the source syntax. The separate first-release error taxonomy and nonempty list decision is in RFC0035_STANDARD_LIBRARY_PROPOSAL.md. The owner-approved ClaimStatus correction also removed a stale claim-status phrase from the core.claims module summary; one RDF literal changed, and its subject IRI remains stable. The ledger now covers 2,907 of 6,952 nodes, with 617 mismatches and 4,045 unreviewed.

RFC-0036 graph data model domain review

All 92 RFC-0036 domain nodes now have source-bound reviews: 51 match and 41 mismatch. Nine backend record/input/cache shapes and their 24 fields are misclassified as authored Gnomon declarations and fields; Resource.kind is projected as a required LtreePath despite the authored opaque-text rule; seven backend or graph-algebra types are misclassified as author-writable Value types. The graph/storage-versus-authoring model and acceptance criteria are in RFC0036_GRAPH_MODEL_PROPOSAL.md. No RDF triples or subject IRIs changed. The ledger now covers 2,999 of 6,952 nodes, with 658 mismatches and 3,953 unreviewed.

RFC-0037 graph backend services domain review

All 90 RFC-0037 domain nodes now have source-bound reviews: nine match and 81 mismatch. The nine backend invariants match the authored rules. The 13 backend service, factory, and query-definition declarations, nine backend write or transaction effects, 31 service methods, and 28 TypeScript/backend types are incorrectly classified with Gnomon authoring classes. The proposed backend API classes and implementation reconciliation are in RFC0037_BACKEND_MODEL_PROPOSAL.md. No RDF triples or subject IRIs changed. The ledger now covers 3,089 of 6,952 nodes, with 739 mismatches and 3,863 unreviewed.

RFC-0038 graph client domain review

All 73 RFC-0038 domain nodes now have source-bound verdicts: 12 match and 61 mismatch. The 17 client API declarations, 11 options/context/result fields, 17 methods and batch helpers, and 16 runtime types are incorrectly classified with Gnomon authoring classes. The RFC-0038 proposal also records direct framework conformance gaps in the query builder, batch atomicity, client surface, and session/audit binding. No RDF source triples or subject IRIs changed. The ledger now covers 3,162 of 6,952 nodes, with 800 mismatches and 3,790 unreviewed.

RFC-0018 compiler-services claim review

All 68 RFC-0018 claim nodes now have source-bound reviews. Sixty-six match the authored RFC and Lean catalog. Two mismatch: the model pin projection repeats a both-present precedence rule that conflicts with RFC-0008’s exactly-one grammar and with RFC-0018 Lean b13, and §7.3 simultaneously filters out and displays incompatible mustSatisfy completions. The exact choices and acceptance checks are in RFC0018_MODEL_PIN_PROPOSAL.md and RFC0018_COMPLETION_FILTER_PROPOSAL.md. No projection fact or IRI changed, and this review does not verify compiler behavior. The current ledger covers 3,415 of 6,952 nodes, with 825 mismatches and 3,537 unreviewed.

RFC-0018 compiler API domain review

All 69 RFC-0018 domain nodes now have source-bound verdicts: 14 invariants match, while 55 compiler services, artifacts, methods, API types, and the Rust crate are typed with Gnomon authoring classes. The compiler domain proposal defines the class map, records three Q&A decisions absent from normative sections, and lists consumer and conformance checks. No RDF source triple or subject IRI changed. The ledger now covers 3,484 of 6,952 nodes, with 880 mismatches and 3,468 unreviewed.

RFC-0036 scope and diagnostic claim review

Fifteen RFC-0036 claim nodes now have source-bound verdicts. The scope, intrinsic ownership, wire casing, and diagnostic range claims agree with the authored RFC and Lean catalog. Two diagnostic claims mismatch the combined source contract: M36070 is a warning for an insert §4.2 requires rejecting, and M36080 describes normalization despite §5’s M36030 defect rule. RFC0036_DIAGNOSTIC_CONSISTENCY_PROPOSAL.md records the decision and acceptance gates. No RDF triple or claim IRI changed. The ledger now covers 3,499 of 6,952 nodes, with 882 mismatches and 3,453 unreviewed. The projection, source-review, and 16 claim-query checks pass; the strict semantic release gate remains red.

RFC-0036 identity and predicate claim review

Fifteen more RFC-0036 claim nodes now have source-bound verdicts. Fourteen match §3–§4 and the Lean catalog at the claim level. The absolute backend-allocation claim mismatches RFC-0036’s own optional ResourceInput.id and its Lean schema. RFC0036_ID_ALLOCATION_PROPOSAL.md records the implemented explicit-ID paths and the first-release choices. No RDF fact or subject IRI changed. The ledger now covers 3,514 of 6,952 nodes, with 883 mismatches and 3,438 unreviewed. Projection, review, and all 16 claim-query checks pass; the semantic release gate remains red.

RFC-0036 data, interval, and permission claim review

Twenty more RFC-0036 claims now have source-bound matching verdicts across §4–§5: registered Resource data shape, temporal Statement rules, Predicate identity, endpoint validity, and permission bits. Matching the authored RFC and Lean catalogs does not establish backend conformance. In particular, the separate decisions on statement identity and the M36070/M36080 diagnostic conflicts remain open. No RDF fact or IRI changed. The ledger now covers 3,534 of 6,952 nodes, with 883 mismatches and 3,418 unreviewed. Projection, review, and all 16 claim-query checks pass; the semantic release gate remains red.

RFC-0036 permission, data, time, and deletion claim review

The remaining 28 RFC-0036 claim nodes now have source-bound verdicts. Twenty-seven match the authored §§5–9 and Lean catalog. The §9.1 claim that every entity except Predicate has deletedAt conflicts with the §6.2–§6.4 persisted shapes for PermissionCache, ResourcePolicy, StatementPolicy, and ExternalLink; Lean classifies all four as graph entities. The proposed contract and backend acceptance checks are in RFC0036_SOFT_DELETE_SHAPE_PROPOSAL.md. No RDF fact or IRI changed. All 78 RFC-0036 claims are now reviewed. The ledger covers 3,562 of 6,952 nodes, with 884 mismatches and 3,390 unreviewed. Projection, review, and all 16 claim-query checks pass; the strict semantic release gate remains red.

RFC-0042 authorization claim review

All 76 RFC-0042 claim nodes now have source-bound verdicts. Seventy-five faithfully project the authored policy shape, evaluation, cache, shorthand, and API authorization rules. The ResourcePolicy equivalence claim exposes an internal contradiction: §3.1 and Lean require predicate on every predicate_policy, while §7 calls a predicate-free ResourcePolicy an equivalent predicate_policy. The resolution and conformance fixtures are in RFC0042_CLAIM_REVIEW.md. The separate domain review still records the preset type contradiction. No RDF fact or IRI changed in this review. The ledger covers 4,236 of 6,952 nodes, with 1,007 mismatches and 2,716 unreviewed. The strict semantic release gate remains red.

RFC-0037 contract and collection claim review

The first 25 RFC-0037 claim nodes now have source-bound verdicts. Twenty-four match the authored §§1–4 and Lean catalog. The read-only write() claim inherits §3.3’s M37020 rule, but the Lean diagnostic catalog defines M37021 for that exact condition. The owner-facing resolution and conformance criteria are in RFC0037_READONLY_DIAGNOSTIC_PROPOSAL.md. The 56 remaining RFC-0037 claims still require review. No RDF fact or IRI changed. The ledger covers 3,587 of 6,952 nodes, with 885 mismatches and 3,365 unreviewed; the semantic release gate remains red.

RFC-0037 service and traversal claim review

The next 25 RFC-0037 claim nodes now have source-bound verdicts across §4–§5. Twenty-four match the authored service, transaction, and traversal contracts. The WorkspaceService out-of-scope claim instead attributes Workspace creation and tenant binding to RFC-0014, which is about module versioning; the current prose cites RFC-0045 and RFC-0051 for narrower tenant-mode and RLS responsibilities. The correction is recorded in RFC0037_WORKSPACE_REFERENCE_GAP.md. No RDF fact or IRI changed in this review. The ledger covers 3,612 of 6,952 nodes, with 886 mismatches and 3,340 unreviewed. Thirty-one RFC-0037 claims still require review, and the strict semantic release gate remains red.

RFC-0037 composition, pagination, and diagnostic claim review

The remaining 31 RFC-0037 claims now have source-bound verdicts. Twenty-seven match the authored §§5–8 and Lean catalog. Two read-only-write claims expose the same M37020/M37021 conflict noted above. Two §8.1 compatibility claims are stale: the owner-approved edge-rich traversal path required behavioral changes to the legacy model and adapters, documented in RFC0037_LEGACY_COMPATIBILITY_GAP.md. The source-bound reviews now cover all 81 RFC-0037 claims, with six mismatches. No RDF fact or IRI changed in this review. The full ledger covers 3,643 of 6,952 nodes, with 890 mismatches and 3,309 unreviewed. The strict semantic release gate remains red.

RFC-0037 WorkspaceService reference correction

The RFC-0014 tenancy attribution was corrected in the protobuf claim and Lean source to the narrower RFC-0045 tenant-mode and RFC-0051 PostgreSQL RLS responsibilities. The claim subject IRI is unchanged; one claim-text literal and the corresponding Lean evidence and document references changed. The pinned Lean corpus compiled, its RFC Turtle regenerated, and the reference catalog remained byte-identical. All 171 RFC-0037 reviews were rebound to the changed Lean source. The WorkspaceService claim now matches, leaving five RFC-0037 claim mismatches. The ledger remains at 3,643 of 6,952 reviewed, with 889 mismatches and 3,309 unreviewed. The strict semantic release gate remains red.

RFC-0037 legacy compatibility correction

The §1 and §8 text now distinguishes the inherited service map from the edge-rich traversal result selected for Gnomon. Two RDF claims no longer say the legacy memory and PostgreSQL backends needed no behavioral changes. Lean motivations and evidence were aligned, claim Turtle regenerated, and all 171 RFC-0037 reviews rebound to the changed authored and Lean sources. The two compatibility claims now match their sources. Their subject IRIs are stable; their claim text and one claim predicate changed. The ledger covers 3,643 of 6,952 nodes, with 887 mismatches and 3,309 unreviewed. Backend conformance remains an independent release requirement, and the strict semantic release gate remains red.

RFC-0038 legacy-client maturity correction and initial claim review

RFC-0038 §1 and §10 now identify the inherited graph client as a migration baseline. Its current class has no client.query() entry point, and the builder’s execute() and fetchAll() methods still throw. The two RDF claims about full production coverage and preserved legacy naming now state the target contract and actual legacy names. Lean motivations were aligned; claim Turtle regenerated; all 73 RFC-0038 domain reviews were rebound to the changed authored and Lean sources without altering their class verdicts. The first 20 RFC-0038 claim nodes now have source-bound matching verdicts. The reviewed source facts do not establish runtime conformance. Claim subject IRIs remain stable. The ledger covers 3,663 of 6,952 nodes, with 887 mismatches and 3,289 unreviewed. The strict semantic release gate remains red.

RFC-0038 transaction, namespace, and cursor claim review

The next 25 RFC-0038 claims now have source-bound verdicts. Twenty-three match the authored transaction, namespace, and token rules. Two cursor claims expose the unresolved RFC-0037/0038 type conflict: RFC-0038’s iterable Cursor<T> is incompatible with RFC-0037’s page-shaped Cursor<T>. The toArray() claim also states 10,000 as a fixed cap although §5.1 and Lean make it an implementation-defined limit with a 10,000 default. The evidence and acceptance criteria remain in RFC0038_QUERY_PAGINATION_PROPOSAL.md. No RDF fact or IRI changed in this review. The ledger covers 3,688 of 6,952 nodes, with 889 mismatches and 3,264 unreviewed. Twenty-four RFC-0038 claims still require review; the strict semantic release gate remains red.

RFC-0038 builder, batch, session, and audit claim review

The remaining 24 RFC-0038 claim nodes now have source-bound matching verdicts across §§5–9. These verdicts confirm what the authored RFC and Lean catalog say; they do not establish that the current client executes builder queries, secures continuation tokens, binds tenant context, or emits the required audit records. Those implementation and conformance gaps remain in RFC0038_QUERY_PAGINATION_PROPOSAL.md and the graph client contract audit. All 69 RFC-0038 claims are now reviewed, with two cursor-related mismatches. The ledger covers 3,712 of 6,952 nodes, with 889 mismatches and 3,240 unreviewed. No RDF fact or IRI changed in this review; the strict semantic release gate remains red.

RFC-0039 template envelope and permissions claim review

The first 20 RFC-0039 claims now have source-bound verdicts. Eighteen match the authored §§1–3 and Lean catalog. The envelope apiVersion claim conflicts with the active shared document parser and awaits the first-release identity choice in GRAPH_DOCUMENT_API_VERSION_PROPOSAL.md. The exports.root claim includes a value-form branch without a defined expression object or executable result; the contract alternatives are in RFC0039_ROOT_VALUE_FORM_PROPOSAL.md. No RDF fact or IRI changed in this review. The ledger covers 3,732 of 6,952 nodes, with 891 mismatches and 3,220 unreviewed. Fifty-nine RFC-0039 claims still require review; the strict semantic release gate remains red.

RFC-0039 visibility and object-body claim review

The next 20 RFC-0039 claims now have source-bound verdicts. Eighteen match the authored permissions, visibility, Resource, Statement, and nested-call rules. Two more claims inherit the unresolved value-root contract: the recommendation to split templates without a primary Resource and the blanket Resource-reference interpretation of nested-call roots do not cover a value-form root coherently. The choice and acceptance tests are in RFC0039_ROOT_VALUE_FORM_PROPOSAL.md. No RDF fact or IRI changed in this review. The ledger covers 3,752 of 6,952 nodes, with 893 mismatches and 3,200 unreviewed. Thirty-nine RFC-0039 claims still require review; the strict semantic release gate remains red.

RFC-0039 expression and executor claim review

The next 20 RFC-0039 claims now have source-bound verdicts. Seventeen match the authored §4–§6 expression and execution rules. Three expose unresolved contracts: the retired Zod grammar path versus the extracted expression repository owner, the unspecified variadic hash encoding (whose runtime had also truncated its digest), and the missing value slot in the execution result for value-form roots. The evidence and acceptance criteria are in RFC0039_EXPRESSION_SOURCE_GAP.md, RFC0039_HASH_ENCODING_PROPOSAL.md, and RFC0039_ROOT_VALUE_FORM_PROPOSAL.md. The framework’s single-string hash builtin now emits the complete SHA-256 hex digest; its full graph-template-engine Bazel target passed locally with 32 Vitest tests. No RDF fact or IRI changed in this review. The ledger covers 3,772 of 6,952 nodes, with 896 mismatches and 3,180 unreviewed. Nineteen RFC-0039 claims still require review; the strict semantic release gate remains red.

RFC-0039 idempotency, storage, and outcome claim review

The remaining 19 RFC-0039 claims now have source-bound verdicts. Seventeen match the authored §§6–9 and Lean catalog. The content-addressing claim equates a stable template digest with identical execution results even though now, uuid, and uniqueId vary and no digest lookup is implemented. The absolute rollback claim conflicts with §6.5 and M39050’s explicit continueOnError partial-commit path. The first-release alternatives and tests are in RFC0039_EXECUTION_OUTCOME_PROPOSAL.md. All 79 RFC-0039 claims now have source-bound reviews; nine remain mismatches. No RDF fact or IRI changed in this review. The ledger covers 3,791 of 6,952 nodes, with 898 mismatches and 3,161 unreviewed. The strict semantic release gate remains red.

RFC-0039 domain identity review

All 63 RFC-0039 domain nodes now have source-bound reviews. Thirty-two match the authored template contract; 31 need correction. Twenty-five class mismatches project nested object forms as top-level declarations, expression forms and builtins as Gnomon algebra operations, result slots as declaration fields, and template/runtime schemas as language types. The remaining six cover the unresolved value-root wording on two fields and one invariant, retired expression ownership, unconditional rollback wording, and missing RFC provenance on Template.metadata.version. The concrete class map and acceptance checks are in RFC0039_DOMAIN_CLASS_PROPOSAL.md. No RDF fact or IRI changed in this review. The ledger covers 3,854 of 6,952 nodes, with 929 mismatches and 3,098 unreviewed. The strict semantic release gate remains red.

The Template.metadata.version provenance omission was corrected in the source protobuf and generated Turtle after this review. Its source-bound verdict is now matching. The ledger still covers 3,854 of 6,952 nodes, with 928 mismatches and 3,098 unreviewed.

RFC-0040 manifest and diagnostic claim review

The first 20 RFC-0040 claims now have source-bound verdicts. Nineteen match the manifest envelope, exports, compile-pipeline, token-scope, and Lean diagnostic contracts. One exposes an authored M40021 conflict: §§4.2 and 12 reserve it for a call to an unimported template, while §13.3 and Lean also assign it to an unused template import. The proposed single meaning and fixtures are in RFC0040_TEMPLATE_IMPORT_DIAGNOSTIC_PROPOSAL.md. No RDF fact or IRI changed. The ledger covers 3,874 of 6,952 nodes, with 929 mismatches and 3,078 unreviewed. Fifty-four RFC-0040 claims remain. The strict semantic release gate remains red.

RFC-0040 envelope, dependency, and provider claim review

Twenty-nine further RFC-0040 claims now have source-bound matching verdicts for the manifest envelope, dependencies, template imports, token scopes, and provider lifecycles. The module.gnm document-name claim had already been reviewed during an earlier literal correction and was not duplicated. The ledger covers 3,903 of 6,952 nodes, with 929 mismatches and 3,049 unreviewed. Fifty of 75 RFC-0040 claims are reviewed; 25 remain. The strict semantic release gate remains red.

RFC-0040 hooks, transforms, and objects claim review

The remaining 25 RFC-0040 claims now have source-bound matching verdicts. They cover token and provider defaults, configuration flags, hooks, build-time transforms, object validation, and graph object shapes. All 75 RFC-0040 claims are reviewed; the M40021 conflict remains the sole mismatch in that claim set. The ledger covers 3,928 of 6,952 nodes, with 929 mismatches and 3,024 unreviewed. RFC-0040 domain nodes remain unreviewed. The strict semantic release gate remains red.

RFC-0040 manifest domain review

All 85 RFC-0040 domain nodes now have source-bound verdicts: 60 match and 25 expose unresolved identity or contract drift. Thirteen graph-document, module-object, and manifest-member nodes are typed as top-level Gnomon DeclarationKind forms. Five token-scope nodes have prefixed FQNs absent from the authored enum and collide with requester session scopes. Two invariants target the wrong phase or transform identity. Five field/type nodes overstate category ordering, hook timing, provider optionality, or confuse namespace/version and exact/range SemVer contracts. The exact evidence, proposed class map, and acceptance checks are in RFC0040_DOMAIN_IDENTITY_PROPOSAL.md. No RDF fact or IRI changed in this review. The ledger covers 4,013 of 6,952 nodes, with 954 mismatches and 2,939 unreviewed. The strict semantic release gate remains red.

The RFC-0040 RDF source now preserves the optional use of Module.category, marks the hook context invariant as install-time, and distinguishes exact module SemVer from an import range. Generated Turtle and those three source-bound reviews were refreshed. The ledger remains at 4,013 reviewed of 6,952 nodes, with 951 mismatches and 2,939 unreviewed.

RFC-0041 install runtime and lifecycle claim review

The first 25 RFC-0041 claims now have source-bound verdicts. Twenty-three match the authored install, hook, provenance, audit, and uninstall rules. The inherited faithful-codification claim conflicts with §14.3 behavior changes and the still-incomplete install audit entry. The lifecycle invariant claims strategy depends only on version comparison, contradicting force and manifest-hash reinstall rules. Evidence, first-release recommendations, and backend tests are in RFC0041_INSTALL_CONFORMANCE_PROPOSAL.md and RFC0041_LIFECYCLE_PRIORITY_PROPOSAL.md. Framework commits 279bbaf76 and 65d300610 removed database-audit suppression and made module failures propagate for transaction rollback; the local graph-module-engine Bazel target passed 28 Vitest files and 216 tests. No RDF fact or IRI changed in this review. The ledger covers 4,038 of 6,952 nodes, with 953 mismatches and 2,914 unreviewed. Sixty-five RFC-0041 claims remain; the strict semantic release gate remains red.

RFC-0041 pipeline and strategy claim review

The next 35 RFC-0041 claims now have source-bound verdicts. Twenty-five match dependency, bootstrap, diagnostic, and lifecycle clauses. Ten expose three linked contract gaps: transaction phases 0–1 are outside the transaction despite the blanket phase claim; optional dependency availability at plan time cannot retroactively produce a compile-time M40021; and unqualified execution determinism omits clocks, IDs, graph reads, and hooks. The same-major no-op rule also conflicts with force and changed-hash reinstall, and highest-patch wording disagrees with full SemVer ordering. The concrete first-release choices and tests are in RFC0041_INSTALL_SEQUENCING_PROPOSAL.md and RFC0041_LIFECYCLE_PRIORITY_PROPOSAL.md. No RDF fact or IRI changed. The ledger covers 4,073 of 6,952 nodes, with 963 mismatches and 2,879 unreviewed. Sixty of 90 RFC-0041 claims are reviewed; 30 remain. The strict semantic release gate remains red.

RFC-0041 transaction, hash, installer, and linker claim review

The final 30 RFC-0041 claims now have source-bound matching verdicts. They faithfully project the authored transaction, hash-domain, stable-ID, installer, and linker rules. The extracted engine does not yet provide the full surface: batch savepoints do not commit earlier modules, the required manifest hash and module-record fields are absent, object failures lack M41020, operations are no-ops, installer order differs, and the runtime provider/template linker and its diagnostics are unimplemented. The exact source comparison and backend acceptance cases are in RFC0041_ENGINE_CONFORMANCE_GAPS.md. All 90 RFC-0041 claims are reviewed; 12 carry source-semantic mismatches. No RDF fact or IRI changed. The ledger covers 4,103 of 6,952 nodes, with 963 mismatches and 2,849 unreviewed. The strict semantic release gate remains red.

RFC-0041 install-domain identity review

All 57 RFC-0041 domain nodes now have source-bound verdicts. Fourteen match authored stable-ID hints, install invariants, planning phase, and graph predicate identities. Forty-three need correction: one installed Resource kind, 15 manifest/runtime artifacts projected as source declarations, nine fields on a graph Resource or plan artifact, four contradictory invariants, one runtime engine projected as a Gnomon module, nine runtime outcomes/phases projected as language algebra operations, and four runtime values projected as source-language types. The class map, cross-RFC identities, and consumer checks are in RFC0041_DOMAIN_IDENTITY_PROPOSAL.md. No RDF fact or IRI changed in this review. The ledger covers 4,160 of 6,952 nodes, with 1,006 mismatches and 2,792 unreviewed. The strict semantic release gate remains red.

RFC-0043 operation claim review

All 77 RFC-0043 claim nodes now have source-bound verdicts. Eleven expose internal contradictions in the authored operation contract: transaction atomicity for external effects, mutation classification for adapters in queries, authorization error types, guard placement, idempotency persistence after commit, audit coverage, and unchanged-install wording. A concrete first-release proposal and acceptance fixtures are in RFC0043_EXECUTION_CONTRACT_PROPOSAL.md. The owner decision on this public contract is pending. No normative RDF fact or IRI changed. The ledger covers 4,313 of 6,952 nodes, with 1,018 mismatches and 2,639 unreviewed. The strict semantic release gate remains red.

RFC-0043 operation-domain identity review

All 58 RFC-0043 domain nodes now have source-bound verdicts. The language procedure and nine effect kinds match. Forty-eight require class or target correction: the manifest operation and nested workflow, 31 manifest slots, five runtime shapes, and ten invariants linked to those misclassified targets. The class map and acceptance checks are in RFC0043_DOMAIN_IDENTITY_PROPOSAL.md. No RDF fact or IRI changed while the cross-RFC module-object class choice is pending. The ledger covers 4,371 of 6,952 nodes, with 1,066 mismatches and 2,581 unreviewed. The strict semantic release gate remains red.

RFC-0044 transform claim review

All 68 RFC-0044 claim nodes now have source-bound verdicts, including the previously reviewed output-file name. Ten new mismatches expose an undefined IR-only output location, order-insensitive cache keys for order-sensitive projectors, wall-clock data in supposedly deterministic IR, inaccurate claims about the current core.sdo generators, and install wording for a build-only feature. The first-release contract and acceptance checks are in RFC0044_REPRODUCIBILITY_PROPOSAL.md. The owner decision on public transform semantics is pending. No normative RDF fact or IRI changed. The ledger covers 4,438 of 6,952 nodes, with 1,076 mismatches and 2,514 unreviewed. The strict semantic release gate remains red.

RFC-0045 process and hosting claim review

All 76 RFC-0045 claim nodes now have source-bound verdicts. Ten expose contradictory or stale host guarantees: control endpoints are promised before their listener binds, the default HTTP serve and control endpoints claim the same port without a shared-listener rule, an undefined READY_FD protocol, incomplete shutdown deadline and environment-variable definitions, an unconditional clean OOM exit, and migration instructions when nothing is deployed. The implementable first-release contract and process fixtures are in RFC0045_HOST_CONTRACT_PROPOSAL.md. The owner decision is pending. No normative RDF fact or IRI changed. The ledger covers 4,514 of 6,952 nodes, with 1,086 mismatches and 2,438 unreviewed. The strict semantic release gate remains red.

RFC-0046 configuration claim review

All 67 RFC-0046 claim nodes now have source-bound verdicts. Eight expose contract gaps: required versus optional absence, four-layer precedence versus secret-backend resolution, prefix-accepting numeric parsers, a Number type outside the canonical hierarchy, a premature core.flags availability claim, and boot-only cache wording that omits secret/flag refresh. The recommended first-release semantics and fixtures are in RFC0046_RESOLUTION_CONTRACT_PROPOSAL.md. The public resolution and numeric-type decisions remain pending. No RDF fact or IRI changed. The ledger covers 4,581 of 6,952 nodes, with 1,094 mismatches and 2,371 unreviewed. The strict semantic release gate remains red.

RFC-0047 observability claim review

All 64 RFC-0047 claim nodes now have source-bound verdicts. Ten expose source-semantic conflicts: exactly-one audit versus tolerated audit failure, rollback after an external audit sink failure, redacted SHA-256 hashes that cannot prove full input identity, exported-span guarantees under SDK sampling, trace context conflated with correlation IDs, and stale deployed-system migration wording. A first-release durable audit, versioned proto, keyed fingerprint, and trace-context proposal with fixtures is in RFC0047_OBSERVABILITY_CONTRACT_PROPOSAL.md. The owner decision is pending. No RDF fact or IRI changed. The ledger covers 4,645 of 6,952 nodes, with 1,104 mismatches and 2,307 unreviewed. The strict semantic release gate remains red.

RFC-0047 observability domain identity review

All 57 RFC-0047 domain nodes now have source-bound verdicts. Three invariants match. Fifty-four need correction: a nested errors syntax form, thirteen metric/span event names, 26 audit-record fields, three runtime methods, four runtime/telemetry shapes, six invariants linked to those misclassified types, and a stack-trace invariant that strengthens two SHOULD rules into MUST-like wording. The class map and acceptance checks are in RFC0047_DOMAIN_IDENTITY_PROPOSAL.md. No RDF fact or IRI changed. The ledger covers 4,702 of 6,952 nodes, with 1,158 mismatches and 2,250 unreviewed. The strict semantic release gate remains red.

RFC-0048 approved first-release session model

The owner approved the session contract in RFC0048_SESSION_CONTRACT_PROPOSAL.md on 2026-10-04. The authored RFC and Lean catalog now specify a kernel-owned public scope for request-only anonymous access, capability-set attenuation, explicit credential strategy outcomes, authoritative revocation checks, atomic token rotation, and a refresh result carrying an optional replacement token. RFC-0047’s audit record now includes authMethod. The affected claim projection facts and IRIs were updated to the approved first-release semantics; the new audit-record field adds a domain node. Generated claim/domain Turtle, RFC Turtle, and reference catalogs were regenerated from their sources.

The 78 RFC-0048 claim nodes have source-bound reviews. The new RFC-0047 authMethod domain node is reviewed as a mismatch because the current ontology Field class denotes a source declaration slot, while AuditLogEntry is a runtime record; it joins the previously documented RFC-0047 domain identity work. The ledger now covers 4,782 of 6,954 nodes, with 1,159 mismatches and 2,172 unreviewed. Most RFC-0048 domain nodes, runtime behavior, external RDF consumers, and the strict semantic release gate remain open.

The approved public scope has an RFC-0048 domain node. Its reviewed Capability class and capabilityScope value follow the current ontology. Four inherited domain summaries that still said “no scopes,” compared scope-name strings, or promised one object instance across restarts were corrected.

RFC-0040 §5.1.1 now includes public in the token scope grammar and limits root resolution to authenticated system or explicitly root-granted contexts. Its root-resolvability and scope-enumeration claim literals and token-scope domain summary were aligned. All 160 existing RFC-0040 source-bound reviews were rebound to the changed authored and Lean sources. The claim and domain subject IRIs remain stable; no deployed migration is needed.

RFC-0000 required section titles (2026-10-07)

The required-rfc-sections claim value now repeats all seven full titles from authored RFC-0000 §5 and Lean statement b0. This corrects four shortened titles in the projection; it does not change the authored contract, claim IRI, subject, or section provenance. The protobuf source was updated, Turtle regenerated, and the node’s source-bound review refreshed. The review gate reports 6,954 reviewed nodes, 2,421 mismatches, and no unreviewed nodes. The separate domain summary and Lean invariant still have their recorded mismatch and are not cleared by this correction.

The paired domain summary and Lean invariant have now been aligned with those same authored titles. The pinned Lean corpus compiled and regenerated its reference catalogs and RFC Turtle successfully. All RFC-0000 projection reviews were rebound to the changed Lean catalog hash; their other findings and verdicts remain unchanged. The section-structure domain review now matches, leaving 2,420 semantic mismatches. Proof review and provenBy ledger validation still pass their source-integrity checks; the 714 provenBy mismatches remain.

RFC-0001 backend-only exclusion correction (2026-10-07)

Authored §4 requires M01002 for composition or view declarations in backend-only modules. The claim literals, paired domain summary, and Lean diagnostic had substituted route for composition. They now name the authored declarations; claim and domain identities and diagnostic code remain unchanged. Lean catalogs compiled against the pinned framework and the reference catalog and Turtle were regenerated. The claim review now matches. The domain review’s prior match is withdrawn because it also types a module.type value as NamedDeclaration, a declaration-instance class; value classification still needs an explicit contract. Consequently the complete ledger remains at 2,420 mismatches, with all 6,954 nodes reviewed. Other RFC-0001 verdicts were preserved while their Lean source hash was refreshed. Proof and provenBy source-integrity checks pass; this correction does not clear the separate proof or domain-class gaps.

RFC-0001 conditional diagnostic fix (2026-10-07)

Authored §6 requires a suggested fix when available. Lean statement b25 and its axiom justification now include that conditional field, and the claimValue list retains the same availability condition as claimText. This aligns the catalog with the existing authored rule; it does not require a fix for every diagnostic. Claim identity, subject, and provenance are unchanged. All 55 Lean catalog modules compiled, reference outputs regenerated, and projection drift, proof review, and provenBy source-integrity checks passed. The refreshed claim review matches; the ledger has 2,419 mismatches and no unreviewed nodes. This source agreement does not verify diagnostic production in the implementation.

RFC-0001 module cardinality summary alignment (2026-10-14)

Authored §5 rule 2 and the existing Lean M01060 diagnostic reject zero or more than one module declaration. The Lean invariant and RDF domain summary incorrectly shortened this to “zero or more,” including the valid one-module case. Root review classified the exact summary correction as routine alignment with the existing unequivocal contract under the program goal. It introduces no new syntax, diagnostic behavior, identity, or deployment migration.

Both maintained summaries now say “zero or more than one.” The owning generators compiled all 55 structured Lean RFC modules and regenerated the reference catalogs, domain Turtle, and diagnostic snapshot. The actual semantic diff replaces one domain summary triple and one reference sentence. All 57 emitted RFC/formal Turtle files are byte-identical; all 742 diagnostic definitions and the coverage report are unchanged. The diagnostic snapshot changes only the RFC-0001 source hash.

All 138 RFC-0001 projection reviews bind the changed Lean source hash while preserving unrelated findings and verdicts. The corrected whole node now matches, leaving 2,420 mismatches among 6,954 reviewed nodes and no unreviewed nodes. All twelve invoked generation and integrity gates passed. The actual 38-query comparison changes one governance invariant summary row; the other 37 result multisets, including all sixteen claim queries, are unchanged.

The implementation record links the exact source patch, command logs, regenerated-delta verification, and historical counterfactual in a compact hash-bound evidence record. Original typed paths and hashes are preserved; the later copies are not a final clean package. Strict release, 715 provenBy mismatches, parser conformance, upstream formal-model correction, and framework/site artifact cutover remain separate open requirements.

RFC-0001 grouped authored-clause alignment (2026-10-14)

The remaining fifteen RFC-0001 projection mismatches were audited together. Two were routine omissions from the existing authored contract: the optional action.backcompat summary incorrectly deferred authoring itself to Phase 1, and Lean statement b54 omitted the existing requirement that no-silent-coercion violations surface diagnostics. The summary now permits Q2 authoring while deferring prior-version validation; b54 now includes the diagnostic clause already present in authored §6, the RDF claim, and the Lean anti-pattern catalog.

The owning generators compiled all 55 structured modules and all twelve generation/integrity commands passed. The actual semantic delta replaces one domain summary triple and one emitted RFC statement-predicate triple; 56 other emitted Turtle catalogs remain byte-identical. All 38 actual query result multisets are unchanged. All 138 RFC-0001 source review hashes were refreshed; only the two related verdicts change. The b54 citation hash was refreshed while preserving its mismatch and finding. Diagnostic definitions and coverage remain unchanged; the separate 715 provenBy mismatches remain.

The ledger now has 2,418 mismatches among 6,954 reviewed nodes, with zero unreviewed. Thirteen RFC-0001 public identity/kind/class decisions remain pending in one exact batch proposal, including the measured query-consumer consequences. No candidate identity, ontology, or query change has been applied. The compact grouped evidence records the fifteen dispositions, real commands, before/after bindings, actual query comparison, unapplied candidate patch, and counterfactual impact.

RFC-0001 approved complete RDF batch (2026-10-14)

The owner approved the complete thirteen-node RDF/ontology/query batch in reply call359cf486. The exact reviewed patch was applied at source base c0abe3ed640b1fa0258b933d0f27848d671bb276, correcting nine claim subjects, one Permission kind, and three FieldChoice value identities. Four existing choice references move to the value IRIs, and five new DomainEntity scope nodes carry precise authoring/allocation scope without inventing DSL FQNs. The approved orphan-query classification and subjectFqn→subject output contract were applied with those identities.

Seventeen existing node hashes were refreshed, thirteen existing mismatch verdicts corrected, three review IRIs moved, and five new matching reviews added. Every unrelated review and the four already-matching choice-reference claim findings are preserved. The ledger now has 6,959 reviewed nodes, 2,405 mismatches, no unreviewed nodes, and no RFC-0001 projection mismatches.

Actual regenerated RDF exactly matches the approved 28-removed/71-added triple delta. All 38 actual query-delta comparisons match the reviewed counterfactual, including its six changed result multisets. Projection/review/link/claim-query and source-integrity checks pass. Existing Jena SHACL live and malformed-document fixtures pass using the retained bound local runtime. The strict domain-identity gate remains red on exactly the same 18 FQN and 21 kind-class conflicts as the source baseline; the separate 715 provenBy mismatches remain unchanged.

The implementation record links approval, actual typed records, and preserved counterfactuals. Publication, final clean packaging, framework/source-copy cutover, site pins, and formal-release gates remain separate requirements.

RFC-0003 grouped authored-clause alignment (2026-10-14)

Two stale claim literals now follow the existing authored contract. The Sensitive-field warning text restores §5a constraint 3’s by an active policy condition; Lean’s M03223 catalog retains the warning and runtime visibility requirement. The widget identified-by value now states stable identity id without treating typed prop references as part of identity. Its unchanged claim text retains the separate typed-prop requirement, matching authored §5 item 4 and the Lean Widget term; Lean b19 retains canonical identity lookup. No identity format or new enforcement rule is introduced.

The owning generator changes exactly those two claim triples. All 38 actual query result multisets and columns are unchanged. All 6,959 review rows are preserved except the two related node hashes and findings. The widget verdict now matches. The Sensitive-field claim keeps its mismatch because its existing domain/field/View/show subject has no authored domain owner; correcting text does not resolve that identity. The ledger has 2,404 global mismatches, 53 in RFC-0003, and no unreviewed nodes. RFC-0003 still has 42 unresolved claim references to 15 domain identities.

All six invoked projection/review/link/query commands exited 0; the RFC-0003 ownership command was its nonrelease inventory, not a strict release pass. The grouped actual record preserves controller failures, original logs, final review integrity, exact triple proof, and the complete query comparison. Domain and Lean sources, formal outputs, and proof ledgers remain byte-identical. Strict identity, provenBy, normative-release, final package, and publication gaps remain open.

The owner approved two separate batches, each applied once at source baseline f4d98a8f4bb9a1b6fda15444c14a426db615e5a1. Three RFC-0016 and ten RFC-0029 claim subjects now point to their existing authored invariant owners. The RFC-0004 orthogonality and policy non-circumvention invariants retain their aspect scope and also name the existing presentation-facet entity.

Actual owning-source regeneration produces exactly thirteen removed and fifteen added RDF triples. Fifteen related review rows change; eleven identity or scope verdicts now match. Every other review is preserved. The four RFC-0029 batch-support/cache semantic mismatches remain open. Current totals are 6,962 reviewed nodes, 2,308 mismatches, and zero unreviewed nodes. Unresolved claim-domain links decrease from 1,011 to 998, to 469 identities; RFC-0016 retains four unresolved references and RFC-0029 retains thirteen.

All 38 displayed query result multisets and columns are unchanged. Among fourteen complete relations checked without the terminal outer LIMIT, exclusions retain 359 rows with one corrected subject, and orphan claims decrease from 967 to 954 rows. The other twelve relations are unchanged. Projection/review/section/link/query/inventory checks pass. The nonrelease identity inventory still reports the inherited eighteen FQN and twenty-one kind-class conflicts; those strict release blockers are unchanged.

The actual adoption record contains source and emitted-RDF equality, exact deltas, complete query effects, and real gate logs. The current Site corpus parser also consumes these outputs. Pinned preview publication, downstream artifact repinning, framework Java consumer execution, Lean proofs, runtime conformance, and release acceptance remain separate gates; no earlier artifact acceptance is relabeled.

Approved RFC-0029 conditional batch scope (2026-10-16)

The owner approved the prepared three-line conditional-batch patch. The claim, domain summary, and Lean invariant now explicitly apply the ten-procedure limit and automatic splitting only if batch support is implemented, matching authored §8.6. Support itself remains SHOULD. The owning projection emitter changes exactly two RDF literals; no identity or numeric limit changes.

All 105 RFC-0029 review fingerprints were revalidated using the exact source delta and unchanged semantic inputs outside it. Only the batch claim’s verdict changes. The three cache-contract claims retain their mismatch verdicts and findings. Current totals are 6,962 reviewed nodes, 2,307 mismatches, and zero unreviewed nodes. Of 38 displayed query relations, only the invariant-summary relation replaces that literal; all fourteen complete relations checked without an outer LIMIT are unchanged.

The actual adoption record contains the exact source/RDF/query proof and passing available Python checks. It also records the concrete generated-reference hold: the owning all-55 Lean emitter still requires the known inconsistent external pin. reference/rfc-0029.md:58 remains stale until the corrected release/pin and owning emission are available. Retained formal RDF was used as query context; it is not relabeled as newly emitted. No native Lean pipeline, runtime batching fixture, package, consumer pin, or release acceptance is claimed for this partial regeneration.

RFC-0006 ClaimStatus regression condition restored (2026-10-16)

The adopted canonical RFC-0006 flow requires governing-policy permission and an explicitly declared reversible transition for a ClaimStatus regression. The claimstatus-monotone-default projection text previously named policy permission alone. Its one maintained claimText literal now retains both conditions from authored §7.1 and unchanged Lean b22/b25 catalog rules. The claim IRI, subject, kind, predicate, value, and section link remain unchanged; no new status, identity, transition rule, or proof is added.

Owning Python emission replaces exactly one RDF literal. The substantive review of that whole node now matches; all 6,961 unrelated review messages and every unrelated ledger byte are preserved. Current totals are 6,962 reviewed nodes, 2,306 mismatches, and zero unreviewed nodes. All 38 displayed query result multisets and columns and all fourteen complete relations without an outer LIMIT are unchanged. Projection drift, ClaimStatus contract, review integrity, claim query, and KG link checks pass.

The actual adoption record retains before source/RDF/review/query data, exact delta and ledger equality proofs, and real gate logs, including the first verifier’s blank-node-ID comparison failure. Narrative, Lean, generated reference/formal RDF, and proof inputs remain byte-identical. The RFC-0029 reference-generation hold, 715 citation mismatches, runtime conformance, consumer pins, and strict release acceptance remain separate open requirements.