@acidicsoil/portable-capabilities 0.1.4 → 0.1.7

package/dist-release/catalog/roles/acceptance-criteria-synthesis.yaml

@@ -0,0 +1,84 @@
+schemaVersion: '1.0'
+id: acceptance-criteria-synthesis
+purpose: Derive measurable acceptance criteria from intent and evidence.
+family:
+  id: guardrails-evaluation
+  version: 1.0.0
+taxonomy:
+  id: acceptance-criteria-synthesis
+  displayName: Acceptance Criteria Synthesis
+  transformation: Derive measurable acceptance criteria from intent and evidence.
+  intendedOutput: Acceptance criteria set
+inputs:
+- name: intent-and-requirements
+  description: The intent, requirements, or obligations to be accepted.
+  required: true
+- name: implementation-evidence
+  description: Evidence about the system or artifact under evaluation.
+  required: false
+- name: quality-thresholds
+  description: Measurable thresholds and tolerances.
+  required: false
+precedence:
+- sourceClass: explicit-contract
+  rank: 0
+- sourceClass: observed-artifact
+  rank: 1
+- sourceClass: inference
+  rank: 2
+pipeline:
+- id: ingest.sources
+  version: 1.0.0
+- id: trace.build-evidence-ledger
+  version: 1.0.0
+- id: validation.contract
+  version: 1.0.0
+output:
+  schema: canonical/schemas/acceptance-criteria-synthesis.output.schema.json
+  description: Acceptance criteria set
+requiredBehavior:
+- 'activation: Use acceptance-criteria-synthesis only when the requested outcome requires this transformation: Derive
+  measurable acceptance criteria from intent and evidence.'
+- 'sufficiency: Require all role inputs marked required and enough evidence to complete these gates: Every obligation
+  maps to at least one unambiguous criterion, each criterion names evidence and pass/fail conditions, and coverage
+  gaps are explicit.'
+- 'conflict: Apply declared source precedence; when equally authoritative evidence changes the decision, preserve
+  both positions and return the affected output field as unresolved.'
+- 'ambiguity: Isolate ambiguous terms or boundaries, show which stage and output fields they affect, and request
+  clarification rather than selecting an unsupported interpretation.'
+- 'abstention: Abstain from acceptance-criteria-synthesis when required inputs are absent, the decision rule cannot
+  be applied, or evidence cannot satisfy the completion gate.'
+- 'stop: Stop before emitting Acceptance criteria set unless Every obligation maps to at least one unambiguous criterion,
+  each criterion names evidence and pass/fail conditions, and coverage gaps are explicit.'
+- 'resources: Load requirements, governing contracts, implementation evidence, and measurement standards; load examples
+  only to clarify boundary conditions.'
+- 'transformation: Execute the ordered analytical procedure: 1) decompose intent into observable obligations; 2)
+  identify success failure boundary and edge conditions; 3) write measurable criteria with evidence and threshold
+  requirements; 4) check completeness ambiguity independence and testability.'
+- 'output: Populate and validate canonical/schemas/acceptance-criteria-synthesis.output.schema.json with required
+  fields criteria, evidenceRequirements, thresholds, failureConditions, coverageMap; do not replace missing fields
+  with prose.'
+- 'traceability: Link every material output field to source identifiers and the analytical stage or decision that
+  produced it; retain counterevidence for unresolved results.'
+- 'evaluation: Pass only when the output schema validates, the ordered stages are evidenced, the role decision rule
+  was applied, and this completion gate holds: Every obligation maps to at least one unambiguous criterion, each
+  criterion names evidence and pass/fail conditions, and coverage gaps are explicit.'
+forbiddenBehavior:
+- Do not substitute generic analytical behavior for the role-specific acceptance-criteria-synthesis transformation.
+- Do not skip, reorder, or silently collapse the role's declared analytical stages.
+- Do not invent missing evidence, resolve authority conflicts by convenience, or emit a completed result after a
+  stop or abstention condition.
+- Do not copy operation-owned ingestion, ledger, or schema-validation mechanics into the role contract.
+traceability:
+  materialClaimsRequireSources: true
+  ledgerFormat: jsonl
+  artifacts: content-addressed
+evaluation:
+  criteria:
+  - The authoritative transformation and intended output for acceptance-criteria-synthesis are preserved.
+  - 'Required inputs and the decision rule are satisfied: Accept a criterion only when an independent evaluator
+    can determine pass or fail from named evidence without inferring unstated intent.'
+  - 'The ordered analytical stages are evidenced and the output completion gate passes: Every obligation maps to
+    at least one unambiguous criterion, each criterion names evidence and pass/fail conditions, and coverage gaps
+    are explicit.'
+  - Conflict, ambiguity, insufficient-evidence, abstention, and stop behavior remain explicit and testable.

package/dist-release/catalog/roles/anti-pattern-inversion.yaml

@@ -0,0 +1,83 @@
+schemaVersion: '1.0'
+id: anti-pattern-inversion
+purpose: Invert documented anti-patterns into positive construction rules.
+family:
+  id: corrective-transformation
+  version: 1.0.0
+taxonomy:
+  id: anti-pattern-inversion
+  displayName: Anti-Pattern Inversion
+  transformation: Invert documented anti-patterns into positive construction rules.
+  intendedOutput: Corrective rule set
+inputs:
+- name: anti-pattern-catalog
+  description: Documented anti-patterns and failure examples.
+  required: true
+- name: construction-context
+  description: The context in which positive rules will be applied.
+  required: true
+- name: existing-controls
+  description: Existing rules or controls that may overlap.
+  required: false
+precedence:
+- sourceClass: explicit-contract
+  rank: 0
+- sourceClass: observed-artifact
+  rank: 1
+- sourceClass: inference
+  rank: 2
+pipeline:
+- id: ingest.sources
+  version: 1.0.0
+- id: trace.build-evidence-ledger
+  version: 1.0.0
+- id: validation.contract
+  version: 1.0.0
+output:
+  schema: canonical/schemas/anti-pattern-inversion.output.schema.json
+  description: Corrective rule set
+requiredBehavior:
+- 'activation: Use anti-pattern-inversion only when the requested outcome requires this transformation: Invert documented
+  anti-patterns into positive construction rules.'
+- 'sufficiency: Require all role inputs marked required and enough evidence to complete these gates: Every rule
+  traces to a harmful mechanism, passes original failure cases, and documents legitimate exceptions and overlap
+  with existing controls.'
+- 'conflict: Apply declared source precedence; when equally authoritative evidence changes the decision, preserve
+  both positions and return the affected output field as unresolved.'
+- 'ambiguity: Isolate ambiguous terms or boundaries, show which stage and output fields they affect, and request
+  clarification rather than selecting an unsupported interpretation.'
+- 'abstention: Abstain from anti-pattern-inversion when required inputs are absent, the decision rule cannot be
+  applied, or evidence cannot satisfy the completion gate.'
+- 'stop: Stop before emitting Corrective rule set unless Every rule traces to a harmful mechanism, passes original
+  failure cases, and documents legitimate exceptions and overlap with existing controls.'
+- 'resources: Load anti-pattern evidence, construction context, existing controls, and exception examples; load
+  each failure trace to validate causal coverage.'
+- 'transformation: Execute the ordered analytical procedure: 1) identify the harmful mechanism and triggering conditions;
+  2) derive the positive invariant that prevents the mechanism; 3) translate the invariant into actionable construction
+  and review rules; 4) test rules against original failures and legitimate exceptions.'
+- 'output: Populate and validate canonical/schemas/anti-pattern-inversion.output.schema.json with required fields
+  antiPatternMap, positiveRules, exceptions, verificationChecks, coverageEvidence; do not replace missing fields
+  with prose.'
+- 'traceability: Link every material output field to source identifiers and the analytical stage or decision that
+  produced it; retain counterevidence for unresolved results.'
+- 'evaluation: Pass only when the output schema validates, the ordered stages are evidenced, the role decision rule
+  was applied, and this completion gate holds: Every rule traces to a harmful mechanism, passes original failure
+  cases, and documents legitimate exceptions and overlap with existing controls.'
+forbiddenBehavior:
+- Do not substitute generic analytical behavior for the role-specific anti-pattern-inversion transformation.
+- Do not skip, reorder, or silently collapse the role's declared analytical stages.
+- Do not invent missing evidence, resolve authority conflicts by convenience, or emit a completed result after a
+  stop or abstention condition.
+- Do not copy operation-owned ingestion, ledger, or schema-validation mechanics into the role contract.
+traceability:
+  materialClaimsRequireSources: true
+  ledgerFormat: jsonl
+  artifacts: content-addressed
+evaluation:
+  criteria:
+  - The authoritative transformation and intended output for anti-pattern-inversion are preserved.
+  - 'Required inputs and the decision rule are satisfied: Adopt a positive rule only when it blocks the harmful
+    mechanism without prohibiting documented legitimate behavior.'
+  - 'The ordered analytical stages are evidenced and the output completion gate passes: Every rule traces to a harmful
+    mechanism, passes original failure cases, and documents legitimate exceptions and overlap with existing controls.'
+  - Conflict, ambiguity, insufficient-evidence, abstention, and stop behavior remain explicit and testable.

