Deferred proof obligations
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.
RFC-0036 external-ID scope mismatch
Two additional source-bound reviews found that executable proof bodies used
global external-ID uniqueness from external AX-010. The authored RFC and graph
backend use the pair (kind, externalId) as the uniqueness key. The old
propositions did not mention kind; the no-reassignment proof also omitted a
deletion transition. Both bodies are now opaque deferred obligations, pending
the contract and formal-model decision in
EXTERNAL_ID_SCOPE_PROPOSAL.md.
RFC-0036deriv_d47cb6d1a00f: AX-010’s globalexternalIdAllocated(e, r, t)uniqueness has no kind argument or deletion transition. It does not prove the authored post-deletion no-reassignment rule, and it forbids reuse of the same external ID by another kind.RFC-0036deriv_89cd18bae843: The proposition quantifies overExternalIdbut never mentionsResource.kind. It does not faithfully formalize uniqueness of the authored(kind, externalId)pair.
Two hundred thirty-two no-sorry theorem bodies were reviewed and found to prove propositions
weaker than their RFC headings. They are now explicit opaque obligations with
sorry in the source fragments; no claim-specific proof is asserted.
The first forty-six findings are individual source reviews, including the
original eleven from the prior source-hashed ledger. The remaining one hundred
eighty-six record thirty-six reviewed repeated propositions.
RFC-0042deriv_836d975692dd: The RFC heading requires authentication when requiresAuth is true, but the Lean proposition only derives authorized from the existence of a granting capability. It has no authentication predicate or requiresAuth condition.RFC-0042deriv_8edf54e0fac5: The RFC heading requires rejection of resourceId without resourceKind, but the Lean proposition only asserts that every Resource has a nonempty kind. It does not represent policy declaration fields or diagnostic M42010.RFC-0020deriv_648a5c486464: The RFC heading requires an overflow diagnostic before event loss, but the proposition only says that an input not accepted faithfully is rejected with a diagnostic. It has no subscription queue, overflow condition, event loss, or ordering of the diagnostic before loss.RFC-0020deriv_5cc185aba021: The RFC heading forbids agent subscriptions from widening read scope beyond declared permissions, but the proposition only derives the existence of a granting capability from generic authorization. It represents neither subscription scope nor declared permissions.RFC-0020deriv_cc6eabcc2a57: The RFC heading requires an open-time check for query entity kinds, but the proposition only derives a granting capability from an already authorized generic operation. It represents no subscription-open event, query kinds, or check outcome.RFC-0042deriv_aadfeb916f33: The heading requires at least one of the declared requiresRoles, but the proposition only derives a capability grant from generic authorization. No role or declared role set appears in the proposition.RFC-0042deriv_70c72fa0e14b: The heading requires invalidation for each of four documented permission-cache triggers, but the proposition only derives eventual invalidation when an input of an arbitrary cache is mutated. It does not identify any of the four triggers or require their coverage.RFC-0042deriv_ec232556eedd: The heading forbids trusting a permission cache for write-side decisions, but the proposition only states eventual invalidation of a cache after an input mutation. The quantified operation is unused, and no write decision or cache read is represented.RFC-0042deriv_d91b51e0c0f0: The heading names four permission-cache invalidation triggers, but the proposition only covers mutation of an input of an arbitrary cache and eventual invalidation. It has no representation or exhaustive coverage of the four trigger conditions.RFC-0042deriv_2de3e1eb2c4d: The heading requires policy-chain re-evaluation inside a write transaction, but the proposition only derives a granting capability from an already authorized operation. It has no write transaction, policy chain, or re-evaluation predicate.RFC-0042deriv_8a8b64e732c3: The heading forbids caching when-expression results across requests, but the proposition only states eventual invalidation after an input mutation. It has no when-expression results, request boundaries, or cross-request cache reuse.
Reused generic emission proposition
These 19 bodies all used emit r i t1 = emit r i t2, which says only that
a generic rule emits the same result at two times for one input. Each
claim needs additional conditions or outputs absent from that proposition.
RFC-0000deriv_0d0c8d3b9f2e: The proposition only asserts time-invariant generic emission and does not represent compiler versions, code meanings, or major-version exception.RFC-0000deriv_5ee603359b5c: The proposition only asserts time-invariant generic emission and does not represent MCP transport, severity, or source mapping fidelity.RFC-0002deriv_cc7565f9e89b: The proposition only asserts time-invariant generic emission and does not represent duplicate suppression or an at-most-once emission condition.RFC-0003deriv_cef856ba3d04: The proposition only asserts time-invariant generic emission and does not represent unused views, route generation, or M03220.RFC-0004deriv_a113ced8d6b9: The proposition only asserts time-invariant generic emission and does not represent aspect conflicts, precedence outcomes, or required diagnostic content.RFC-0005deriv_93ac2e947f9d: The proposition only asserts time-invariant generic emission and does not represent cross-module rollback, rejection, or actionable diagnostics.RFC-0017deriv_533efd614b8d: The proposition only asserts time-invariant generic emission and does not represent LSP/compiler interface parity or code-namespace equality.RFC-0018deriv_23755e558141: The proposition only asserts time-invariant generic emission and does not represent compiler-session and CLI outputs for identical inputs.RFC-0021deriv_338bf47e61e4: The proposition only asserts time-invariant generic emission and does not represent M21xxx violation classes or replacement of M01603.RFC-0031deriv_a4c887949ad1: The proposition only asserts time-invariant generic emission and does not represent missing introspection fields or M31103.RFC-0031deriv_0173b67b4e0e: The proposition only asserts time-invariant generic emission and does not represent executable SDL syntax or M31104.RFC-0037deriv_09263dcd0ae3: The proposition only asserts time-invariant generic emission and does not represent private error semantics or equality across implementations.RFC-0039deriv_f1d3cdd9f47a: The proposition only asserts time-invariant generic emission and does not represent cross-module visibility or M39003 at compile time.RFC-0040deriv_e42f69f54bea: The proposition only asserts time-invariant generic emission and does not represent manifest hashes or deterministic compilation output.RFC-0041deriv_a8df464e532e: The proposition only asserts time-invariant generic emission and does not represent graph mutations or install-pipeline input equality.RFC-0043deriv_9bb6aabcb8a3: The proposition only asserts time-invariant generic emission and does not represent idempotency.requiredKey or rejection with M43010.RFC-0044deriv_2c4185b5ad0b: The proposition only asserts time-invariant generic emission and does not represent transform cache keys or their source/parser/profile/projector inputs.RFC-0049deriv_7f9490a8d40e: The proposition only asserts time-invariant generic emission and does not represent query side effects or rejection of non-projective bodies.RFC-0050deriv_0760d2e76d2a: The proposition only asserts time-invariant generic emission and does not represent user-namespace resource/statement effects or M50012.
Reused generic sensitive-declaration approval proposition
These thirteen bodies all stated that a sensitive declaration has a human approval record. Each heading requires a more specific trigger, actor, artifact, or workflow than that proposition represents.
RFC-0001deriv_2e1600a73627: The proposition covers a human approval record for a generic sensitive declaration; it does not represent diagnostic emission or policy-review audit content.RFC-0002deriv_7be85c354c89: The proposition covers a human approval record for a generic sensitive declaration; it does not represent alter migrations, removed columns, or the install-plan diff.RFC-0008deriv_dab99961b435: The proposition covers a human approval record for a generic sensitive declaration; it does not represent agent capability declarations, a review step, or deployment ordering.RFC-0009deriv_c450d497e7dd: The proposition covers a human approval record for a generic sensitive declaration; it does not represent AI authorship, review before marking approved, or install-plan state.RFC-0009deriv_118169b717e0: The proposition covers a human approval record for a generic sensitive declaration; it does not represent AI actors, final decisions, or high-authority actions.RFC-0009deriv_b1f67c8379d2: The proposition covers a human approval record for a generic sensitive declaration; it does not represent agent declarations, activation, or non-development environments.RFC-0010deriv_8539c1993425: The proposition covers a human approval record for a generic sensitive declaration; it does not represent model proposals, a confirmation surface, or conversion to high-authority commands.RFC-0011deriv_5f64ca5c27f8: The proposition covers a human approval record for a generic sensitive declaration; it does not represent annotation aspects, governance modules, or parity with policy install-plan review.RFC-0016deriv_dcd50a8db81e: The proposition covers a human approval record for a generic sensitive declaration; it does not represent MAJOR breaking migrations or approval before apply.RFC-0016deriv_1d14af087baa: The proposition covers a human approval record for a generic sensitive declaration; it does not represent RemoveField or RemoveEntity operations and their RFC-0005 approval workflow.RFC-0016deriv_aafc2aa86445: The proposition covers a human approval record for a generic sensitive declaration; it does not represent removeField, changeType, or removeEntity workflows.RFC-0050deriv_7c8fefa81b7d: The proposition covers a human approval record for a generic sensitive declaration; it does not represent db.graph.unrestricted manifest declarations or manual review.RFC-0054deriv_60500b7c03d8: The proposition covers a human approval record for a generic sensitive declaration; it does not represent PR tagging, destructive operations, or explicit signoff.
External manifest-name axiom mismatch
Ten additional inherited bodies failed Lean compilation because external
AX-034 concludes project.aion while the authored Gnomon contract requires
project.gnm. Their original bodies were replaced with explicit deferred
obligations in the per-RFC fragments. This preserves the normative statements
and permits a compile-only audit; it does not prove them. The affected entries
are:
- RFC-0001
deriv_30bdca51eda7 - RFC-0002
deriv_2407d9a640ef - RFC-0008
deriv_3ede6542e8eb,deriv_7730cf1db969,deriv_7812282a2c9c - RFC-0017
deriv_eea6e9b4a3fc,deriv_caefe290cd94 - RFC-0030
deriv_fba532cac87e - RFC-0040
deriv_17d046b63567 - RFC-0054
deriv_96d02b1408b0
Some headings demand more than a manifest filename, such as an LSP action or DDL ordering. A corrected AX-034 alone will not prove those full claims; each replacement proof must also pass semantic review.
Reused authorization-to-capability proposition
These thirteen bodies all proved only that an already authorized operation has a granting capability. That proposition does not specify when an operation must be authorized, how checks are enforced, or when rejection must occur. The missing semantics for each RFC claim are:
RFC-0000deriv_8a929553f510: No principal taxonomy or implicit-trust rule is represented.RFC-0001deriv_b5aede494144: No authorization declaration, compiler output, or enforceable runtime contract is represented.RFC-0003deriv_67e554762fed: No composition path or operation/policy bypass is represented.RFC-0003deriv_d40c19b25f82: No compiler handling of action-level authorization in view declarations is represented.RFC-0005deriv_190d341e8be5: No rollback operation or forward-only policy constraint is represented.RFC-0006deriv_6d8a136d0d73: No AI actor, claim state transition, or flow-level authorization is represented.RFC-0009deriv_63930be87f25: No agent capability scope or runtime boundary check is represented.RFC-0015deriv_cb6e8549e1e2: No pre-write target check, asserted-to-inferred escalation check, or terminal-state guard is represented.RFC-0015deriv_40d2340aaab7: No self-escalation through registry writes, rule injection, or derived authorization values is represented.RFC-0033deriv_0552d6d59f86: No unauthenticated request,auth.requiredsetting, handler invocation, or rejection order is represented.RFC-0034deriv_b09b691a096c: No unauthenticated request or pre-handler rejection is represented.RFC-0040deriv_ddfff7df813e: No token scope or cross-scope resolution is represented.RFC-0043deriv_3fb135009362: No conjunction of auth, roles, permissions, and policy checks or rejection before effects is represented.
Reused generic cache-invalidation proposition
These twelve bodies prove only AX-017’s statement that mutation of an input to an arbitrary cache eventually causes some invalidation. The proposition neither identifies the RFC-specific cache and trigger nor establishes timing, absence of invalidation, deletion, re-resolution, or backend behavior.
RFC-0005deriv_d2dbba6e733e: Does not prohibit invalidation when model digest and template version are unchanged.RFC-0005deriv_d7d8bf989a4a: Does not identify model-digest keys, delete all prior entries, or order deletion before kernel activation.RFC-0005deriv_5836e6990e99: Does not identify promptTemplate versions or delete all entries under the prior version.RFC-0005deriv_8872389ad572: Does not represent rollback, co-existing new-install entries, or a prior-install kernel artifact.RFC-0030deriv_126eaaa54bc7: Does not represent current lockfile entries or prohibit registry queries.RFC-0030deriv_03250b0167b6: Does not represent transitively imported proto changes or the specific lockfile entry.RFC-0036deriv_996abc2ca68a: Does not identify PermissionCache, policy or Statement changes, or their input relationship.RFC-0036deriv_6b6af6d72dac: Does not represent write-side permission decisions, re-evaluation, or locking.RFC-0039deriv_05b7d2f6cfd4: Does not represent cache misses or backend round trips.RFC-0039deriv_87ed06dcd98f: Does not represent lookup keys, per-execution caching, or invalidation at execution end.RFC-0046deriv_7e10cb68c890: Does not represent override-file change detection or re-resolution of flag-marked configuration.RFC-0046deriv_5640244a5b64: Does not represent TTL expiry, secret resolution, or re-resolution after invalidation.
Reused generic live-reference proposition
These ten bodies prove only AX-018’s statement that the target of an already live generic reference is alive. The proposition does not establish the specific lookup, validation phase, diagnostic, or deletion constraint in the corresponding RFC heading.
RFC-0001deriv_ed2025086741: Does not represent compile-time cross-reference resolution.RFC-0001deriv_ea63534ad8e6: Does not represent manifest paths, .gnm file existence, or M01064.RFC-0003deriv_19634c26f810: Does not represent route.page, page.layout, or layout-region identifier resolution.RFC-0005deriv_e0862f779701: Does not represent model registration before agent activation.RFC-0005deriv_ed4f6acbcb50: Does not represent compiler emission of M05046 at agent activation.RFC-0007deriv_77c482f87e1b: Does not represent a kind drop or a pre-drop live-instance check.RFC-0013deriv_7e2bc5080da5: Does not represent EntityKind declarations or scope in a given block.RFC-0033deriv_7bd5438e0811: Does not represent exposes lists, operation kinds, or declaration lookup.RFC-0036deriv_e39d62db8c33: Does not prohibit predicate deletion while Statements reference it.RFC-0036deriv_be6b39991f8c: Does not represent Statement subjectId/objectId, insertion time, or non-deleted Resource targets.
Reused generic capability-to-authorization proposition
These eight bodies prove only AX-040’s implication from an existing capability grant to generic authorization. The proposition neither requires the listed runtime checks nor constrains when an operation or projection can execute.
RFC-0000deriv_d27857c6f844: Does not represent agent mutations or parity with human policy constraints.RFC-0000deriv_ed3637edf254: Does not represent execution tools, RFC-0005 boundaries, mutation effects, or check ordering.RFC-0007deriv_2559dcdf73f8: Does not represent AI actors, claim fields, or a declared permissions-block action.RFC-0010deriv_2ee9dd655d67: Does not represent kernel enforcement of RFC-0005/0009 policies before committed events.RFC-0015deriv_afca1c98b8cd: Does not represent agent writes, declared permissions, or pre-write enforcement at the object graph.RFC-0022deriv_5b12fccc97fa: Does not represent workflow triggers, underlying actions, or rejection before workflow execution.RFC-0049deriv_d5b4dfef2a1b: Does not represent query carrier projections or principal-scoped result filtering.RFC-0049deriv_ee1153388b2a: Does not represent source projections, predicate policies, or exclusion of unreadable gnomons.
Reused principal-existence proposition
These seven bodies prove only that the total principalOf function returns a
Principal for each Operation. This does not establish auditability, persisted
attribution, declared actors, tenant boundaries, or stable anonymous identity.
RFC-0005deriv_96196dd445e9: Does not represent an audit record for policy-affecting operations.RFC-0013deriv_b1dc3982f6f3: Does not represent a required actor field or its declared principal kind.RFC-0038deriv_dbc760039db1: Does not represent writes, active principals, or persisted creatorId.RFC-0043deriv_2c22a000267a: Does not represent tenantBoundaryRef declarations.RFC-0048deriv_22ca2b5f5f99: Does not represent principalId, tenantId, or authMethod audit fields.RFC-0048deriv_243cea557b8e: Does not represent anonymous identity or stability across restarts.RFC-0050deriv_9ccf165d40e9: Does not represent install-time gnomons or module.installed_by/principal.created_by emission.
Reused lineage-existence proposition
These seven bodies prove only that each DerivedEntity has some Lineage. The proposition does not constrain lineage contents or connect the specific RFC artifact to a source, rule, actor, or template invocation.
RFC-0002deriv_9d09e8041b62: Does not represent canonical identity metadata on compiled objects.RFC-0007deriv_445cda53ee3e: Does not represent source gnomons or derivation rule version in lineage.RFC-0007deriv_8f952f0aa69d: Does not represent optional lineage-reference fields such as source, rule/model, confidence, time range, or supersession chain.RFC-0007deriv_1ff7c4a28441: Does not represent source gnomons or the derivation rule in lineage.RFC-0010deriv_ba042df97140: Does not represent extracted symbols or source spans.RFC-0049deriv_79bab2019e88: Does not represent mutations or provenance for each gnomon they create.RFC-0050deriv_c29fd37c98cb: Does not represent nested template calls or template.instantiated_from.
Reused file-class equality proposition
These seven bodies prove only that two declarations already contained in a file have the same declaration class. This is an at-most-one-class property; it does not establish a nonempty file, a required declaration kind, or the compiler diagnostics in the RFC headings.
RFC-0001deriv_b04a567a184f: Does not require an objects file to be nonempty or contain a permitted kind, or produce M01052.RFC-0001deriv_3502645875a5: Does not represent cross-file references, extraction of a supporting declaration, or M08702.RFC-0001deriv_9d338b29f249: Does not require a nonempty file or emit M08701 for mixed classes.RFC-0006deriv_4faeb51cf296: Does not represent domain concepts or the declared-kind taxonomy.RFC-0008deriv_90ff4996101b: Does not require a file to contain any declaration, so it establishes at most one class rather than exactly one.RFC-0024deriv_f7eb6e85ef93: Does not represent client operations {} and spec: fields or their mutual exclusion.RFC-0033deriv_ee641f9dd571: Does not represent api declarations, invalid file classes, or M08701.
Reused expression-type existence proposition
These seven bodies prove only that the total expressionType function returns
some GnomonType. The proposition does not constrain that type or establish
the compiler checks required by the RFC headings.
RFC-0013deriv_e16e19a54f51: Does not represent then-block membership or boolean-valued expressions.RFC-0021deriv_985b1ca67974: Does not prove transform termination or output-type correctness for every input.RFC-0021deriv_d3a2f3bdbdfd: Does not represent flow-sensitive inference or conditional-branch narrowing.RFC-0021deriv_40a6635ac05f: Does not represent nullable inputs or explicit null handling.RFC-0021deriv_2e19628fec49: Does not prove assignability to a new field type or compiler verification.RFC-0022deriv_f3b434ff6442: Does not represent sequential/parallel composition or step-to-step data-flow type checks.RFC-0029deriv_adeaea03fae4: Does not represent procedure outputs, Promise stripping, or inferred return extraction.
Reused generic boundary-fidelity proposition
These six bodies prove only that a generic boundary input is accepted faithfully or rejected with some diagnostic. The proposition does not identify the RFC-specific input, condition, coercion, error policy, or code.
RFC-0002deriv_2c94bf55eaa8: Does not identify compiler policy declarations or prove they cannot be silently dropped.RFC-0004deriv_b79ddf3562af: Does not identify missing referenced fields or diagnostic M04311.RFC-0022deriv_2283f88bd089: Does not represent failed sub-agent steps, data corruption, an error policy, or its compile error.RFC-0023deriv_f820568a8a9c: Does not represent Studio degradation or notification to the author.RFC-0036deriv_fa23b228128e: Does not represent JSON null fields or the required coercion/rejection rule at the API boundary.RFC-0036deriv_762897ca0345: Does not prohibit literal null data in Resource or Statement or require M36040.
Reused status-setter identity proposition
These six bodies prove only that the status of a formal Declaration was set by an actor classified as its writer. They do not establish the instance state, source classification, authoring metadata, or review timing in the RFC claims.
RFC-0007deriv_b711d96ae7ec: Does not require instances to carry an allowed epistemic_status.RFC-0007deriv_5fbe7fc86fbb: Does not restrict AI-derived instance states or represent human adjudication.RFC-0007deriv_507dfb53a53f: Does not represent instance writes or prohibit separate post-hoc status derivation.RFC-0009deriv_0858c6c3e832: Does not represent authored_by: ai or model IDs in compiled bundles.RFC-0009deriv_d44cdaf6d99e: Does not require draft modifiers until human review or M09823.RFC-0010deriv_651de3b4395b: Does not represent migration tooling, confidence, normative emission, or author confirmation.
Reused no-AST-structure proposition
These five bodies prove only that a formal MeaningField has no AST structure.
The external isPlainProse predicate is defined as that negative property;
its axiom does not test readability, required fields, documentation format,
or reviewer comprehension.
RFC-0006deriv_0fe4ef24ba9e: Does not require a meaning field on each declared kind or establish nontechnical comprehensibility.RFC-0006deriv_6ef65c7199f2: Does not render a self-explanation covering fields, facets, states, actions, AI permissions, and provenance.RFC-0008deriv_142ea3ddb42b: Does not establish plain-language readability for a nontechnical domain author.RFC-0008deriv_ff9c27462a2c: Does not represent doc comments or CommonMark syntax.RFC-0009deriv_d61521cf40ba: Does not represent AI-actor definitions or reviewer-assessable terms.
Reused concept-field identity proposition
These five bodies prove only f.concept = conceptOf f; the external
fileNamedAfter predicate is defined by that equality. It does not inspect
an actual filename or its syntax.
RFC-0008deriv_db70d0c82886: Does not establish that the actual filename matches the defined concept.RFC-0008deriv_0e7a52f21662: Does not establish the .gnm extension.RFC-0008deriv_84f1ee00f8f4: Does not establish lowercase RFC 1123 labels or the 63-character limit.RFC-0033deriv_dc0048ceadd6: Does not represent api declarations, api.gnm filenames, or concept folders.RFC-0034deriv_9ecd0440132f: Does not represent serve declarations, serve.gnm filenames, or concept folders.
Reused value-type existence proposition
These five bodies prove only that every formal Value has some GnomonType. They do not constrain the type, forbid null, or demonstrate a compiler mapping.
RFC-0006deriv_71239e1945bc: Does not exclude null types, nullable modifiers, or null literals.RFC-0021deriv_e46c61ea5c96: Does not require arithmetic operands to be numeric.RFC-0021deriv_c2133a794b1e: Does not represent a coercion path or its compiler verification.RFC-0031deriv_40d9864c05aa: Does not map GraphQL types through the specified table.RFC-0043deriv_0f90ed28e1d7: Does not constrain a Resource state field to the workflow’s states.
Reused generic spec-conformance proposition
These five bodies restate that an implementation already labeled conforming implements an arbitrary artifact already in the spec. The antecedents do not identify the RFC-specific feature or prove its implementation.
RFC-0005deriv_ad4dd081671c: Does not represent install-plan entries or the typed operation taxonomy.RFC-0023deriv_58471598e8b1: Does not represent Studio CSP or nonconformance when CSP is absent or invalid.RFC-0023deriv_7ade18500f97: Does not establish the four required Studio panels or their reachability.RFC-0036deriv_29b645c914ba: Does not encode exact graph backend shapes.RFC-0047deriv_92b07f202ea9: Does not represent audit-log emitters or the §3.1 event schema.
Reused module-surface equality proposition
These four bodies prove only that two Modules with equal name and version have equal formal surfaces. The proposition does not identify the RFC’s FQN, artifact fingerprint, resolution inputs, or stable object IDs.
RFC-0001deriv_2747b5d4e9d5: Does not establish FQN uniqueness across installed modules or M01061.RFC-0010deriv_2b006916f517: Does not represent kernel artifacts, compiled bundle fingerprints, or matching version stamps.RFC-0014deriv_7744fae7bbf9: Does not represent module.gnm, module.lock, registry state, or resolution output.RFC-0041deriv_b86293e6ea3a: Does not represent stable object IDs or their derivation at install time.
Reused session-principal equality proposition
These four bodies prove only that an Operation already assigned to a Session has that Session’s principal. The proposition does not enforce identity claims, isolation, tenant context, or read-time scoping.
RFC-0005deriv_4af392355508: Does not establish transaction-context isolation between operations.RFC-0009deriv_4f5ca4c3f018: Does not compare the principal with a declared agent identity or reject spoofing with M09832.RFC-0038deriv_57554f777a1a: Does not propagate tenant context into the backend before reads and writes.RFC-0038deriv_5d411205a3ff: Does not represent read operations or enforce tenant binding on visible data.
Reused generic diagnostic-rejection implication
These four bodies prove only that a generic boundary input not accepted faithfully receives some diagnostic rejection. Their RFCs require a specific input condition, diagnostic identity, and sometimes termination.
RFC-0017deriv_6d71e600a163: Does not identify erroneous files or emit a diagnostic for each.RFC-0028deriv_59c8f47e8f80: Does not identify missing/invalid openapi versions, halt, or M28801.RFC-0044deriv_c8d607b5dd57: Does not identify unhandled formats, registered adapters, or M44020.RFC-0048deriv_480bd3b0e387: Does not identify unsupported inbound credentials or M48040.
Reused no-capability denial proposition
These four bodies prove only that an Operation without a granting capability is not formally authorized. They do not connect that condition to the RFC’s specified actor or request, nor prove an actual rejection response.
RFC-0006deriv_7801e3b5ef4d: Does not require AI action declarations or prohibit actions lacking one.RFC-0009deriv_f050f25442f7: Does not represent AI permissions blocks or prevent unlisted actions.RFC-0034deriv_f5da5b39b945: Does not represent request handling or a rejection response.RFC-0048deriv_50285e074c02: Does not represent missing tokens, anonymous-access policy, request rejection, or M48050.
Reused bitemporal query-kind proposition
These three bodies prove that each formal Boundary accepts some ReadOperation
of the asOf, validAt, and combined kinds. The operation-kind witnesses do
not specify time parameters, temporal filtering semantics, default qualifiers,
or mutation behavior.
RFC-0007deriv_648a10a42461: Does not establish append-only system_time rows or prohibit UPDATE/DELETE.RFC-0036deriv_0f0d67812786: Does not establish that query evaluation fixes system and valid time to the supplied parameters.RFC-0049deriv_cf6d8a19c135: Does not propagate qualifiers through source projections or supply the asOf(now()).validAt(now()) default.
Reused declared-home proposition
These three bodies prove only that a generic Concern is hosted by its declared home. The formal type does not identify the RFC-specific declaration class or forbidden nested content.
RFC-0003deriv_b62508d8828f: Does not exclude business logic, validation rules, or authorization predicates from view declarations.RFC-0006deriv_0c1f52653534: Does not forbid facets from defining state machines or overriding including-entity fields.RFC-0015deriv_39bd101aae71: Does not forbid bindings inside entity, flow, or policy blocks.
Reused session capability-witness proposition
These three bodies derive a capability for an already authorized operation in a session. They do not define agent permissions blocks, scope sets, or the security transition that each claim constrains.
RFC-0015deriv_d774153e6e24: Does not prevent prompt injection, indirect rule-triggered writes, or binding reconfiguration from acquiring write access beyond the agent permissions block.RFC-0048deriv_e2a83a2b8d11: Does not require fresh authentication to widen an attenuated session’s scopes.RFC-0048deriv_5f646ea02a98: Does not establish that session scopes are a subset of the bound principal’s scopes.
Reused bound-endpoint request-schema equality
These two bodies prove equality of request schemas for endpoints bound to one function. Neither proposition represents individual fields or their order.
RFC-0031deriv_236734a4133a: Does not preserve argument ordering from the schema declaration.RFC-0031deriv_c5877255c42e: Does not map required and optional arguments or preserve defaults in descriptions.
Reused same-file declaration-class equality
These two bodies transport a property between equal declaration classes in one file. The property is unconstrained and no RFC-specific syntax is represented.
RFC-0008deriv_2ba6244edd77: Does not require a meaning property on facet declarations.RFC-0008deriv_d324d85a9539: Does not restrict project.gnm to its project block.
Reused endpoint response-schema existence
These two bodies establish only that an endpoint has a response schema.
RFC-0015deriv_3d9e04a6a0bb: Does not validate model responses against an agent’s declared output types.RFC-0028deriv_469356b62da8: Does not select HTTP response statuses or construct the required union and optional void arm.
Reused nonempty opaque kind proposition
These two bodies show that Resource.kind is nonempty and opaque. The proposition does not identify compiled objects or semantic type declarations.
RFC-0002deriv_41d1dc142498: Does not establish compiled-object canonical path, namespace, or stable external identity.RFC-0007deriv_17bc52111a5d: Does not establish that an instance kind references a declared semantic type kind.
Reused synchronous-derivation determinism proposition
These two bodies derive determinism for a synchronous Declaration. They do not model planner inputs or method classifications.
RFC-0005deriv_55be840eab28: Does not establish deterministic plan generation for identical inputs.RFC-0007deriv_db9040231406: Does not restrict mode:sync to lightweight methods or exclude llm and embedding_model.
Reused permission-bit excluded middle
These two bodies establish only bitsValid b ∨ ¬bitsValid b. This tautological
classification does not impose runtime behavior for invalid values.
RFC-0036deriv_56406312a728: Does not reject out-of-range values or prohibit silent normalization.RFC-0036deriv_44b218969a30: Does not define the valid numeric set, defect response, or M36030 diagnostic.
Reused generic cache invalidation
These two bodies establish eventual invalidation of a generic cache after one input mutates. They do not describe the required refresh decisions.
RFC-0028deriv_674467740a30: Does not compare spec and lockfile hashes or constrain reparsing to hash changes.RFC-0046deriv_810e729aea92: Does not require long-lived operations to re-read configuration after rotation.
Reused request-schema existence
These two bodies establish only that an Endpoint has a request schema.
RFC-0028deriv_6ca9d85842ee: Does not create the body field or resolve its JSON content schema.RFC-0029deriv_f35a317eea31: Does not attempt static schema extraction for supported validator cases.
Reused reference-liveness implication
These two bodies establish that a Reference cannot be live when its target is not alive. Neither proposition describes compiler or write-path responses.
RFC-0002deriv_6f603f3c2c12: Does not emit diagnostics for unresolved references.RFC-0036deriv_55646b847801: Does not reject Statement creation with soft-deleted subjectId or objectId, or emit M36050.
Reused physical-artifact provenance
These two bodies rely on the external PhysicalArtifact type’s sourceModel string and definitionally false handAuthored predicate. They do not identify either RFC-specific artifact or validate its actual source.
RFC-0007deriv_8e8c2d3b017a: Does not enforce generation of projection tables from the logical model.RFC-0018deriv_0d544b467360: Does not prohibit a separate hand-edited property-registry document.
Reused bound-endpoint schema equality
These two bodies assert schema equality when two endpoints are already bound to one function. They neither construct bindings nor derive their schemas.
RFC-0030deriv_9656d76e7c51: Does not derive request fields and return type from proto message types.RFC-0034deriv_064cd392952d: Does not establish multiple serve declarations or protocol bindings for one api.
Reused generic storage-primitive witness
These two bodies select some StoragePrimitive for a state-persisting Operation. The proposition names neither claim evidence nor cached OpenAPI operations.
RFC-0010deriv_9863eae897a8: Does not select the installed storage manifest’s declared strategy for Claim evidence writes.RFC-0028deriv_0fe70cb3f48f: Does not use cached operations or emit M24421 when the spec is unreachable.
Reused PEG-expressibility predicate
The external predicate witnesses a PEG string by applying the opaque pegExpressionOf function to any Grammar; it does not validate the authored EBNF or a generated artifact.
RFC-0008deriv_fda6391a165c: Does not establish translation of the normative grammar without modification.RFC-0012deriv_f30f3f5b2d45: Does not extract a standalone PEG file or validate it in CI.
Individual claim mismatches reviewed after repeated groups
RFC-0000deriv_b6ca7a92fe79: Authorization via a capability does not represent compiler diagnostic meanings or version exceptions.RFC-0003deriv_72a657dea3ea: Generic boundary rejection does not export composition-layer identity metadata.RFC-0005deriv_9df6c037c4b7: Authorization and principal existence do not preserve policyAffecting in install-plan entries.RFC-0006deriv_5437a0c22a36: Generic lineage existence does not detect facet field-name conflicts or emit M06501.RFC-0006deriv_d34785ed1167: Type existence does not detect facet field-name conflicts or emit M06501.RFC-0007deriv_99914043204a: An implication with an impossible type-missing premise does not supersede duplicate identity or record lineage.RFC-0007deriv_0c125e52d7a9: Temporal query support and generic boundary behavior do not perform identity merge transitions.RFC-0007deriv_1dfc18b0fa63: Relation components do not perform identity merge transitions.RFC-0009deriv_c4f660b0b12e: Validation excluded middle and deterministic emission do not require human review before approval.RFC-0009deriv_5e90de876dca: Capability authorization does not require human review of AI-authored declarations.RFC-0009deriv_49776dd1d55b: A human principal on an authorized operation does not review an AI-authored declaration.RFC-0009deriv_a33591604dff: Writing-actor and capability witnesses do not enforce human-review ordering in an install plan.RFC-0009deriv_404b29ba4755: Generic lineage and cache invalidation do not enforce human review before approval.RFC-0010deriv_8bc31b978319: Effect-declaration excluded middle does not prevent unconfirmed low-confidence migration mappings from becoming normative.RFC-0015deriv_f2392d7f490f: Capability authorization does not constrain binding declaration placement.RFC-0016deriv_bbdc0f3f4195: Generic boundary behavior does not compare migration version bumps or emit M01610.
Further individual claim mismatches
RFC-0008deriv_8363b0716bab: Equality of File.concept with itself does not inspect or reject generic filenames. The conflicting file-name rules are recorded in the companion QA.RFC-0008deriv_6c8d4fe3e6b7: Equal concept fields do not establish module ownership for every .gnm file in a concept folder.RFC-0022deriv_24253a28c250: Type existence and generic deterministic emission do not resolve, type-check, or diagnose step input bindings.RFC-0028deriv_4129cc391808: Generic emission and boundary response do not detect input-source shadowing or emit M28803.RFC-0029deriv_0f94f5abfaaa: Provenance, emission, and Value type existence do not implement unresolved-schema fallback, M29900, JSON typing, or operation generation.RFC-0031deriv_9b65078b73e2: Generic deterministic emission does not validate introspection URLs or emit M31100.RFC-0036deriv_57f05c5f54f5: Covers only Resources, not Statements, and AX-006 constructs an all-member Workspace rather than checking runtime reachability.RFC-0036deriv_72ed3485bae5: Generic boundary response does not prohibit silent Statement deduplication.RFC-0036deriv_653dda9bf558: Reflexive equality does not define or enforce bitwise permission comparison.RFC-0036deriv_6fb0fab78ffc: Abstract deletedAt-field presence does not identify bitemporal traversal queries or projected Resource output.RFC-0036deriv_975f019870a0: Opaque DecimalString output existence does not validate decimal syntax or persisted encoding.RFC-0041deriv_a86a2c8ecd5a: Surface equality does not reject duplicate manifests or emit M41004.RFC-0043deriv_274efb0c7016: Effect excluded middle and deterministic emission do not reject mutating queries or emit M43011.RFC-0048deriv_f83ac9276824: Session principal equality does not filter capability resolution through active-session scopes.RFC-0048deriv_087b941caa0a: Equal principals for two operations do not forbid scope widening over a session lifetime.RFC-0049deriv_2cb3ff8cfd6e: A capability witness does not filter unreadable gnomons from an aggregate.RFC-0050deriv_7342e5065c7b: Effect excluded middle and concern placement do not require a template.compose wrapper.RFC-0050deriv_3cd9885e58db: Declaring-Module existence does not emit four required install-time relations.RFC-0054deriv_dd9a4dbfa5d8: A Relation subject does not constrain cross-module foreign keys or require graph.statement relations.