@afokapu/atdd-bun 0.1.0

package/planner-nodes/nodes/planner.artifact-naming.separator-semantics.convention.yaml

@@ -0,0 +1,42 @@
+schema_version: 1.1.0
+rule_id: planner.artifact-naming.separator-semantics
+kind: family
+status: active
+name: Separator semantics (colon vs dot)
+statement: Colon means hierarchical descent (unlimited depth); dot means lateral variation (keep shallow).
+source:
+  legacy_path: src/atdd/planner/conventions/artifact-naming.convention.yaml
+  legacy_section: separator_semantics
+  legacy_sha: eca68a67c92694c9
+  extraction_mode: high_fidelity
+parity:
+  source_fragments_preserved: true
+  examples_preserved: true
+  implementation_preserved: false
+  fix_hint_preserved: false
+  reviewed_at: '2026-06-16'
+terms:
+- term_id: colon
+  label: 'Colon ( : )'
+  text: hierarchical descent — navigate deeper into the resource tree.
+  values:
+    purpose: Hierarchical descent
+    multiplicity: Unlimited
+    visual_weight: Strong boundary - different conceptual levels
+  examples:
+    positive:
+    - commons:ux:foundations:color
+    - scenario:catalog:primitives:actor
+- term_id: dot
+  label: Dot ( . )
+  text: lateral variation — different flavors/states of the same thing.
+  values:
+    purpose: Lateral variation
+    multiplicity: Typically 1, rarely 2
+    visual_weight: Soft boundary - same level, different facet
+    warning: Multiple dots (e.g. .uuid.v7.encoded) usually indicates over-specification
+  examples:
+    positive:
+    - sensory:gesture.raw
+    - player:session.active
+    - match:config.duel

package/planner-nodes/nodes/planner.artifact-naming.theme-first-identity.convention.yaml

@@ -0,0 +1,39 @@
+schema_version: 1.0.0
+rule_id: planner.artifact-naming.theme-first-identity
+kind: rule
+status: active
+name: Artifact identity is theme-first
+statement: A produced or consumed artifact/contract identity must be theme-first — it must
+  parse as the grammar {theme}(:{category})*:{aspect}(.{variant})?, every colon/dot
+  token must be kebab-case, and the leading theme must be declared in plan/_themes.yaml.
+terms:
+- term_id: artifact_theme_first_identity
+  text: the theme-first identity rule for a produced artifact/contract name
+  values:
+    theme_source: plan/_themes.yaml
+    grammar: "{theme}(:{category})*:{aspect}(.{variant})?"
+    examples_ok:
+    - commons:identifiers.uuid
+    - commons:ux:foundations:color
+    - orders:checkout.submitted
+    - inventory:stock
+    examples_bad:
+    - undeclared:result
+    - Bad:Theme
+    - gesture.raw
+implementation:
+  type: validator
+  ref: planner.static.validators.bun
+metadata:
+  severity: 3
+  disposition: strict
+validation:
+  family: format
+  template: naming_pattern
+  variant: planner_artifact_theme_first_identity
+  phase: CONFIRM
+  enforcement: confirm-blocking
+  subject_kind: artifact
+  failure_evidence:
+  - artifact_name
+  - reason

package/planner-nodes/nodes/planner.artifact-naming.urn-structure.convention.yaml

@@ -0,0 +1,26 @@
+schema_version: 1.1.0
+rule_id: planner.artifact-naming.urn-structure
+kind: rule
+status: active
+name: URN structure
+statement: 'A contract URN exactly matches the artifact name, preserving colons and dots: contract:{artifact_name}.'
+source:
+  legacy_path: src/atdd/planner/conventions/artifact-naming.convention.yaml
+  legacy_section: urn_structure
+  legacy_sha: eca68a67c92694c9
+  extraction_mode: high_fidelity
+content:
+  examples:
+  - commons:identifiers.uuid -> contract:commons:identifiers.uuid
+  - commons:ux:foundations:color.primary -> contract:commons:ux:foundations:color.primary
+parity:
+  source_fragments_preserved: true
+  examples_preserved: true
+  implementation_preserved: false
+  fix_hint_preserved: false
+  reviewed_at: '2026-06-16'
+terms:
+- term_id: contract_urn
+  text: the URN form of an artifact name.
+  values:
+    pattern: contract:{artifact_name}