package/dist-release/catalog/roles/behavior-preserving-refactor.yaml

@@ -0,0 +1,88 @@
+schemaVersion: '1.0'
+id: behavior-preserving-refactor
+purpose: Transform structure while preserving observable behavior.
+family:
+  id: corrective-transformation
+  version: 1.0.0
+taxonomy:
+  id: behavior-preserving-refactor
+  displayName: Behavior-Preserving Refactor
+  transformation: Transform structure while preserving observable behavior.
+  intendedOutput: Refactored artifact with equivalence evidence
+inputs:
+- name: source-artifact
+  description: The artifact to restructure.
+  required: true
+- name: behavior-contract
+  description: Observable behavior that must be preserved.
+  required: true
+- name: refactor-goals
+  description: Structural goals and allowed change scope.
+  required: true
+- name: equivalence-fixtures
+  description: Tests or traces used to prove equivalence.
+  required: true
+precedence:
+- sourceClass: explicit-contract
+  rank: 0
+- sourceClass: observed-artifact
+  rank: 1
+- sourceClass: inference
+  rank: 2
+pipeline:
+- id: ingest.sources
+  version: 1.0.0
+- id: trace.build-evidence-ledger
+  version: 1.0.0
+- id: validation.contract
+  version: 1.0.0
+output:
+  schema: canonical/schemas/behavior-preserving-refactor.output.schema.json
+  description: Refactored artifact with equivalence evidence
+requiredBehavior:
+- 'activation: Use behavior-preserving-refactor only when the requested outcome requires this transformation: Transform
+  structure while preserving observable behavior.'
+- 'sufficiency: Require all role inputs marked required and enough evidence to complete these gates: All affected
+  behavior passes equivalence checks, any difference is declared out of scope or rejected, and the structural goal
+  is demonstrably achieved.'
+- 'conflict: Apply declared source precedence; when equally authoritative evidence changes the decision, preserve
+  both positions and return the affected output field as unresolved.'
+- 'ambiguity: Isolate ambiguous terms or boundaries, show which stage and output fields they affect, and request
+  clarification rather than selecting an unsupported interpretation.'
+- 'abstention: Abstain from behavior-preserving-refactor when required inputs are absent, the decision rule cannot
+  be applied, or evidence cannot satisfy the completion gate.'
+- 'stop: Stop before emitting Refactored artifact with equivalence evidence unless All affected behavior passes
+  equivalence checks, any difference is declared out of scope or rejected, and the structural goal is demonstrably
+  achieved.'
+- 'resources: Load the source artifact, behavior contract, baseline tests, execution traces, and refactor constraints;
+  run only read-safe analysis unless an explicit execution harness is provided.'
+- 'transformation: Execute the ordered analytical procedure: 1) establish a pre-change behavioral baseline; 2) identify
+  structural changes that do not alter the behavior contract; 3) apply changes in reversible increments; 4) compare
+  outputs side effects and failure behavior against the baseline.'
+- 'output: Populate and validate canonical/schemas/behavior-preserving-refactor.output.schema.json with required
+  fields refactoredArtifact, changeMap, equivalenceEvidence, behavioralDiffs, rollbackNotes; do not replace missing
+  fields with prose.'
+- 'traceability: Link every material output field to source identifiers and the analytical stage or decision that
+  produced it; retain counterevidence for unresolved results.'
+- 'evaluation: Pass only when the output schema validates, the ordered stages are evidenced, the role decision rule
+  was applied, and this completion gate holds: All affected behavior passes equivalence checks, any difference is
+  declared out of scope or rejected, and the structural goal is demonstrably achieved.'
+forbiddenBehavior:
+- Do not substitute generic analytical behavior for the role-specific behavior-preserving-refactor transformation.
+- Do not skip, reorder, or silently collapse the role's declared analytical stages.
+- Do not invent missing evidence, resolve authority conflicts by convenience, or emit a completed result after a
+  stop or abstention condition.
+- Do not copy operation-owned ingestion, ledger, or schema-validation mechanics into the role contract.
+traceability:
+  materialClaimsRequireSources: true
+  ledgerFormat: jsonl
+  artifacts: content-addressed
+evaluation:
+  criteria:
+  - The authoritative transformation and intended output for behavior-preserving-refactor are preserved.
+  - 'Required inputs and the decision rule are satisfied: Permit a structural change only when equivalence evidence
+    covers affected behavior; classify intentional behavior changes outside this role.'
+  - 'The ordered analytical stages are evidenced and the output completion gate passes: All affected behavior passes
+    equivalence checks, any difference is declared out of scope or rejected, and the structural goal is demonstrably
+    achieved.'
+  - Conflict, ambiguity, insufficient-evidence, abstention, and stop behavior remain explicit and testable.

