Expressed Ownership

Reattaching what you express to who owns it

The Frame

EXO reattaches what you express to who owns it — and today it's a concept, not code

EXO (Expressed Ownership) is a protocol-first, tech-agnostic framework for making what you express attributable, protected, and portable in the age of AI.

Its status is honest up front: a pre-implementation framework, defined but not yet built.

0

source files implementing EXO — it's a conceptual framework, no code yet

3

promises of the protocol: attributable, protected, portable

Proof

The gap is bridgeable: attribution can already be tracked

AI systems now author memories about us that we didn't write and can't access. Yet attribution is not hypothetical — Amplifier already records AI co-authorship on its commits.

If a tool can already mark who authored what, then reattaching ownership is an engineering gap, not a fantasy.

10 / 50

of amplifier-foundation's last 50 commit bodies carry a Co-authored-by trailer

The Break

Capture went from monitoring to authoring — and your expression became theirs

The systems that record you no longer just watch. With AI, they compose digital memories about you. What you express is now owned by the platforms that capture it, not by you.

Expression has been severed from ownership. The rest of this deck is about reattaching them.

The Mechanism

EXO separates ownership into four clean types

The core move is a rule for who owns what — making reattachment tractable instead of vague.

With ownership typed, the framework can borrow from prior art to make it real.

Idea

Attributed to you

Knowledge

Owned / licensed by source

Expression

Contextually co-owned

Outcome

Fully yours

The Lineage

EXO synthesizes prior art into one portable, tech-agnostic protocol

It doesn't start from zero. It reframes existing efforts as a single portable protocol rather than four separate systems.

A credible lineage — which points to an existing system that could carry it.

Data Dignity

Jaron Lanier

Solid

Tim Berners-Lee

SSI & DIDs

Self-sovereign identity

Web3

Smart contracts

The Turn

Amplifier could be the right vehicle for EXO

An existing system already shows the behaviors EXO needs — not as a promise, but as things it does today.

Which sets up the point the whole deck drives toward.

1

Already captures session transcripts of what you express

2

Already tracks attribution via co-authored commits

3

Is modular and event-driven — extensible by design

The Payoff

Leave with your thesis — the platform keeps its equipment

When you leave a university, you take what you learned and your thesis — your expression. The curriculum and the lab equipment — the platform — stay behind.

That reattachment of expression to ownership is exactly what EXO is designed to do.

The Invitation

EXO is an open, pre-implementation invitation

The protocol is defined. No code exists yet. Amplifier is a proposed starting point — where the reattachment of expression to ownership could begin.

Designed, not built. The next move is to build it.

Sources

Research Methodology

Feature status: Conceptual framework — no code implementation exists (pre-implementation concept, no git metrics).

Deck source: docs/exo-protocol-deck.html, 896 lines, in the amplifier-stories repo.

Research performed:

Co-authorship count: git -C amplifier-foundation log --format='%b' -50 | grep -ci 'co-authored-by' → 10 of last 50 commit bodies.
No EXO source code: grep -rli 'expressed ownership' --include=*.py --include=*.rs --include=*.ts /home/ramparte/dev/ANext → 0 files.
Ownership types & status verbatim: grep -iE 'Status:|Author:|Nature:|Data:' docs/exo-protocol-deck.html.
Deck git history: git log --format='%h | %ai | %an | %s' -- docs/exo-protocol-deck.html (first staged 2026-01-30 by Alex Lopez; current version e09aeaf, 2026-07-14).
Suggested repo check: git -C amplifier-protocol-bridge remote -v → unrelated to EXO (Amplifier CLI reference implementation for microsoft/amplifier-core).

Gaps: "Framework originator" (Sam Schillace) is a deck assertion, not independently confirmable from git — earliest committer of the deck file is Alex Lopez. Prior-art frameworks (Data Dignity, Solid, SSI & DIDs, Web3) are the deck's own external references, not verified against any repo. PR #18 (merged 2026-01-31) verified from a corpus markdown snapshot, not a live gh query.