This is the boring machinery that makes data sharing defensible: intake, triage, risk review, decision, publication, audit. You are not trying to make everyone happy. You are trying to make the decision traceable.
This does not change the real platform. It saves your selected knobs as a simple posture that the DSI Pilot Live Studio can use as default agreement settings.
Open maximises fairness and innovation. Restricted protects privacy and safety. Registered is often the pragmatic middle.
Common failure
Publishing data without the “what it is not” section. People then use it for the exact thing it cannot support, and you get blamed.
Common theatre
A policy that looks strict but is impossible to operate. People bypass it, then you pretend you did not notice.
This is the “boardroom-friendly” trace. It is intentionally copyable, not downloadable.
Trust Under Load - Governance Engine (copyable memo) Case: Bilateral dispute (template) Status: intake Access tier: registered Interim release: Yes (time-boxed) Audit trail: Required Provenance notes: Required Minimum defensible evidence: - Data classification and sensitivity (including inference risk) - Legal basis and constraints for sharing - Misuse threat model and mitigations - Operational need and minimum viable utility Operator notes: (none yet)