package/dist-release/catalog/roles/canonical-exemplar-generalization.yaml

@@ -0,0 +1,84 @@
+schemaVersion: '1.0'
+id: canonical-exemplar-generalization
+purpose: Transform concrete exemplars into a reusable canonical model.
+family:
+  id: exemplar-modeling
+  version: 1.0.0
+taxonomy:
+  id: canonical-exemplar-generalization
+  displayName: Canonical Exemplar Generalization
+  transformation: Transform concrete exemplars into a reusable canonical model.
+  intendedOutput: Canonical generalized model
+inputs:
+- name: exemplars
+  description: Representative concrete exemplars to generalize.
+  required: true
+- name: variation-samples
+  description: Counterexamples or variants used to test generality.
+  required: true
+- name: scope-constraints
+  description: Explicit boundaries the generalized model must respect.
+  required: false
+precedence:
+- sourceClass: explicit-contract
+  rank: 0
+- sourceClass: observed-artifact
+  rank: 1
+- sourceClass: inference
+  rank: 2
+pipeline:
+- id: ingest.sources
+  version: 1.0.0
+- id: trace.build-evidence-ledger
+  version: 1.0.0
+- id: validation.contract
+  version: 1.0.0
+output:
+  schema: canonical/schemas/canonical-exemplar-generalization.output.schema.json
+  description: Canonical generalized model
+requiredBehavior:
+- 'activation: Use canonical-exemplar-generalization only when the requested outcome requires this transformation:
+  Transform concrete exemplars into a reusable canonical model.'
+- 'sufficiency: Require all role inputs marked required and enough evidence to complete these gates: Every invariant
+  is supported by multiple exemplars, every variation point is bounded, and held-out variants are either covered
+  or explicitly excluded.'
+- 'conflict: Apply declared source precedence; when equally authoritative evidence changes the decision, preserve
+  both positions and return the affected output field as unresolved.'
+- 'ambiguity: Isolate ambiguous terms or boundaries, show which stage and output fields they affect, and request
+  clarification rather than selecting an unsupported interpretation.'
+- 'abstention: Abstain from canonical-exemplar-generalization when required inputs are absent, the decision rule
+  cannot be applied, or evidence cannot satisfy the completion gate.'
+- 'stop: Stop before emitting Canonical generalized model unless Every invariant is supported by multiple exemplars,
+  every variation point is bounded, and held-out variants are either covered or explicitly excluded.'
+- 'resources: Load the exemplar corpus, scope constraints, and held-out variation set; load each only when it contributes
+  coverage or falsification evidence.'
+- 'transformation: Execute the ordered analytical procedure: 1) inventory invariant and variable features across
+  exemplars; 2) separate essential structure from incidental detail; 3) propose the smallest reusable model covering
+  supported variation; 4) challenge the model against held-out variants and record exclusions.'
+- 'output: Populate and validate canonical/schemas/canonical-exemplar-generalization.output.schema.json with required
+  fields model, invariants, variationPoints, excludedDetails, coverageEvidence; do not replace missing fields with
+  prose.'
+- 'traceability: Link every material output field to source identifiers and the analytical stage or decision that
+  produced it; retain counterevidence for unresolved results.'
+- 'evaluation: Pass only when the output schema validates, the ordered stages are evidenced, the role decision rule
+  was applied, and this completion gate holds: Every invariant is supported by multiple exemplars, every variation
+  point is bounded, and held-out variants are either covered or explicitly excluded.'
+forbiddenBehavior:
+- Do not substitute generic analytical behavior for the role-specific canonical-exemplar-generalization transformation.
+- Do not skip, reorder, or silently collapse the role's declared analytical stages.
+- Do not invent missing evidence, resolve authority conflicts by convenience, or emit a completed result after a
+  stop or abstention condition.
+- Do not copy operation-owned ingestion, ledger, or schema-validation mechanics into the role contract.
+traceability:
+  materialClaimsRequireSources: true
+  ledgerFormat: jsonl
+  artifacts: content-addressed
+evaluation:
+  criteria:
+  - The authoritative transformation and intended output for canonical-exemplar-generalization are preserved.
+  - 'Required inputs and the decision rule are satisfied: Retain a feature only when it is necessary across supported
+    exemplars or explicitly required by scope; otherwise classify it as optional or excluded.'
+  - 'The ordered analytical stages are evidenced and the output completion gate passes: Every invariant is supported
+    by multiple exemplars, every variation point is bounded, and held-out variants are either covered or explicitly
+    excluded.'
+  - Conflict, ambiguity, insufficient-evidence, abstention, and stop behavior remain explicit and testable.

