Validate machine-readable federation charters

[maziyarpanahi]

Summary

Participants cannot reliably determine who may join, what may be trained, how decisions are made, or how a federation ends from prose alone.

Scope

• Define a charter contract for roles, permitted tasks, quorum, privacy ceilings, incident response, appeals, and termination.
• Validate every round against the active charter version and preserve amendment history.

Acceptance criteria

• The implementation is deterministic and performs no mandatory network call.
• Logs, exceptions, reports, and fixtures contain no raw sensitive values.
• .venv/bin/python -m pytest tests/unit/governance/test_federation_charter.py -q

Out of scope

• A compliance certification or autonomous clinical decision guarantee.
• Bundling restricted datasets, credentials, or proprietary services.
• Unrelated changes to release publishing or existing public APIs.

Files

• openmed/governance/federation_charter.py
• tests/unit/governance/test_federation_charter.py
• docs/governance/federation-charters.md

---

Task: OM-171d · Milestone: v3.3 · Priority: P0 · Size: M
Depends on: — · Blocks: —
Roadmap: Audited V3 horizon expansion, 2026-08-13: OPENMED_V3_HORIZON_BRIEF.md section 3; OPENMED_BENCHMARK_PORTFOLIO_AND_TRUST.md section 9
Spec: PLANS/V2/EXECUTION/tasks/OM-171d.md