package/planner-nodes/nodes/planner.artifact-naming.validation-rules.convention.yaml

@@ -0,0 +1,33 @@
+schema_version: 1.1.0
+rule_id: planner.artifact-naming.validation-rules
+kind: constraint
+status: active
+name: Naming validation rules
+statement: Artifact names must satisfy the format, semantic, and technical validation rules.
+source:
+  legacy_path: src/atdd/planner/conventions/artifact-naming.convention.yaml
+  legacy_section: validation_rules
+  legacy_sha: eca68a67c92694c9
+  extraction_mode: high_fidelity
+content:
+  constraints:
+  - 'format: theme lowercase no separators; category/aspect/variant kebab-case; colon for descent; dot
+    for variants.'
+  - 'semantic: theme from approved taxonomy; each hierarchy level adds value; aspect a concrete noun;
+    variant a state/type/facet; URN matches name exactly; avoid deep variant nesting.'
+  - 'technical: contract file exists at contracts/{segments}.schema.json; $id is urn:contract:{artifact_name};
+    all consumers reference the same name; file path derivable by splitting on : and .'
+parity:
+  source_fragments_preserved: true
+  examples_preserved: false
+  implementation_preserved: false
+  fix_hint_preserved: false
+  reviewed_at: '2026-06-16'
+terms:
+- term_id: validation_rule
+  text: a format/semantic/technical constraint on artifact names.
+  values:
+    categories:
+    - format
+    - semantic
+    - technical

package/planner-nodes/nodes/planner.artifact-naming.verb-object-corpus-drift.convention.yaml

@@ -0,0 +1,49 @@
+schema_version: 1.0.0
+rule_id: planner.artifact-naming.verb-object-corpus-drift
+kind: policy
+status: active
+name: Verb-object drift across the authored corpus is reported
+statement: The wagon and feature names already on disk are scanned for verb-object
+  conformance and the non-conforming ones are reported with a count, so naming drift
+  is visible and its size is known. This reports; it never blocks.
+terms:
+- term_id: corpus_not_gate
+  text: 'planner.wagon.name-is-verb-object and planner.feature.name-is-verb-object
+    gate the AUTHORING path — confirm_naming reads session.kept_units(), so anything
+    authored through atdd plan conforms by construction. Neither looks at the corpus.
+    An artifact renamed by hand, or created outside a plan session, drifts with nothing
+    to notice. This rule is the corpus half.'
+- term_id: reports_never_blocks
+  text: 'Advisory by design, and the disposition is load-bearing. 101 of 229 authored
+    artifacts do not conform today, and the remedy is unaffordable: a name is carried
+    by the directory, the wagon URN, every feature/WMBT/acceptance URN beneath it,
+    the test filenames, component URNs in code headers, both registries and the State
+    Store bindings — renaming one wagon touches roughly 54 files, 37 of them tests.
+    A blocking rule with no affordable remedy is a rule that gets ignored.'
+- term_id: drift_is_the_signal
+  text: 'The count is the artefact. A rising count means new drift entered outside
+    the authoring gate, which is the only thing here that is actually actionable;
+    a falling count means debt was paid opportunistically, while someone was already
+    touching the artifact for other reasons.'
+- term_id: not_a_lexicon_gap
+  text: 'Measured before this rule was written: of 101 non-conforming names, 92 lead
+    with a noun (coach x11, substrate x4, phase x3, pr x3) and 9 carry an `and` connective.
+    Only 2 verbs were genuinely missing from the lexicon. Widening the lexicon to
+    clear the report would silence a rule that is correctly describing the corpus.'
+implementation:
+  type: validator
+  ref: test_verb_object_corpus_drift::test_corpus_verb_object_drift_is_reported
+metadata:
+  severity: 2
+  disposition: advisory
+validation:
+  family: format
+  template: naming_pattern
+  variant: planner_artifact_naming_verb_object_corpus_drift
+  phase: CONFIRM
+  enforcement: advisory
+  subject_kind: wagon
+  failure_evidence:
+  - artifact_kind
+  - slug
+  - reason

