gnomonlearn
Docs/RFC-0036 soft-delete shape conflict

RFC-0036 soft-delete shape conflict

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 §9.1 says every entity type except Predicate carries deletedAt. Its §6.2–§6.4 persisted shapes omit that field from PermissionCache, ResourcePolicy, StatementPolicy, and ExternalLink. The Lean catalog’s Graph entity definition includes all four types. The RDF claim RFC-0036/sec-9/all-but-predicate-have-deletedAt repeats the absolute rule, so its source-bound verdict is a mismatch until the authored contract is reconciled.

Limit §9.1’s required deletedAt field to Resource, Statement, and Workspace. Treat PermissionCache as an evictable derived record, policy rows as mutable configuration with isActive, and ExternalLink as an integration record with enabled. Their lifecycle rules should remain explicit in §6 or their owning RFCs. Keep Predicate deletion constraints separate. Update the RDF claim to name the three soft-deletable entity types, and update Lean’s soft-delete summary and generated projections together.

The alternative is to add deletedAt to all four §6 shapes and implement soft deletion for each backend and API. That would change persisted schemas and policy/cache semantics for a contract whose current shapes do not expose the field.

Acceptance criteria

  1. The authored §6 shapes and §9 rule use one consistent set of types.
  2. Lean and the RDF claim state the same set; projection reviews and emitted Turtle are regenerated from source.
  3. Backend schemas and query filters implement the chosen lifecycle, with tests for default reads and explicit historical inclusion where applicable.
  4. The release gate confirms no stale absolute claim remains.