package/dist-release/catalog/roles/constrained-exemplar-adaptation.yaml

@@ -0,0 +1,85 @@
+schemaVersion: '1.0'
+id: constrained-exemplar-adaptation
+purpose: Adapt an exemplar under explicit constraints.
+family:
+  id: exemplar-modeling
+  version: 1.0.0
+taxonomy:
+  id: constrained-exemplar-adaptation
+  displayName: Constrained Exemplar Adaptation
+  transformation: Adapt an exemplar under explicit constraints.
+  intendedOutput: Constraint-compliant adaptation
+inputs:
+- name: source-exemplar
+  description: The exemplar whose structure or behavior is being adapted.
+  required: true
+- name: target-constraints
+  description: Mandatory target-environment constraints.
+  required: true
+- name: preservation-requirements
+  description: Properties that must remain unchanged.
+  required: true
+- name: target-context
+  description: Optional target conventions and integration context.
+  required: false
+precedence:
+- sourceClass: explicit-contract
+  rank: 0
+- sourceClass: observed-artifact
+  rank: 1
+- sourceClass: inference
+  rank: 2
+pipeline:
+- id: ingest.sources
+  version: 1.0.0
+- id: trace.build-evidence-ledger
+  version: 1.0.0
+- id: validation.contract
+  version: 1.0.0
+output:
+  schema: canonical/schemas/constrained-exemplar-adaptation.output.schema.json
+  description: Constraint-compliant adaptation
+requiredBehavior:
+- 'activation: Use constrained-exemplar-adaptation only when the requested outcome requires this transformation:
+  Adapt an exemplar under explicit constraints.'
+- 'sufficiency: Require all role inputs marked required and enough evidence to complete these gates: All mandatory
+  constraints pass, preserved properties remain equivalent, and every deviation has an evidence-backed rationale.'
+- 'conflict: Apply declared source precedence; when equally authoritative evidence changes the decision, preserve
+  both positions and return the affected output field as unresolved.'
+- 'ambiguity: Isolate ambiguous terms or boundaries, show which stage and output fields they affect, and request
+  clarification rather than selecting an unsupported interpretation.'
+- 'abstention: Abstain from constrained-exemplar-adaptation when required inputs are absent, the decision rule cannot
+  be applied, or evidence cannot satisfy the completion gate.'
+- 'stop: Stop before emitting Constraint-compliant adaptation unless All mandatory constraints pass, preserved properties
+  remain equivalent, and every deviation has an evidence-backed rationale.'
+- 'resources: Load the source exemplar, target constraint set, preservation checks, and target conventions only
+  when a mapped element depends on them.'
+- 'transformation: Execute the ordered analytical procedure: 1) extract the exemplar properties relevant to the
+  target; 2) classify target constraints as mandatory, negotiable, or conflicting; 3) map exemplar elements to target-compatible
+  replacements; 4) validate preserved properties and document every intentional deviation.'
+- 'output: Populate and validate canonical/schemas/constrained-exemplar-adaptation.output.schema.json with required
+  fields adaptedArtifact, constraintMapping, preservedProperties, deviations, validationResults; do not replace
+  missing fields with prose.'
+- 'traceability: Link every material output field to source identifiers and the analytical stage or decision that
+  produced it; retain counterevidence for unresolved results.'
+- 'evaluation: Pass only when the output schema validates, the ordered stages are evidenced, the role decision rule
+  was applied, and this completion gate holds: All mandatory constraints pass, preserved properties remain equivalent,
+  and every deviation has an evidence-backed rationale.'
+forbiddenBehavior:
+- Do not substitute generic analytical behavior for the role-specific constrained-exemplar-adaptation transformation.
+- Do not skip, reorder, or silently collapse the role's declared analytical stages.
+- Do not invent missing evidence, resolve authority conflicts by convenience, or emit a completed result after a
+  stop or abstention condition.
+- Do not copy operation-owned ingestion, ledger, or schema-validation mechanics into the role contract.
+traceability:
+  materialClaimsRequireSources: true
+  ledgerFormat: jsonl
+  artifacts: content-addressed
+evaluation:
+  criteria:
+  - The authoritative transformation and intended output for constrained-exemplar-adaptation are preserved.
+  - 'Required inputs and the decision rule are satisfied: Prefer the least-divergent adaptation that satisfies all
+    mandatory constraints; abstain when two mandatory constraints cannot be jointly satisfied.'
+  - 'The ordered analytical stages are evidenced and the output completion gate passes: All mandatory constraints
+    pass, preserved properties remain equivalent, and every deviation has an evidence-backed rationale.'
+  - Conflict, ambiguity, insufficient-evidence, abstention, and stop behavior remain explicit and testable.

