general

Author: denisecase

IDENTIFIERS.md

@@ -36,50 +36,58 @@ Identifiers are:
 - suitable for direct mapping to Lean theorem names
 
 Identifiers MUST NOT be renamed or repurposed.
-New identifiers MAY be added only in a new major version of EP.
+New identifiers MAY be added only in a new major version of this document.
+
+## Identifier Notes
+
+Each identifier MUST be followed by exactly one note.
+
+- The note MUST be expressed as a single bullet.
+- The bullet text MAY wrap across lines.
+- No additional bullets, sublists, or structural markers are permitted.
+- Notes are explanatory only and do not introduce additional requirements.
 
 ## Canonical Identifier List (Alphabetical, with Notes)
 
 EP.CONFORMANCE.AE.REQUIRED
 
-States that EP operates over Accountable Entities and their identity regimes.
+- States that EP operates over Accountable Entities and their identity regimes.
 
 EP.CONFORMANCE.SE.REQUIRED
 
-States that EP conforms to the Structural Explainability specification.
+- States that EP conforms to the Structural Explainability specification.
 
 EP.DEFINITION.CORE
 
-Defines Evolution Protocol as a structural framework for representing
-graph evolution over accountable entities.
+- Defines Evolution Protocol as a structural framework for representing graph evolution over accountable entities.
 
 EP.GRAPH.DEFINITION
 
-Defines the structural form of graphs in EP.
+- Defines the structural form of graphs in EP.
 
 EP.GRAPH.DELTA
 
-Defines structured, non-causal graph change records.
+- Defines structured, non-causal graph change records.
 
 EP.GRAPH.EVOLUTION
 
-Defines ordered graph histories connecting states via deltas.
+- Defines ordered graph histories connecting states via deltas.
 
 EP.GRAPH.STATE
 
-Defines immutable graph snapshots in an ordered history.
+- Defines immutable graph snapshots in an ordered history.
 
 EP.SCOPE.EXCLUSIONS
 
-Defines what EP explicitly does not specify.
+- Defines what EP explicitly does not specify.
 
 ## Cross-Artifact Consistency Rule
 
 Each identifier in this list MUST appear:
 
 - exactly once in SPEC.md
 - exactly once in CONFORMANCE.md
-- exactly once as a field in the Lean ConformanceEvidence structure
+- exactly once as a field in the Lean `ConformanceEvidence` structure
 - exactly once in the Lean requirements list
 
 Alphabetical order SHOULD be preserved across all artifacts.

SE_MANIFEST.toml

@@ -38,7 +38,7 @@ excludes = [
 [citation]
 cff = "CITATION.cff"
 preferred = "spec"
-bib_hint = "spec-ep-2025"
+bib_hint = "case2025-spec-ep"
 
 [traceability]
 identifier_map = "none"

SPEC.md

@@ -30,7 +30,7 @@ Some requirements describe what the substrate MAY represent,
 while others constrain how such representations MUST NOT be interpreted.
 
 Overlap between these classes is intentional:
-representation permissions do not imply explanatory commitment.
+representation permissions do not imply explanatory or normative commitment.
 
 ## Identifier Semantics and Stability