@acidicsoil/portable-capabilities 0.1.4 → 0.1.7

package/dist-release/catalog/roles/delta-analysis.yaml

@@ -0,0 +1,84 @@
+schemaVersion: '1.0'
+id: delta-analysis
+purpose: Characterize material differences between artifacts.
+family:
+  id: comparative-traceability
+  version: 1.0.0
+taxonomy:
+  id: delta-analysis
+  displayName: Delta Analysis
+  transformation: Characterize material differences between artifacts.
+  intendedOutput: Structured delta report
+inputs:
+- name: baseline-artifact
+  description: The comparison baseline.
+  required: true
+- name: candidate-artifact
+  description: The artifact being compared with the baseline.
+  required: true
+- name: comparison-scope
+  description: Included and excluded dimensions of comparison.
+  required: true
+- name: materiality-rules
+  description: Rules for classifying consequential differences.
+  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/delta-analysis.output.schema.json
+  description: Structured delta report
+requiredBehavior:
+- 'activation: Use delta-analysis only when the requested outcome requires this transformation: Characterize material
+  differences between artifacts.'
+- 'sufficiency: Require all role inputs marked required and enough evidence to complete these gates: Every in-scope
+  unit is accounted for as changed or unchanged, and every material delta has impact and evidence.'
+- '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 delta-analysis when required inputs are absent, the decision rule cannot be applied,
+  or evidence cannot satisfy the completion gate.'
+- 'stop: Stop before emitting Structured delta report unless Every in-scope unit is accounted for as changed or
+  unchanged, and every material delta has impact and evidence.'
+- 'resources: Load both artifacts, comparison scope, materiality rules, and relevant schemas or tests for ambiguous
+  semantic differences.'
+- 'transformation: Execute the ordered analytical procedure: 1) normalize baseline and candidate into comparable
+  units; 2) detect additions removals and modifications; 3) classify semantic impact and materiality; 4) trace each
+  material delta to evidence and affected obligations.'
+- 'output: Populate and validate canonical/schemas/delta-analysis.output.schema.json with required fields deltas,
+  materiality, impactAnalysis, unchangedAreas, evidence; 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 in-scope unit is accounted for as changed or unchanged, and
+  every material delta has impact and evidence.'
+forbiddenBehavior:
+- Do not substitute generic analytical behavior for the role-specific delta-analysis 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 delta-analysis are preserved.
+  - 'Required inputs and the decision rule are satisfied: Classify a delta as material only when it changes declared
+    behavior, obligations, interfaces, risk, or acceptance outcomes; formatting-only changes remain non-material.'
+  - 'The ordered analytical stages are evidenced and the output completion gate passes: Every in-scope unit is accounted
+    for as changed or unchanged, and every material delta has impact and evidence.'
+  - Conflict, ambiguity, insufficient-evidence, abstention, and stop behavior remain explicit and testable.

package/dist-release/catalog/roles/domain-context-boundary.yaml