package/planner-nodes/nodes/planner.artifact.definition.convention.yaml

@@ -0,0 +1,30 @@
+schema_version: 1.1.0
+rule_id: planner.artifact.definition
+kind: family
+status: draft
+name: Artifact — advisory semantic anchor
+statement: An artifact is a produced-or-consumed unit of the domain — a theme-namespaced,
+  URN-identified thing (material, contract, schema) that wagons exchange and that WMBTs
+  and acceptances prove. Its identity follows the canonical naming pattern (theme:hierarchy:aspect.variant)
+  and mirrors its declared location. This is a planner domain-decomposition artifact
+  naming WHAT is exchanged; its runtime realization as cargo in flight is a coder/tester
+  concern. This node is an advisory semantic anchor — it enforces nothing directly;
+  the enforceable parts of this meaning are decomposed into the constraint/rule nodes
+  that require it.
+terms:
+- term_id: semantic_anchor
+  label: Advisory semantic anchor
+  text: a definitional node that gives the artifact a stable meaning but is not itself
+    bound to a validator; it is transitively protected by the enforceable constraint/rule
+    nodes that require it.
+- term_id: artifact
+  label: Artifact
+  text: artifact -> {urn-identified, theme-namespaced, naming-patterned, location-mirroring}.
+  values:
+    urn-identified: has a structured URN (see planner.artifact-naming.urn-structure,
+      planner.artifact-naming.schema-identifier).
+    theme-namespaced: its top segment is a canonical theme (see planner.artifact-naming.theme-taxonomy).
+    naming-patterned: follows theme:hierarchy:aspect.variant with colon/dot separator
+      semantics (see planner.artifact-naming.naming-pattern, planner.artifact-naming.separator-semantics).
+    location-mirroring: logical identity mirrors physical/contract location (see planner.artifact-naming.contract-file-mapping,
+      planner.artifact-naming.logical-physical-mapping).

package/planner-nodes/nodes/planner.component.artifact-derivation.convention.yaml

@@ -0,0 +1,139 @@
+schema_version: 1.1.0
+rule_id: planner.component.artifact-derivation
+kind: rule
+status: active
+name: 'Component: Artifact Derivation'
+statement: Component names are derived from artifact resources by converting the resource
+  to PascalCase and adding a capability suffix chosen by the artifact type (events,
+  states, data, configs).
+implementation:
+  type: none
+source:
+  legacy_path: src/atdd/planner/conventions/component.convention.yaml
+  legacy_sha: sha256:8bfb25fd6c2bdb6e
+  extraction_mode: high_fidelity
+  legacy_section: artifact-derivation
+content:
+  summary: Deriving a component name mechanically from its artifact resource keeps
+    names predictable and traceable back to the artifact they handle, while the type-driven
+    suffix encodes the component's capability.
+  operational_guidance: Component names come from artifact resources (the part after
+    the colon). Components describe the CAPABILITY to handle artifacts.
+  examples:
+  - Resource 'started' (event) → MatchStartedPublisher
+  - Resource 'remaining' (state) → TimebankTracker
+  counter_examples:
+  - Naming a component 'choiceHandler' (not PascalCase) or with a suffix unrelated
+    to the artifact type
+parity:
+  source_fragments_preserved: true
+  examples_preserved: true
+  implementation_preserved: true
+  fix_hint_preserved: true
+  reviewed_at: '2026-06-16'
+terms:
+- term_id: pascalcase_conversion
+  label: PascalCase conversion
+  text: Convert the artifact resource to PascalCase before adding a suffix.
+  values:
+    rule: Convert artifact resource to PascalCase
+    examples:
+    - from: choice
+      to: Choice
+    - from: player-wallet
+      to: PlayerWallet
+    - from: domain-impacts
+      to: DomainImpacts
+    - from: remaining
+      to: Remaining
+- term_id: capability_suffix
+  label: Capability suffix by artifact type
+  text: Add a capability suffix based on artifact type and component responsibility,
+    drawn from per-type suffix catalogs for events, states, data, and configs.
+  values:
+    events:
+      description: Past tense resources (started, closed, credited)
+      suffixes:
+      - Publisher
+      - Emitter
+      - Broadcaster
+      examples:
+      - artifact: match:started
+        resource: started
+        component: MatchStartedPublisher
+        urn: component:resolve-dilemmas:make-choice.MatchStartedPublisher.backend.integration
+      - artifact: wallet:credited
+        resource: credited
+        component: WalletCreditedEmitter
+        urn: component:manage-wallets:credit-wallet.WalletCreditedEmitter.backend.integration
+    states:
+      description: Adjective resources (remaining, active, current)
+      suffixes:
+      - Tracker
+      - Monitor
+      - Manager
+      examples:
+      - artifact: mechanic:timebank.remaining
+        resource: remaining
+        component: TimebankTracker
+        urn: component:burn-timebank:track-timebank.TimebankTracker.backend.domain
+      - artifact: session:active
+        resource: active
+        component: SessionManager
+        urn: component:init-session:maintain-session.SessionManager.backend.application
+    data:
+      description: Noun resources (choice, identity, profile)
+      suffixes:
+      - Provider
+      - Handler
+      - Processor
+      - Maker
+      examples:
+      - artifact: mechanic:decision.choice
+        resource: choice
+        component: ChoiceMaker
+        urn: component:resolve-dilemmas:make-choice.ChoiceMaker.backend.domain
+      - artifact: player:identity
+        resource: identity
+        component: IdentityProvider
+        urn: component:contextualize-identity:identify-player.IdentityProvider.backend.application
+    configs:
+      description: Configuration resources (config, settings, agreement)
+      suffixes:
+      - Configurator
+      - Builder
+      - Initializer
+      examples:
+      - artifact: match:config
+        resource: config
+        component: MatchConfigurator
+        urn: component:setup-match:configure-match.MatchConfigurator.backend.application
+      - artifact: league:config
+        resource: config
+        component: LeagueBuilder
+        urn: component:define-league:configure-league.LeagueBuilder.backend.application
+- term_id: complete_example
+  label: Worked artifact-to-components example
+  text: One artifact can fan out to multiple components across sides and layers, each
+    a PascalCase resource plus capability suffix.
+  values:
+    artifact: mechanic:decision.choice
+    wagon: resolve-dilemmas
+    feature: make-choice
+    components:
+    - name: ChoiceDisplay
+      urn: component:resolve-dilemmas:make-choice.ChoiceDisplay.frontend.presentation
+      purpose: Renders choice options to user
+      derivation: Resource 'choice' → ChoiceDisplay (presentation UI)
+    - name: ChoiceValidator
+      urn: component:resolve-dilemmas:make-choice.ChoiceValidator.frontend.application
+      purpose: Validates user selection before submission
+      derivation: Resource 'choice' → ChoiceValidator (validation logic)
+    - name: ChoiceMaker
+      urn: component:resolve-dilemmas:make-choice.ChoiceMaker.backend.domain
+      purpose: Applies business rules to make the choice
+      derivation: Resource 'choice' → ChoiceMaker (core business logic)
+    - name: ChoicePersister
+      urn: component:resolve-dilemmas:make-choice.ChoicePersister.backend.integration
+      purpose: Persists choice to database
+      derivation: Resource 'choice' → ChoicePersister (persistence)

