RFC-0043 · Reference catalog
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.
Generated reference catalog. This page renders structured Lean data for RFC-0043: defined terms, diagnostics, dependencies, and invariants. It does not establish proof coverage or runtime conformance. The authored narrative lives in
RFC-0043.This page is generated from the
lean/Gnomon/Spec/module for RFC-0043. Edit that source and regenerate this catalog.
Title: Graph Operations
Status: draft
Owners: Module Platform, Runtime
Diagnostic range: M43000-M43099
Depends on: RFC-0001, RFC-0006, RFC-0007, RFC-0008, RFC-0010, RFC-0024, RFC-0033, RFC-0036, RFC-0037, RFC-0038, RFC-0039, RFC-0040, RFC-0042, RFC-0048
Proof citations in source: 13 / 13. Standalone proof verification is pending.
Definitions
| Term | Meaning |
|---|---|
| Conflict policy | The runtime’s behavior on concurrent-mutation conflicts. Currently only fail_fast is defined. |
| Effect pipeline | The ordered list of effect steps that the operation executes within a single transaction. |
| Effect step | One typed action in the operation’s pipeline. Nine kinds defined in §5. |
| Guard | A pre-flight policy expression that must evaluate true; if false, the operation is rejected with the configured error. |
| Operation | A declarative, typed runtime-callable unit. Has input schema, output schema, transport kind, authorization, and an effect pipeline. |
| Transport | The semantic kind of operation: query (read-only) or mutation (state-changing). |
| Workflow | An optional state machine declaration that constrains operation invocations to declared transitions. |
Diagnostics
| Code | Severity | Description |
|---|---|---|
M43010 | Error | Mutation operation does not declare idempotency.requiredKey: true |
M43011 | Error | Query operation contains a mutating effect kind |
M43020 | Error | tenantBoundaryRef cannot be resolved at request time |
M43021 | Error | inputSchemaRef or outputSchemaRef does not resolve |
M43030 | Error | Effect pipeline exceeds the 20-step limit |
M43031 | Error | Forward reference between effect steps detected |
M43032 | Error | Effect step fails its kind-specific schema validation |
M43033 | Error | Effect-step key collision: two steps declare the same key |
M43040 | Error | Workflow transition originates from a declared terminal state |
M43041 | Error | Workflow declared on a query operation |
M43042 | Error | Subject Resource’s current state is not in the workflow’s states set |
M43043 | Error | Workflow transition’s effectKeys references a non-existent step |
M43050 | Error | Operation invocation: operation FQN not registered in this runtime |
M43051 | Error | Operation invocation: input exceeds maxPayloadBytes |
M43052 | Error | Operation invocation: completed within timeoutMs exceeded |
M43060 | Warning | Operation declares both requiresPermissions and policy.preset; verify intended conjunctive semantics |
M43061 | Warning | Operation has no errorCatalogRef; failures will return generic error class |
Dependency neighborhood
graph LR
nRFC_0043["RFC-0043"]
nRFC_0001["RFC-0001"]
nRFC_0043 --> nRFC_0001
nRFC_0006["RFC-0006"]
nRFC_0043 --> nRFC_0006
nRFC_0007["RFC-0007"]
nRFC_0043 --> nRFC_0007
nRFC_0008["RFC-0008"]
nRFC_0043 --> nRFC_0008
nRFC_0010["RFC-0010"]
nRFC_0043 --> nRFC_0010
nRFC_0024["RFC-0024"]
nRFC_0043 --> nRFC_0024
nRFC_0033["RFC-0033"]
nRFC_0043 --> nRFC_0033
nRFC_0036["RFC-0036"]
nRFC_0043 --> nRFC_0036
nRFC_0037["RFC-0037"]
nRFC_0043 --> nRFC_0037
nRFC_0038["RFC-0038"]
nRFC_0043 --> nRFC_0038
nRFC_0039["RFC-0039"]
nRFC_0043 --> nRFC_0039
nRFC_0040["RFC-0040"]
nRFC_0043 --> nRFC_0040
nRFC_0042["RFC-0042"]
nRFC_0043 --> nRFC_0042
nRFC_0048["RFC-0048"]
nRFC_0043 --> nRFC_0048
Invariants
- An operation’s effect pipeline MUST contain between 1 and 20 steps. (enforced by: compile-time)
- Authorization is conjunctive across requiresAuth, requiresRoles, requiresPermissions, and policy. (enforced by: runtime)
- Every mutation operation MUST declare idempotency.requiredKey: true. (enforced by: compile-time)
- Every operation MUST declare a tenantBoundaryRef resolvable at request time. (enforced by: compile-time + runtime)
- Every operation invocation MUST produce an audit log entry per RFC-0047. (enforced by: runtime)
- Forward references between effect steps MUST be rejected at compile time. (enforced by: compile-time)
- Idempotency results are persisted and looked up per (operation FQN, tenantId, principalId). (enforced by: runtime)
- Query operations MUST NOT contain any mutating effect kind. (enforced by: compile-time)
- Query operations MUST NOT declare workflows. (enforced by: compile-time)
- Workflow transitions originating from a declared terminal state MUST be rejected at compile time. (enforced by: compile-time)
Normative Statements
Statements are structured source data. Proof citations, where present, have not passed a standalone Gnomon proof gate.
Authorization
- MUST — Authorization checks (auth, roles, permissions, policy) apply conjunctively; failure rejects the operation before any effect executes. (proof citation:
rfc0043_b10_grounded; verification pending)
Compatibility and Migration
- MUST — The runtime MUST reject inputs exceeding maxPayloadBytes (default 262144). (proof citation:
rfc0043_b1_grounded; verification pending)
Compile and Runtime Pipeline
- MUST — The error type returned MUST match the failure cause per the runtime invocation step table. (proof citation:
rfc0043_b29_grounded; verification pending)
Effect Pipeline
- MUST — Forward references between effect steps MUST be rejected at compile time (M43031). (proof citation:
rfc0043_b19_grounded; verification pending) - MUST — effects MUST contain between 1 and 20 steps; longer pipelines must be decomposed (M43030).
Guards and Conflict Policy
- MUST — Future conflict policies MUST preserve fail_fast semantics for backward compatibility.
Idempotency
- MUST — Every mutation operation MUST declare idempotency.requiredKey: true.
- MUST — The runtime MUST persist idempotency-key results for the duration governed by RFC-0046 (default 24 hours).
- MUST — The runtime MUST refuse to execute a mutation without an idempotency key.
Invariants
- MUST — Every operation invocation produces an audit log entry. (proof citation:
rfc0043_b23_grounded; verification pending)
Operation Declaration
- MUST — A mutation operation without idempotency.requiredKey: true MUST be rejected at compile time (M43010). (proof citation:
rfc0043_b25_grounded; verification pending) - MUST — A query operation containing any mutating effect MUST be rejected at compile time (M43011). (proof citation:
rfc0043_b13_grounded; verification pending) - MUST — Every operation MUST declare tenantBoundaryRef. (proof citation:
rfc0043_b15_grounded; verification pending) - MUST — Operations whose tenant boundary cannot be resolved at request time MUST be rejected with M43020 before any effects execute. (proof citation:
rfc0043_b5_grounded; verification pending) - MUST_NOT — Query effects MUST NOT mutate graph state. (proof citation:
rfc0043_b17_grounded; verification pending)
Workflow State Machine
- MUST_NOT — Query operations MUST NOT declare workflows (M43041). (proof citation:
rfc0043_b21_grounded; verification pending) - MUST — The state field on the subject Resource MUST be a typed value matching the workflow’s states set. (proof citation:
rfc0043_b8_grounded; verification pending) - MUST — Transitions FROM a terminal state MUST be rejected at compile time (M43040). (proof citation:
rfc0043_b3_grounded; verification pending)
Linked References
| Direction | Target |
|---|---|
| Depends on | RFC-0001 |
| Depends on | RFC-0006 |
| Depends on | RFC-0007 |
| Depends on | RFC-0008 |
| Depends on | RFC-0010 |
| Depends on | RFC-0024 |
| Depends on | RFC-0033 |
| Depends on | RFC-0036 |
| Depends on | RFC-0037 |
| Depends on | RFC-0038 |
| Depends on | RFC-0039 |
| Depends on | RFC-0040 |
| Depends on | RFC-0042 |
| Depends on | RFC-0048 |