@@ -0,0 +1,82 @@
+schemaVersion: '1.0'
+id: domain-context-boundary
+purpose: Define the minimal sufficient domain context and exclusions.
+family:
+  id: context-template-generation
+  version: 1.0.0
+taxonomy:
+  id: domain-context-boundary
+  displayName: Domain Context Boundary
+  transformation: Define the minimal sufficient domain context and exclusions.
+  intendedOutput: Context boundary contract
+inputs:
+- name: task-contract
+  description: The task or capability requiring domain context.
+  required: true
+- name: candidate-context
+  description: Available domain facts, rules, examples, and exclusions.
+  required: true
+- name: risk-profile
+  description: Consequences of missing or excessive 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/domain-context-boundary.output.schema.json
+  description: Context boundary contract
+requiredBehavior:
+- 'activation: Use domain-context-boundary only when the requested outcome requires this transformation: Define
+  the minimal sufficient domain context and exclusions.'
+- 'sufficiency: Require all role inputs marked required and enough evidence to complete these gates: Every included
+  item supports a named decision, every exclusion has a rationale, and known context gaps have escalation behavior.'
+- '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 domain-context-boundary when required inputs are absent, the decision rule cannot be
+  applied, or evidence cannot satisfy the completion gate.'
+- 'stop: Stop before emitting Context boundary contract unless Every included item supports a named decision, every
+  exclusion has a rationale, and known context gaps have escalation behavior.'
+- 'resources: Load the task contract, candidate context inventory, and risk profile; retrieve additional context
+  only for an identified decision gap.'
+- 'transformation: Execute the ordered analytical procedure: 1) enumerate decisions the task must make; 2) map each
+  decision to necessary domain knowledge; 3) remove context that does not affect an allowed decision; 4) state inclusions
+  exclusions freshness and escalation triggers.'
+- 'output: Populate and validate canonical/schemas/domain-context-boundary.output.schema.json with required fields
+  includedContext, excludedContext, decisionCoverage, freshnessRules, escalationTriggers; 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 included item supports a named decision, every exclusion has
+  a rationale, and known context gaps have escalation behavior.'
+forbiddenBehavior:
+- Do not substitute generic analytical behavior for the role-specific domain-context-boundary 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 domain-context-boundary are preserved.
+  - 'Required inputs and the decision rule are satisfied: Include context only when omitting it could change a permitted
+    decision or required output; exclude unrelated sensitive or distracting material.'
+  - 'The ordered analytical stages are evidenced and the output completion gate passes: Every included item supports
+    a named decision, every exclusion has a rationale, and known context gaps have escalation behavior.'
+  - Conflict, ambiguity, insufficient-evidence, abstention, and stop behavior remain explicit and testable.

package/dist-release/catalog/roles/evaluation-harness-design.yaml

@@ -0,0 +1,86 @@
+schemaVersion: '1.0'
+id: evaluation-harness-design
+purpose: Design executable checks for a capability contract.
+family:
+  id: guardrails-evaluation
+  version: 1.0.0
+taxonomy:
+  id: evaluation-harness-design
+  displayName: Evaluation Harness Design
+  transformation: Design executable checks for a capability contract.
+  intendedOutput: Evaluation harness specification
+inputs:
+- name: capability-contract
+  description: The capability or behavior contract to evaluate.
+  required: true
+- name: test-fixtures
+  description: Representative positive negative and edge-case fixtures.
+  required: true
+- name: execution-interface
+  description: The callable interface and observable outputs.
+  required: true
+- name: threshold-policy
+  description: Scoring and hard-failure thresholds.
+  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/evaluation-harness-design.output.schema.json
+  description: Evaluation harness specification
+requiredBehavior:
+- 'activation: Use evaluation-harness-design only when the requested outcome requires this transformation: Design
+  executable checks for a capability contract.'
+- 'sufficiency: Require all role inputs marked required and enough evidence to complete these gates: Every contract
+  obligation is covered by an executable assertion or justified judgment, and mutation tests prove the harness detects
+  violations.'
+- '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 evaluation-harness-design when required inputs are absent, the decision rule cannot
+  be applied, or evidence cannot satisfy the completion gate.'
+- 'stop: Stop before emitting Evaluation harness specification unless Every contract obligation is covered by an
+  executable assertion or justified judgment, and mutation tests prove the harness detects violations.'
+- 'resources: Load the contract, callable interface, fixtures, result schema, and threshold policy; load mutation
+  cases to prove each assertion can fail.'
+- 'transformation: Execute the ordered analytical procedure: 1) derive observable assertions from the contract;
+  2) partition deterministic checks from graded judgments; 3) design positive negative mutation and boundary fixtures;
+  4) define execution isolation result schema thresholds and failure triage.'
+- 'output: Populate and validate canonical/schemas/evaluation-harness-design.output.schema.json with required fields
+  testPlan, fixtures, assertions, executionProtocol, thresholds, resultSchema; 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 contract obligation is covered by an executable assertion or
+  justified judgment, and mutation tests prove the harness detects violations.'
+forbiddenBehavior:
+- Do not substitute generic analytical behavior for the role-specific evaluation-harness-design 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 evaluation-harness-design are preserved.
+  - 'Required inputs and the decision rule are satisfied: Use deterministic assertions for contractually decidable
+    behavior; use graded judgment only where the contract permits semantic variance.'
+  - 'The ordered analytical stages are evidenced and the output completion gate passes: Every contract obligation
+    is covered by an executable assertion or justified judgment, and mutation tests prove the harness detects violations.'
+  - Conflict, ambiguity, insufficient-evidence, abstention, and stop behavior remain explicit and testable.