package/planner-nodes/nodes/planner.component.business-focus.convention.yaml

@@ -0,0 +1,65 @@
+schema_version: 1.1.0
+rule_id: planner.component.business-focus
+kind: rule
+status: active
+name: 'Component: Business Focus'
+statement: Each component must have a single business capability, and its name must
+  reflect that primary business purpose.
+implementation:
+  type: none
+source:
+  legacy_path: src/atdd/planner/conventions/component.convention.yaml
+  legacy_sha: sha256:8bfb25fd6c2bdb6e
+  extraction_mode: high_fidelity
+  legacy_section: business-focus
+content:
+  summary: One business capability per component keeps responsibilities sharp and
+    makes the component's name a faithful index of what it does, so the graph stays
+    readable and components stay swappable.
+  examples:
+  - option-validator
+  - decision-processor
+  - dilemma-display
+  - choice-persister
+  - result-publisher
+  counter_examples:
+  - 'manager-helper-util  # vague, no single business capability'
+parity:
+  source_fragments_preserved: true
+  examples_preserved: true
+  implementation_preserved: true
+  fix_hint_preserved: true
+  reviewed_at: '2026-06-16'
+terms:
+- term_id: single_capability
+  label: Single business capability
+  text: Each component must have a single business capability. Check that the component
+    name reflects its primary business purpose.
+  values:
+    rule: Each component must have single business capability
+    check: Component name reflects its primary business purpose
+- term_id: business_capabilities
+  label: Business capability vocabulary
+  text: Canonical business capabilities a component name can express, grouped by core
+    business, UI/UX, and integration concerns.
+  values:
+    core_business:
+      validator: Validates business rules and constraints
+      processor: Processes business logic and computations
+      coordinator: Coordinates multiple operations
+      transformer: Transforms data between formats
+      aggregator: Aggregates data from multiple sources
+    ui_ux:
+      display: Displays information to users
+      collector: Collects user input
+      navigator: Manages navigation flow
+    integration:
+      persister: Persists data to storage
+      fetcher: Fetches data from external sources
+      publisher: Publishes events/notifications
+      subscriber: Subscribes to events/notifications
+- term_id: naming_pattern
+  label: Component naming pattern
+  text: Component names follow the pattern {business-capability}-{layer-role}.
+  values:
+    pattern: '{business-capability}-{layer-role}'

package/planner-nodes/nodes/planner.component.count-limit.convention.yaml

@@ -0,0 +1,64 @@
+schema_version: 1.1.0
+rule_id: planner.component.count-limit
+kind: constraint
+status: active
+name: 'Component: Count Limit'
+statement: A feature must have at most 8 components; beyond 8 indicates the feature
+  is too large and should be split.
+terms:
+- term_id: max_per_feature
+  label: Maximum components per feature
+  text: "Feature must have \u2264 8 components. Beyond 8 components indicates the\
+    \ feature is too large and should be split."
+  values:
+    max_per_feature: 8
+    action: Split feature if more components needed
+    rationale: Beyond 8 components indicates feature is too large and should be split
+- term_id: typical_distribution
+  label: Typical component distribution
+  text: A typical 8-component budget splits across frontend, backend, and shared cross-cutting
+    concerns.
+  values:
+    frontend: 2
+    backend: 3
+    shared: 3
+    note: frontend = presentation + application; backend = application + domain +
+      integration; shared = cross-cutting concerns
+- term_id: layer_distribution
+  label: Layers available per side
+  text: Frontend components live in presentation/application; backend components live
+    in application/domain/integration.
+  values:
+    frontend:
+    - presentation
+    - application
+    backend:
+    - application
+    - domain
+    - integration
+implementation:
+  type: validator
+  ref: test_component_count_limit::test_component_count_limit
+source:
+  legacy_path: src/atdd/planner/conventions/component.convention.yaml
+  legacy_sha: sha256:8bfb25fd6c2bdb6e
+  extraction_mode: high_fidelity
+  legacy_section: count-limit
+content:
+  summary: A hard ceiling of 8 components per feature keeps features cohesive and
+    bounded, mirroring the WMBT acceptance limits, and forces oversized features to
+    be split rather than sprawl.
+  examples:
+  - 'Feature with 8 components: 2 frontend + 3 backend + 3 shared'
+  counter_examples:
+  - "Feature with 12 components \u2014 too large, must be split"
+metadata:
+  severity: 2
+  disposition: advisory
+  introduced_in: 4.28.0
+parity:
+  source_fragments_preserved: true
+  examples_preserved: true
+  implementation_preserved: true
+  fix_hint_preserved: true
+  reviewed_at: '2026-06-16'

package/planner-nodes/nodes/planner.component.derivation.convention.yaml

@@ -0,0 +1,117 @@
+schema_version: 1.1.0
+rule_id: planner.component.derivation
+kind: rule
+status: active
+name: 'Component: Derivation'
+statement: Components are derived from feature analysis — from ioSeeds triggers (events,
+  commands, queries) and from WMBT verbs (validate, process, display, persist, coordinate)
+  — each trigger generating a component with a business capability and layer.
+implementation:
+  type: none
+source:
+  legacy_path: src/atdd/planner/conventions/component.convention.yaml
+  legacy_sha: sha256:8bfb25fd6c2bdb6e
+  extraction_mode: high_fidelity
+  legacy_section: derivation
+content:
+  summary: Deriving components from a feature's ioSeeds and WMBTs makes component
+    generation systematic and traceable, since every component exists because a concrete
+    trigger in the feature called for it.
+  examples:
+  - WMBT 'persist choice' → ChoicePersister at integration
+  - feature.ioSeeds.consume contains command:* → command-processing component at application
+  counter_examples:
+  - Inventing a component with no ioSeed or WMBT trigger behind it
+parity:
+  source_fragments_preserved: true
+  examples_preserved: true
+  implementation_preserved: true
+  fix_hint_preserved: true
+  reviewed_at: '2026-06-16'
+terms:
+- term_id: from_io_seeds
+  label: Derivation from ioSeeds
+  text: ioSeeds triggers generate components with event-publishing, event-handling,
+    command-processing, or query-handling capability.
+  values:
+    produce_events:
+      trigger: feature.ioSeeds.produce contains event:* or notification:*
+      generates: Component with event publishing capability
+      layer: application or integration
+    consume_events:
+      trigger: feature.ioSeeds.consume contains event:* or notification:*
+      generates: Component with event handling capability
+      layer: application or integration
+    consume_commands:
+      trigger: feature.ioSeeds.consume contains command:*
+      generates: Component with command processing capability
+      layer: application
+    produce_queries:
+      trigger: feature.ioSeeds.produce contains query:*
+      generates: Component with query handling capability
+      layer: application or domain
+- term_id: from_wmbt_analysis
+  label: Derivation from WMBT analysis
+  text: WMBT verbs generate validation, processing, presentation, persistence, or
+    coordination components with a business capability and layer.
+  values:
+    validation_needs:
+      trigger: WMBTs contain 'validate', 'verify', 'check'
+      generates: Validation component
+      business_capability: validator
+      layer: domain
+    processing_needs:
+      trigger: WMBTs contain 'process', 'compute', 'calculate'
+      generates: Processing component
+      business_capability: processor
+      layer: application or domain
+    presentation_needs:
+      trigger: WMBTs contain 'display', 'show', 'render'
+      generates: Presentation component
+      business_capability: display
+      layer: presentation
+    persistence_needs:
+      trigger: WMBTs contain 'store', 'save', 'persist'
+      generates: Persistence component
+      business_capability: persister
+      layer: integration
+    coordination_needs:
+      trigger: WMBTs contain 'coordinate', 'orchestrate', 'manage'
+      generates: Coordination component
+      business_capability: coordinator
+      layer: application
+- term_id: generation_strategy
+  label: Component generation strategy
+  text: The end-to-end strategy from feature analysis to validated components.
+  values:
+    step_1_analyze: Analyze feature ioSeeds and WMBTs
+    step_2_identify: Identify needed business capabilities
+    step_3_assign: Assign capabilities to appropriate layers
+    step_4_generate: Generate up to 8 components with complete structure
+    step_5_validate: Ensure all feature needs covered by components
+- term_id: mapping_example
+  label: Feature-to-component mapping example
+  text: A binary-choice feature with consume/produce ioSeeds and WMBTs maps to validator,
+    processor, and display components.
+  values:
+    binary_choice_feature:
+      input:
+        ioSeeds:
+          consume:
+          - dilemma:presented
+          produce:
+          - decision:made
+        wmbts:
+        - validate options
+        - process choice
+        - display result
+      output_components:
+      - business_capability: option-validator
+        layer: domain
+        reason: WMBT mentions validation
+      - business_capability: choice-processor
+        layer: application
+        reason: WMBT mentions processing
+      - business_capability: result-display
+        layer: presentation
+        reason: WMBT mentions display

