wiki/attractors/provenance
Provenance
wiki/attractors/provenance/index.mdRendered from markdown source. Open raw source on GitHub.
Provenance
This page is an attractor gateway, not a canon declaration. It compresses current evidence in the Work Vault and points toward underlying research.
<!-- BEGIN CURATED SEMANTIC COMPRESSION -->
Semantic Compression
In this vault, provenance is the lineage of meaning: the preservation of origin, context, transformation, authorship, admissibility, and consent conditions as an artifact moves through time.
Why It Matters
Provenance determines whether a record can be trusted without pretending that context is disposable. It binds memory to consent, witness to accountability, and artifact history to future use.
Core Motifs
- lineage
- authorship
- transformation
- admissibility
- consentful recordkeeping
- source of record
- context preservation
<!-- END CURATED SEMANTIC COMPRESSION -->
<!-- BEGIN GENERATED EVIDENCE MAP -->
Primary Research
- The Historical Record of the Future Requires Consentful Loops
- The Consentocracy Bridge
- Forgetting-First AI
- Privacy Is a Membrane, Not a Wall
- Machine Invitation
Adjacent Research
- Decision Provenance
- Stable Artifacts, Tunable Projections
- Shimmery Memory Publishing Contract
- IPOL
- From Archive to Interface
Related Projects
Related Concepts
Related Invariants
- P1 - Boundary and Interface
- P3 - Authorization and Consent Gate
- P4 - Legibility and Interpretability
- P5 - Conservation and Accounting
- P7 - Incentive Drift and Attractors
- P8 - Reversibility and Exit
- C2 - Ledgered Reciprocity
- C5 - Boundary-Accounting Misalignment
- C11 - Illegitimate Constitutional Comparator
Unresolved / Needs Link Resolution
- No unresolved seed links in this pass.
<!-- END GENERATED EVIDENCE MAP -->
<!-- BEGIN OPEN RESEARCH EDGES -->
Open Questions
- What makes a trace admissible?
- How much context must travel with an artifact?
- Can provenance be consentful without being controlling?
Next Navigation
- Start with The Historical Record of the Future Requires Consentful Loops.
- Continue to Continuity Office for operational provenance.
- Use Memory when provenance becomes recurrence, archive, or forgetting policy.
<!-- END OPEN RESEARCH EDGES -->