Purpose drift
A later change from approved purpose is explicit rather than silently treated as the same use.
Evidence ceiling E3Proof boundary
DATA/1 · DATA RIGHTS & USAGE FABRIC
Data should not lose its obligations when it crosses a system boundary.
DATA/1 attaches a portable passport to data, binds every requested use to purpose/model-use/location/recipient/retention constraints, conservatively propagates declared rights through derivation, tracks model genealogy and follows revocation through declared lineage.
Reference data use
ALLOW
The synthetic forecasting read is allowed. The same dataset's TRAINING use is separately typed and denied because the passport does not grant it.
- DATASET
- reference:customer-operations
- PASSPORT
- sha256:649784e0f423ed9e25d5197faf7477dc6db3785037bb4aad186b697e61f7701a
- PURPOSE
- FORECASTING
- MODEL USE
- INFERENCE
- TRAINING ATTEMPT
- DENY
- CORE LINES
- 19
Data that carries its terms
LINEAGE + RIGHTS + PURPOSE + RETENTION
OpenLineage can supply execution lineage, DPV can supply data/purpose/legal-role vocabularies, ODRL can supply usage policies, and data contracts can supply schema/quality/terms. DATA/1 composes those references into a portable use boundary rather than replacing them.
Model-use typing
Inference, evaluation, training, fine-tuning and embedding are distinct uses.
Derived rights
Transformations conservatively inherit/intersect declared upstream constraints.
Model genealogy
Training-class uses bind model artifacts to their declared source passports and obligations.
Data airlock
Purpose + credential + environment + sensitivity gates progressively disclose/use protected data.
Revocation impact
Declared downstream datasets, models and usage receipts become inspectable blast radius.