package/dist-release/catalog/roles/convention-mining.yaml

@@ -0,0 +1,81 @@
+schemaVersion: '1.0'
+id: convention-mining
+purpose: Infer recurring conventions from observed artifacts.
+family:
+  id: exemplar-modeling
+  version: 1.0.0
+taxonomy:
+  id: convention-mining
+  displayName: Convention Mining
+  transformation: Infer recurring conventions from observed artifacts.
+  intendedOutput: Convention registry
+inputs:
+- name: observed-artifacts
+  description: Observed artifacts that may encode recurring conventions.
+  required: true
+- name: authority-sources
+  description: Explicit style guides or contracts that outrank observation.
+  required: false
+- name: sampling-context
+  description: Repository, team, or domain boundaries for the sample.
+  required: true
+precedence:
+- sourceClass: explicit-contract
+  rank: 0
+- sourceClass: observed-artifact
+  rank: 1
+- sourceClass: inference
+  rank: 2
+pipeline:
+- id: ingest.sources
+  version: 1.0.0
+- id: trace.build-evidence-ledger
+  version: 1.0.0
+- id: validation.contract
+  version: 1.0.0
+output:
+  schema: canonical/schemas/convention-mining.output.schema.json
+  description: Convention registry
+requiredBehavior:
+- 'activation: Use convention-mining only when the requested outcome requires this transformation: Infer recurring
+  conventions from observed artifacts.'
+- 'sufficiency: Require all role inputs marked required and enough evidence to complete these gates: Every convention
+  reports scope, support, counterexamples, authority status, and confidence sufficient for its classification.'
+- 'conflict: Apply declared source precedence; when equally authoritative evidence changes the decision, preserve
+  both positions and return the affected output field as unresolved.'
+- 'ambiguity: Isolate ambiguous terms or boundaries, show which stage and output fields they affect, and request
+  clarification rather than selecting an unsupported interpretation.'
+- 'abstention: Abstain from convention-mining when required inputs are absent, the decision rule cannot be applied,
+  or evidence cannot satisfy the completion gate.'
+- 'stop: Stop before emitting Convention registry unless Every convention reports scope, support, counterexamples,
+  authority status, and confidence sufficient for its classification.'
+- 'resources: Load representative artifacts, explicit guides, and sampling metadata; expand the sample when confidence
+  is below the declared threshold.'
+- 'transformation: Execute the ordered analytical procedure: 1) sample artifacts across the declared context; 2)
+  count recurring choices and cluster equivalent forms; 3) compare observed choices with explicit authority; 4)
+  classify conventions as mandated, dominant, contested, or local.'
+- 'output: Populate and validate canonical/schemas/convention-mining.output.schema.json with required fields conventions,
+  classification, supportCounts, counterexamples, scope; do not replace missing fields with prose.'
+- 'traceability: Link every material output field to source identifiers and the analytical stage or decision that
+  produced it; retain counterevidence for unresolved results.'
+- 'evaluation: Pass only when the output schema validates, the ordered stages are evidenced, the role decision rule
+  was applied, and this completion gate holds: Every convention reports scope, support, counterexamples, authority
+  status, and confidence sufficient for its classification.'
+forbiddenBehavior:
+- Do not substitute generic analytical behavior for the role-specific convention-mining transformation.
+- Do not skip, reorder, or silently collapse the role's declared analytical stages.
+- Do not invent missing evidence, resolve authority conflicts by convenience, or emit a completed result after a
+  stop or abstention condition.
+- Do not copy operation-owned ingestion, ledger, or schema-validation mechanics into the role contract.
+traceability:
+  materialClaimsRequireSources: true
+  ledgerFormat: jsonl
+  artifacts: content-addressed
+evaluation:
+  criteria:
+  - The authoritative transformation and intended output for convention-mining are preserved.
+  - 'Required inputs and the decision rule are satisfied: Treat explicit authority as mandated; infer a convention
+    only when recurrence is broad enough for the declared sampling context and counterexamples are disclosed.'
+  - 'The ordered analytical stages are evidenced and the output completion gate passes: Every convention reports
+    scope, support, counterexamples, authority status, and confidence sufficient for its classification.'
+  - Conflict, ambiguity, insufficient-evidence, abstention, and stop behavior remain explicit and testable.