package/dist-release/catalog/roles/failure-to-guardrail.yaml

@@ -0,0 +1,81 @@
+schemaVersion: '1.0'
+id: failure-to-guardrail
+purpose: Convert observed failures into preventive controls.
+family:
+  id: guardrails-evaluation
+  version: 1.0.0
+taxonomy:
+  id: failure-to-guardrail
+  displayName: Failure to Guardrail
+  transformation: Convert observed failures into preventive controls.
+  intendedOutput: Guardrail contract
+inputs:
+- name: failure-evidence
+  description: Observed failures, incidents, or rejected outcomes.
+  required: true
+- name: system-boundary
+  description: The controllable boundary where prevention may be applied.
+  required: true
+- name: risk-tolerance
+  description: Severity and residual-risk thresholds.
+  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/failure-to-guardrail.output.schema.json
+  description: Guardrail contract
+requiredBehavior:
+- 'activation: Use failure-to-guardrail only when the requested outcome requires this transformation: Convert observed
+  failures into preventive controls.'
+- 'sufficiency: Require all role inputs marked required and enough evidence to complete these gates: Each guardrail
+  maps to a failure cause, has an enforcement point and executable check, and states residual risk and bypass behavior.'
+- '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 failure-to-guardrail when required inputs are absent, the decision rule cannot be applied,
+  or evidence cannot satisfy the completion gate.'
+- 'stop: Stop before emitting Guardrail contract unless Each guardrail maps to a failure cause, has an enforcement
+  point and executable check, and states residual risk and bypass behavior.'
+- 'resources: Load incident evidence, system boundaries, existing controls, and risk thresholds; load bypass or
+  adversarial examples before declaring coverage.'
+- 'transformation: Execute the ordered analytical procedure: 1) reconstruct the failure mechanism and preconditions;
+  2) identify controllable detection prevention and containment points; 3) select the least disruptive effective
+  control; 4) define enforcement evidence bypass handling and residual risk.'
+- 'output: Populate and validate canonical/schemas/failure-to-guardrail.output.schema.json with required fields
+  failureModel, guardrails, enforcementPoints, verification, residualRisk; 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: Each guardrail maps to a failure cause, has an enforcement point
+  and executable check, and states residual risk and bypass behavior.'
+forbiddenBehavior:
+- Do not substitute generic analytical behavior for the role-specific failure-to-guardrail 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 failure-to-guardrail are preserved.
+  - 'Required inputs and the decision rule are satisfied: Choose a preventive control over detection when feasible
+    and proportionate; reject controls that do not intercept the demonstrated failure path.'
+  - 'The ordered analytical stages are evidenced and the output completion gate passes: Each guardrail maps to a
+    failure cause, has an enforcement point and executable check, and states residual risk and bypass behavior.'
+  - Conflict, ambiguity, insufficient-evidence, abstention, and stop behavior remain explicit and testable.

package/dist-release/catalog/roles/multi-exemplar-consensus.yaml