package/planner-nodes/nodes/planner.component.io-alignment.convention.yaml

@@ -0,0 +1,65 @@
+schema_version: 1.1.0
+rule_id: planner.component.io-alignment
+kind: rule
+status: active
+name: 'Component: Io Alignment'
+statement: A component's consumed and produced events must be a subset of the owning
+  feature's ioSeeds; every event must be traceable to a feature ioSeed.
+implementation:
+  type: none
+source:
+  legacy_path: src/atdd/planner/conventions/component.convention.yaml
+  legacy_sha: sha256:8bfb25fd6c2bdb6e
+  extraction_mode: high_fidelity
+  legacy_section: io-alignment
+content:
+  summary: Constraining component events to the feature's ioSeeds keeps the component's
+    interface within its feature's declared contract, so no component can quietly
+    invent inputs or outputs the feature never promised.
+  examples:
+  - Component consumes [dilemma:presented] where feature.ioSeeds.consume includes
+    dilemma:presented
+  counter_examples:
+  - Component produces order:shipped but feature.ioSeeds.produce does not contain
+    it
+parity:
+  source_fragments_preserved: true
+  examples_preserved: true
+  implementation_preserved: true
+  fix_hint_preserved: true
+  reviewed_at: '2026-06-16'
+terms:
+- term_id: events_subset
+  label: Events subset of feature ioSeeds
+  text: Component events must be a subset of feature ioSeeds. Check that all consumed/produced
+    events are traceable to feature ioSeeds.
+  values:
+    rule: Component events must subset of feature ioSeeds
+    check: All consumed/produced events traceable to feature ioSeeds
+- term_id: event_limits
+  label: Consume/produce limits and sources
+  text: A component consumes events filtered from feature.ioSeeds.consume by its role
+    and produces events filtered from feature.ioSeeds.produce by its capability, each
+    capped at 3.
+  values:
+    consumes:
+      source: feature.ioSeeds.consume filtered by component role
+      maximum: 3
+      example:
+      - dilemma:presented
+      - user:authenticated
+    produces:
+      source: feature.ioSeeds.produce filtered by component capability
+      maximum: 3
+      example:
+      - decision:made
+      - validation:completed
+- term_id: dependencies
+  label: Component dependencies
+  text: Dependencies come from other components in the same feature plus external
+    dependencies.
+  values:
+    source: Other components in same feature + external dependencies
+    example:
+    - component:same:feature.other
+    - wagon:external#io