@afokapu/atdd-bun 0.3.2 → 0.5.0

package/planner-nodes/ENFORCEMENT_SCOPE.yaml

@@ -2,27 +2,32 @@ schema_version: "1.0.0"
 package: "@afokapu/atdd-bun"
 node_corpus:
   source: "src/atdd/planner/conventions/nodes/"
-  count: 195
+  count: 196
   policy: >-
     Every node is shipped as canonical planner reference material. A node is not
     represented as enforced merely because it is present in this corpus.
 
-# A provider implementation must name every canonical rule it realizes. `coverage`
+# A provider implementation must name every canonical rule it realizes. `disposition` is
+# this package's enforcement, always strict: atdd-bun fails on every finding, whatever the
+# canonical node's own metadata says (the nodes are shipped verbatim). `coverage`
 # describes the Bun predicate actually exercised, not an assertion that the entire
 # prose convention has been ported.
 canonical_bun_enforcement:
   - rule_id: planner.train.naming
+    disposition: strict
     origin: schema-validator
     coverage: complete
     predicates:
       - train definitions and interlocking route targets use train:<subject>:<slug>
   - rule_id: planner.train.registry-coherence
+    disposition: strict
     origin: core-validator-port
     coverage: complete
     predicates:
       - every registry path resolves to a train document
       - every non-sidecar train document is registered
   - rule_id: planner.journey.continuation-closure
+    disposition: strict
     origin: bun-custom-validator
     coverage: complete
     predicates:
@@ -31,7 +36,15 @@ canonical_bun_enforcement:
       - continuation artifacts occur in the selected train sequence
       - continuation destinations resolve to interlockings
       - disconnected continuation or terminal sources are rejected
+  - rule_id: planner.journey.interlocking-composed
+    disposition: strict
+    origin: bun-custom-validator
+    coverage: complete
+    predicates:
+      - a plan that declares interlockings declares at least one journey
+      - every interlocking is a journey entrypoint or the destination of a continuation reachable from one
   - rule_id: planner.wagon.no-consume-cycle
+    disposition: strict
     origin: core-validator-port
     coverage: partial
     predicates:
@@ -39,6 +52,7 @@ canonical_bun_enforcement:
     unported:
       - multi-wagon strongly-connected-component detection
   - rule_id: planner.contract.registry-coherence
+    disposition: strict
     origin: core-validator-port
     coverage: complete
     predicates:
@@ -49,27 +63,32 @@ canonical_bun_enforcement:
       - registry identity theme matches its identity namespace
       - registry paths resolve to contract documents
   - rule_id: planner.theme.must-be-canonical
+    disposition: strict
     origin: bun-custom-validator
     coverage: complete
     predicates:
       - every declared theme belongs to plan/_themes.yaml
       - the package supplies no taxonomy besides reserved index 0
   - rule_id: planner.theme.theme-zero-mandatory
+    disposition: strict
     origin: bun-custom-validator
     coverage: complete
     predicates:
       - plan/_themes.yaml index 0 is commons
   - rule_id: planner.theme.urn-namespace-matches
+    disposition: strict
     origin: bun-custom-validator
     coverage: complete
     predicates:
       - a themed wagon's produced identities begin with that theme
   - rule_id: planner.artifact-naming.theme-first-identity
+    disposition: strict
     origin: bun-custom-validator
     coverage: complete
     predicates:
       - artifact identity themes are declared in plan/_themes.yaml
   - rule_id: planner.wagon.urn
+    disposition: strict
     origin: bun-custom-validator
     coverage: partial
     predicates:
@@ -77,6 +96,7 @@ canonical_bun_enforcement:
     unported:
       - documented directory and file layout
   - rule_id: planner.wagon.urn-naming
+    disposition: strict
     origin: bun-custom-validator
     coverage: partial
     predicates:
@@ -84,6 +104,7 @@ canonical_bun_enforcement:
     unported:
       - verb-object preference
   - rule_id: planner.wagon.produce-consume-artifacts
+    disposition: strict
     origin: bun-custom-validator
     coverage: partial
     predicates:
@@ -91,6 +112,7 @@ canonical_bun_enforcement:
     unported:
       - complete required-field and URN-shape validation
   - rule_id: planner.wagon.features
+    disposition: strict
     origin: bun-custom-validator
     coverage: partial
     predicates:
@@ -98,6 +120,7 @@ canonical_bun_enforcement:
     unported:
       - complete feature-manifest coverage
   - rule_id: planner.wagon.telemetry-filesystem
+    disposition: strict
     origin: bun-custom-validator
     coverage: partial
     predicates:

package/planner-nodes/nodes/planner.journey.interlocking-composed.convention.yaml

@@ -0,0 +1,43 @@
+schema_version: 1.0.0
+rule_id: planner.journey.interlocking-composed
+kind: constraint
+status: active
+name: Every interlocking is composed into a journey
+statement: >-
+  A plan that declares interlockings must declare at least one journey, and every interlocking must be
+  reached by a journey: either as a journey's entrypoint interlocking or as the destination of a
+  continuation reachable from that entrypoint. An interlocking no journey reaches is a routing decision
+  with no stated trigger and no stated place in the product flow.
+rationale: >-
+  planner.journey.continuation-closure validates the journeys a plan declares, so a plan that declares
+  none, or leaves some interlockings outside every journey, passes it vacuously. The journey is where
+  the plan says what starts a routing decision and what happens after its train completes; without
+  this rule a decomposition can stop at interlockings and look complete while the end-to-end flow was
+  never decided.
+terms:
+  - term_id: composed_interlocking
+    text: >-
+      an interlocking that is the entrypoint of at least one journey, or the destination of a
+      continuation reachable from a journey's entrypoint.
+  - term_id: vacuous_topology
+    text: >-
+      a plan with interlockings and no journey. Every interlocking is reported, because none of them is
+      composed.
+implementation:
+  type: validator
+  ref: planner.static.validators.bun::journeyCompositionFindings
+metadata:
+  severity: 4
+  disposition: strict
+  introduced_in: 0.4.0
+validation:
+  family: closure
+  template: graph_route_space_closure
+  variant: planner_journey_composition
+  phase: CONFIRM
+  enforcement: confirm-blocking
+  subject_kind: interlocking
+  failure_evidence:
+    - interlocking_id
+    - journey_count
+    - reason