Skip to content

Record real backplane issue links and advance only the verified Pension-Data producer #2743

Description

@stranske

Target: stranske/Workflows
Priority: P1
Depends on: Pension-Data #703 merged with a captured conformant reference run

Why

config/backplane_participants.json still contains a TBD parent issue and TBD participant issue links. Its lifecycle contract is planned -> emitting -> conformant, while docs/contracts/research-backplane-contract.md:95-109 requires central registry truth. Leaving placeholder links and declaring status from schema presence would repeat the built-but-not-flowing failure. Pension-Data should advance only after its participant-owned emitter has produced a real validated reference run.

Scope

Replace placeholder coordination links with real GitHub references, attach Pension-Data's reference-run evidence, and advance only Pension-Data through the central lifecycle. Keep all other producers honestly planned and LMS candidate/no-op.

Non-Goals

  • Do not modify Pension-Data source in this Workflows issue.
  • Do not advance any other participant or activate LMS.
  • Do not infer conformant from a passing schema fixture without a real participant CI run.
  • Scaffold-only completion does NOT count: replacing TBD strings without a real parent issue, participant issue, reference artifact, CI URL, and lifecycle evidence is incomplete.

Tasks

  • Use this issue as the real Workflows parent coordination issue and update config/backplane_participants.json::parent_issue to this issue's URL.
  • Replace each participant TBD issue with a real issue link or an explicit deferred/retired decision plus expiry; do not fabricate implementation status.
  • Create scripts/validate_backplane_registry.py and tests/test_backplane_registry.py to validate real issue links/deferred expiries, evidence-backed transitions, and reference-run requirements offline.
  • Attach Pension-Data's merged emitter PR, participant conformance run URL, artifact hash, and generated timestamp to the registry/report evidence.
  • Advance Pension-Data planned -> emitting when the emitter exists, then emitting -> conformant only when the real reference run passes the reusable workflow; preserve transition timestamps/history.
  • Update the backplane health/dashboard so stale/missing/invalid/valid reference state is distinct from participant lifecycle state.

Acceptance Criteria

  • python scripts/validate_backplane_registry.py --strict reports zero TBD links and validates every real issue URL/deferred expiry.
  • A registry-transition test rejects conformant when the participant CI URL or reference artifact hash is missing/invalid.
  • Pension-Data alone becomes conformant with captured evidence; the other five producers remain planned/deferred and LMS remains candidate/no-op.
  • Deliberate break: in tests/test_backplane_registry.py::pension_conformant_entry, delete only reference_run_sha256; run python -m pytest -q tests/test_backplane_registry.py::test_conformant_requires_reference_evidence; observe AssertionError: conformant participant lacks reference evidence; revert and show the exact test passes.

Implementation Notes

Workflows remains the contract owner, not a participant. This issue is the first machine-proven registry transition and should become the lifecycle template for later producers.

Cross-repo linkage

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions