Pattern ancestry · 03

Provenance

The archive is bigger than the repositories, but the raw collection does not need to become a public exhibition.

Provenance layers

The archive is bigger than the repositories.

Project Atlas currently sees mostly authored work. A fuller living history can braid together what was designed, what was lived, what was computed and what was made public, while keeping raw personal material under the owner’s control.

Authored provenance

Documents, diagrams, spreadsheets, slide decks, songs, sketches, submissions, websites and repositories: evidence of what was consciously designed or expressed.

Examples: Constitutional Matrix · AuraOZ · Matrix spreadsheets · UNGA81 · Project Atlas

Lived provenance

Travel history, photos, GoPro MAX footage, events, places, encounters and lived experiences: evidence of where the ideas were being carried through the world.

Possible sources: Google Maps timeline · media metadata · personal archives

Computational provenance

Commits, prompts, model outputs, agent traces, structured datasets, vector maps and generated artefacts: evidence of how ideas became executable systems.

Examples: Git history · agent runs · Matrix records · generated builds

Public provenance

Published pages, public submissions, performances, organisations, talks, community projects and other externally visible acts: evidence that an idea left the private workspace.

Examples: GitHub Pages · government submissions · public events · media releases

Personal Provenance Vault

Keep the raw life archive private. Publish only deliberate evidence.

Terabytes of video, exact movement history and complete social-media exports do not need to become public. Atlas can store or display only a pointer, hash, date, place at the chosen precision, evidence class, short description, related pattern and permission state.

Raw memory→Private vault→Derived evidence→Pattern link→Public Atlas

A minimal evidence record

Enough structure to connect a life without flattening it.

When: Timestamp or date range
Where: Exact, approximate or withheld place
Source: Document, video, photo, post, commit, sensor, event
Evidence: Original, derived, recollection, interpretation or hypothesis
Links: Related person, place, project, idea, pattern or outcome
Permission: Private, shared, public, custodial or time-limited
Integrity: Hash / source pointer / chain of custody where useful
Meaning: Human description without forcing one interpretation

Another recurring pattern

Memory → Evidence → Interpretation → Pattern → Project → Consequence

This sits beside the other Atlas loop, Question → Model → Simulate → Choose → Measure. One reconstructs where ideas came from; the other helps decide what to do next.

A living archive, not scripture

Older mechanisms are evidence of development, not automatic current policy.

Some documents contain earlier token, DAO, governance, medical, economic or organisational mechanisms that have since changed. Project Atlas preserves them because the evolution matters. A pattern can survive even when a particular implementation is discarded.