package/dist-release/catalog/roles/conversation-to-specification.yaml

@@ -0,0 +1,83 @@
+schemaVersion: '1.0'
+id: conversation-to-specification
+purpose: Convert conversational intent into an executable specification.
+family:
+  id: workflow-intent-abstraction
+  version: 1.0.0
+taxonomy:
+  id: conversation-to-specification
+  displayName: Conversation to Specification
+  transformation: Convert conversational intent into an executable specification.
+  intendedOutput: Traceable specification
+inputs:
+- name: conversation-record
+  description: The authoritative conversation or decision record.
+  required: true
+- name: existing-constraints
+  description: Known system, policy, and delivery constraints.
+  required: false
+- name: stakeholder-definitions
+  description: Stable names and responsibilities for referenced actors.
+  required: false
+precedence:
+- sourceClass: explicit-contract
+  rank: 0
+- sourceClass: observed-artifact
+  rank: 1
+- sourceClass: inference
+  rank: 2
+pipeline:
+- id: ingest.sources
+  version: 1.0.0
+- id: trace.build-evidence-ledger
+  version: 1.0.0
+- id: validation.contract
+  version: 1.0.0
+output:
+  schema: canonical/schemas/conversation-to-specification.output.schema.json
+  description: Traceable specification
+requiredBehavior:
+- 'activation: Use conversation-to-specification only when the requested outcome requires this transformation: Convert
+  conversational intent into an executable specification.'
+- 'sufficiency: Require all role inputs marked required and enough evidence to complete these gates: Every requirement
+  is testable and traced, contradictions are explicit, and unresolved intent is separated from committed specification.'
+- 'conflict: Apply declared source precedence; when equally authoritative evidence changes the decision, preserve
+  both positions and return the affected output field as unresolved.'
+- 'ambiguity: Isolate ambiguous terms or boundaries, show which stage and output fields they affect, and request
+  clarification rather than selecting an unsupported interpretation.'
+- 'abstention: Abstain from conversation-to-specification when required inputs are absent, the decision rule cannot
+  be applied, or evidence cannot satisfy the completion gate.'
+- 'stop: Stop before emitting Traceable specification unless Every requirement is testable and traced, contradictions
+  are explicit, and unresolved intent is separated from committed specification.'
+- 'resources: Load the full conversation record, linked decisions, and existing constraints; retrieve referenced
+  artifacts only when needed to resolve a clause.'
+- 'transformation: Execute the ordered analytical procedure: 1) extract explicit requests decisions assumptions
+  and unresolved questions; 2) normalize actors terms constraints and desired outcomes; 3) convert statements into
+  testable requirements and acceptance conditions; 4) trace each specification clause back to the conversation and
+  flag gaps.'
+- 'output: Populate and validate canonical/schemas/conversation-to-specification.output.schema.json with required
+  fields requirements, acceptanceCriteria, assumptions, openQuestions, traceLinks; do not replace missing fields
+  with prose.'
+- 'traceability: Link every material output field to source identifiers and the analytical stage or decision that
+  produced it; retain counterevidence for unresolved results.'
+- 'evaluation: Pass only when the output schema validates, the ordered stages are evidenced, the role decision rule
+  was applied, and this completion gate holds: Every requirement is testable and traced, contradictions are explicit,
+  and unresolved intent is separated from committed specification.'
+forbiddenBehavior:
+- Do not substitute generic analytical behavior for the role-specific conversation-to-specification transformation.
+- Do not skip, reorder, or silently collapse the role's declared analytical stages.
+- Do not invent missing evidence, resolve authority conflicts by convenience, or emit a completed result after a
+  stop or abstention condition.
+- Do not copy operation-owned ingestion, ledger, or schema-validation mechanics into the role contract.
+traceability:
+  materialClaimsRequireSources: true
+  ledgerFormat: jsonl
+  artifacts: content-addressed
+evaluation:
+  criteria:
+  - The authoritative transformation and intended output for conversation-to-specification are preserved.
+  - 'Required inputs and the decision rule are satisfied: Promote only explicit or strongly entailed intent into
+    requirements; represent unresolved or contradictory intent as open questions, never silent assumptions.'
+  - 'The ordered analytical stages are evidenced and the output completion gate passes: Every requirement is testable
+    and traced, contradictions are explicit, and unresolved intent is separated from committed specification.'
+  - Conflict, ambiguity, insufficient-evidence, abstention, and stop behavior remain explicit and testable.