Governance you can prove, not just assert.
Access decisions are attribute-based — jurisdiction × purpose × buyer classification × consent state — expressed as policy-as-code. Run the same policy in enforcement or attestation mode, and make machine-checkable claims about what will and won't be released.
What governance does.
Policy-as-code with Cedar
Policies are authored in Cedar, chosen for its formal-verification properties. That lets GateHouse make machine-checkable governance claims rather than assertions — a direct fit with the attestation model.
Configurable by design
Trust models, egress rules and autonomy levels are participant configuration, not fixed product decisions. Sellers may start restrictive — human-approved egress only — and open up gradually as trust builds.
Enforce or attest
The same policy runs two ways: block a release at the boundary, or prove after the fact exactly what a release did and did not disclose. Every decision is logged to a settlement-grade audit trail.
Commercial-impact preview
The policy editor shows the commercial consequence of a rule as you write it: "with this policy, these datasets become invisible to buyers." Governance and monetisation are edited in the same view.