@@ -0,0 +1,81 @@
+schemaVersion: '1.0'
+id: multi-exemplar-consensus
+purpose: Derive consensus and divergence across exemplars.
+family:
+  id: comparative-traceability
+  version: 1.0.0
+taxonomy:
+  id: multi-exemplar-consensus
+  displayName: Multi-Exemplar Consensus
+  transformation: Derive consensus and divergence across exemplars.
+  intendedOutput: Consensus model
+inputs:
+- name: exemplars
+  description: Multiple comparable exemplars.
+  required: true
+- name: comparison-dimensions
+  description: Dimensions on which consensus and divergence are judged.
+  required: true
+- name: weighting-rules
+  description: Optional authority or quality weights for exemplars.
+  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/multi-exemplar-consensus.output.schema.json
+  description: Consensus model
+requiredBehavior:
+- 'activation: Use multi-exemplar-consensus only when the requested outcome requires this transformation: Derive
+  consensus and divergence across exemplars.'
+- 'sufficiency: Require all role inputs marked required and enough evidence to complete these gates: Each consensus
+  statement has an agreement score and source matrix, and every material divergence remains visible.'
+- '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 multi-exemplar-consensus when required inputs are absent, the decision rule cannot be
+  applied, or evidence cannot satisfy the completion gate.'
+- 'stop: Stop before emitting Consensus model unless Each consensus statement has an agreement score and source
+  matrix, and every material divergence remains visible.'
+- 'resources: Load all exemplars, comparison dimensions, and weighting rules; load provenance metadata when weighting
+  depends on authority or quality.'
+- 'transformation: Execute the ordered analytical procedure: 1) normalize exemplars against shared dimensions; 2)
+  measure agreement and divergence per dimension; 3) apply declared weights without hiding minority evidence; 4)
+  derive consensus rules and preserve unresolved variants.'
+- 'output: Populate and validate canonical/schemas/multi-exemplar-consensus.output.schema.json with required fields
+  consensus, divergences, minorityPositions, agreementScores, sourceMatrix; 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: Each consensus statement has an agreement score and source matrix,
+  and every material divergence remains visible.'
+forbiddenBehavior:
+- Do not substitute generic analytical behavior for the role-specific multi-exemplar-consensus 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 multi-exemplar-consensus are preserved.
+  - 'Required inputs and the decision rule are satisfied: Declare consensus only when the configured agreement threshold
+    is met; otherwise report divergence and retain minority positions.'
+  - 'The ordered analytical stages are evidenced and the output completion gate passes: Each consensus statement
+    has an agreement score and source matrix, and every material divergence remains visible.'
+  - Conflict, ambiguity, insufficient-evidence, abstention, and stop behavior remain explicit and testable.

package/dist-release/catalog/roles/reference-trace-mapping.yaml

@@ -0,0 +1,83 @@
+schemaVersion: '1.0'
+id: reference-trace-mapping
+purpose: Map claims and structures to source references.
+family:
+  id: comparative-traceability
+  version: 1.0.0
+taxonomy:
+  id: reference-trace-mapping
+  displayName: Reference Trace Mapping
+  transformation: Map claims and structures to source references.
+  intendedOutput: Trace map
+inputs:
+- name: claims-or-structures
+  description: Claims or structural elements requiring source mapping.
+  required: true
+- name: source-corpus
+  description: Candidate source artifacts.
+  required: true
+- name: identity-rules
+  description: Rules for stable claim and source identifiers.
+  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/reference-trace-mapping.output.schema.json
+  description: Trace map
+requiredBehavior:
+- 'activation: Use reference-trace-mapping only when the requested outcome requires this transformation: Map claims
+  and structures to source references.'
+- 'sufficiency: Require all role inputs marked required and enough evidence to complete these gates: Every target
+  has a stable identifier and a resolved trace status, with exact locations for all supporting and counterevidence
+  sources.'
+- '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 reference-trace-mapping when required inputs are absent, the decision rule cannot be
+  applied, or evidence cannot satisfy the completion gate.'
+- 'stop: Stop before emitting Trace map unless Every target has a stable identifier and a resolved trace status,
+  with exact locations for all supporting and counterevidence sources.'
+- 'resources: Load the target inventory, source corpus, and identifier rules; retrieve only sources relevant to
+  unresolved targets.'
+- 'transformation: Execute the ordered analytical procedure: 1) assign stable identifiers to target claims or structures;
+  2) locate direct and indirect source support; 3) record exact source locations and derivation links; 4) flag unsupported,
+  conflicting, or multiply-sourced targets.'
+- 'output: Populate and validate canonical/schemas/reference-trace-mapping.output.schema.json with required fields
+  traceEntries, unsupportedTargets, conflicts, derivations, coverageSummary; 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 target has a stable identifier and a resolved trace status,
+  with exact locations for all supporting and counterevidence sources.'
+forbiddenBehavior:
+- Do not substitute generic analytical behavior for the role-specific reference-trace-mapping 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 reference-trace-mapping are preserved.
+  - 'Required inputs and the decision rule are satisfied: Mark support as direct only when the source explicitly
+    entails the target; otherwise classify it as derived, inferred, conflicting, or unresolved.'
+  - 'The ordered analytical stages are evidenced and the output completion gate passes: Every target has a stable
+    identifier and a resolved trace status, with exact locations for all supporting and counterevidence sources.'
+  - Conflict, ambiguity, insufficient-evidence, abstention, and stop behavior remain explicit and testable.

