schema_version: "1.0"
parity_id: dora-readiness-composer
sign_off_status: SIGNED_OFF
created: "2026-06-13"
created_by: "claude-sonnet-4-6 / cowork session"

source:
  type: guide
  path: "repo/guides/dora-readiness-composer.html"
  title: "DORA Readiness Composer"
  description: >
    4-stage linear AIN Bridge workflow guide: T300 (ICT Risk Gap Analyser) →
    T304 (Resilience Testing Designer) → T307 (Proportionality Assessment) →
    T310 (AP2 DORA Policy Mandate Builder). AIN Bridge orchestrator with
    postMessage prefill/run/capture. Diagnostic handoff from
    dora-readiness-diagnostic via URL hash #diag=. Composite Policy Mandate
    export assembles 4 stage mandates.

chaingraph_equivalent:
  type: chain
  path: "repo/chaingraph/chains/dora-readiness.html"
  chain_id: "dora-readiness"
  scenario: "B (Gap Assessment)"  # T300 → T302 → T310 is the closest ChainGraph match
  chaingraph_url: "https://ainumbers.co/chaingraph/chains/dora-readiness.html#scenario-gap"
  notes: >
    The composer's 4-stage linear sequence (T300→T304→T307→T310) is covered by
    Scenario B in the dora-readiness chain. T304 (Resilience Testing Designer)
    is not a dedicated step in the chain but is referenced in ART-29 domain 3
    remediation (Q7–Q9). The ChainGraph chain also provides AIN Bridge
    integration via ART-29 §4 artifact chaining rather than the composer's
    single-session postMessage pattern. The chain provides the same compliance
    outcome through a structured branching topology.

parity_matrix:
  - feature: "4-stage sequence T300→T304→T307→T310"
    source: true
    chaingraph: true
    notes: >
      T300/T307/T310 present in Scenario B. T304 coverage handled by ART-29
      Domain 3 (Resilience Testing) remediation and diagnostic routing.

  - feature: "T300 ICT Risk Gap Analyser step"
    source: true
    chaingraph: true
    notes: "Scenario B step 2"

  - feature: "T307 Proportionality Assessment step"
    source: true
    chaingraph: true
    notes: "Scenario B step 1 (common root, all scenarios)"

  - feature: "T310 AP2 DORA Policy Mandate Builder (terminal)"
    source: true
    chaingraph: true
    notes: "Terminal node, all scenarios"

  - feature: "AIN Bridge orchestrator (postMessage prefill/run/capture)"
    source: true
    chaingraph: true
    notes: >
      Chain integrates via ART-29 §4 artifact (execution_hash, chain block)
      rather than single-session postMessage; AIN Bridge handlers present in
      ART-29 node.

  - feature: "Diagnostic handoff via URL hash #diag="
    source: true
    chaingraph: true
    notes: >
      ART-29 is the equivalent ChainGraph diagnostic; its §4 JSON output
      anchors the chain rather than a hash passthrough.

  - feature: "Composite Policy Mandate assembling 4 stage mandates"
    source: true
    chaingraph: true
    notes: "T310 terminal step produces composite mandate from all scenario steps"

  - feature: "T304 Resilience Testing Designer as dedicated workflow step"
    source: true
    chaingraph: false
    notes: >
      PARTIAL — T304 is covered in ART-29 Domain 3 remediation links (Q7–Q9)
      but is not a discrete step in the dora-readiness chain. If needed in
      future, a Scenario D (testing) branch can be added.

  - feature: "sessionStorage ain_lang"
    source: true
    chaingraph: false
    notes: "REMOVED. ChainGraph nodes do not write ain_lang."

  - feature: "§4 execution_hash audit chain"
    source: false
    chaingraph: true
    notes: "NEW in ChainGraph — full §4 artifact anchoring at ART-29"

  - feature: "Branching topology (3 scenarios)"
    source: false
    chaingraph: true
    notes: "NEW — chain adds Incident (Scenario A) and Supervisory (Scenario C) paths beyond composer's linear scope"

gaps_in_chaingraph:
  - id: "T304-as-chain-step"
    description: >
      T304 (Resilience Testing Designer) is not a discrete step in any chain
      scenario. It is covered through ART-29 Domain 3 remediation. Consider
      adding Scenario D (Testing) to dora-readiness chain in a future wave.
    severity: "minor"
    workaround: "ART-29 Domain 3 remediation links to T304 directly"

improvements_in_chaingraph:
  - "3-scenario branching topology covers more DORA compliance paths than the linear composer"
  - "§4 hash-anchored artifacts provide machine-verifiable audit trail"
  - "Chain persists across sessions via §4 JSON export (vs. composer's ephemeral postMessage)"
  - "sessionStorage ain_lang violation removed"

deletion_gate:
  ready_to_delete_source: false
  blocking_reason: "Awaiting Tim sign-off on parity + T304 gap acknowledged"
  delete_command: >
    # Tim runs in PowerShell after sign-off:
    # Remove-Item C:\dev\Claude\Projects\AINumbers\repo\guides\dora-readiness-composer.html
    # git add -A; git commit -m "chore: delete guides/dora-readiness-composer — parity live at chains/dora-readiness (Scenario B)"
