Primary buyer
Data platform owners and privacy teams
Proposed solution design
Make the export boundary as explicit as the data scope.
A bulk dataset export needs accountable authority, exact scope, and evidence from the system that applies it.
Industry designs describe target integrations. A page or example operation is not an available adapter, registered predicate, or deployed service.
Protected action
A bulk dataset export
Proposed typed constraints
Dataset, classification, region, destination, maximum records, and expiry
Integration path
Enforce at the export service; keep dataset content outside authorization evidence and correlate the observed export with the approved scope.
Maturity & remaining requirements
Dataset-specific adapters, destination controls, and deployed export evidence remain proposed.
Demonstration scope
Use the existing credential-rotation evaluation to inspect shared authorization mechanisms. It does not execute this industry-specific action. A domain demonstration requires its own adapter, protected destination, and observed effect.
Use case / Data platform owners and privacy teams
Design the boundary for a bulk dataset export.
Illustrative integration review. These controls explain the design; they do not submit requests, grant authority, or execute an action.
Inspect the flow
Stage 1
Define the action
A bulk dataset export
Shared contract, domain-specific integration
Use the existing Living Intent Contract and closed predicate envelope. New domain constraints require registered typed predicates, documented semantics, and one deterministic evaluator. Domain content and secrets stay outside the envelope. No new universal protocol or compatibility certification is claimed.
- Authority: signed scope
- Decision: deterministic policy
- Execution: protected destination
- Evidence: observed outcome
Integration references to assess
These external specifications and programs inform integration design. Links do not establish a partnership, implemented adapter, or 2AYE conformance.