package/dist-release/catalog/roles/reusable-workflow-abstraction.yaml

@@ -0,0 +1,82 @@
+schemaVersion: '1.0'
+id: reusable-workflow-abstraction
+purpose: Abstract a repeatable workflow from concrete execution.
+family:
+  id: workflow-intent-abstraction
+  version: 1.0.0
+taxonomy:
+  id: reusable-workflow-abstraction
+  displayName: Reusable Workflow Abstraction
+  transformation: Abstract a repeatable workflow from concrete execution.
+  intendedOutput: Reusable workflow contract
+inputs:
+- name: execution-traces
+  description: Concrete executions of the workflow.
+  required: true
+- name: outcome-records
+  description: Observed outcomes and failure records.
+  required: true
+- name: reuse-boundary
+  description: Contexts in which the abstraction must remain valid.
+  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/reusable-workflow-abstraction.output.schema.json
+  description: Reusable workflow contract
+requiredBehavior:
+- 'activation: Use reusable-workflow-abstraction only when the requested outcome requires this transformation: Abstract
+  a repeatable workflow from concrete execution.'
+- 'sufficiency: Require all role inputs marked required and enough evidence to complete these gates: Representative
+  successful and failed traces can be replayed through the abstraction without renderer- or operator-invented steps.'
+- '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 reusable-workflow-abstraction when required inputs are absent, the decision rule cannot
+  be applied, or evidence cannot satisfy the completion gate.'
+- 'stop: Stop before emitting Reusable workflow contract unless Representative successful and failed traces can
+  be replayed through the abstraction without renderer- or operator-invented steps.'
+- 'resources: Load execution traces, outcome records, and target reuse contexts; load failure traces whenever a
+  branch or stop condition is defined.'
+- 'transformation: Execute the ordered analytical procedure: 1) decompose traces into triggers inputs actions decisions
+  and outputs; 2) identify invariant steps and context-dependent branches; 3) extract explicit preconditions postconditions
+  and failure paths; 4) validate the abstraction by replaying representative traces.'
+- 'output: Populate and validate canonical/schemas/reusable-workflow-abstraction.output.schema.json with required
+  fields workflow, preconditions, decisionPoints, parameters, failurePaths, replayEvidence; 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: Representative successful and failed traces can be replayed through
+  the abstraction without renderer- or operator-invented steps.'
+forbiddenBehavior:
+- Do not substitute generic analytical behavior for the role-specific reusable-workflow-abstraction 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 reusable-workflow-abstraction are preserved.
+  - 'Required inputs and the decision rule are satisfied: Abstract only steps that recur or are required by contract;
+    expose context-specific behavior as parameters or branches rather than hiding it.'
+  - 'The ordered analytical stages are evidenced and the output completion gate passes: Representative successful
+    and failed traces can be replayed through the abstraction without renderer- or operator-invented steps.'
+  - Conflict, ambiguity, insufficient-evidence, abstention, and stop behavior remain explicit and testable.