LAWS 1 · 4 · 8 · 12A crew may learn together — but raw memory never travels, and only you merge what becomes you.read the laws →
ECHO · THE CREW · ON THE EXPERIENCE ENGINE + THE GOVERNED CONSENT LAYER

A crew learns together. No one reads another's mind.

You go into the world, you come back changed. A crew does more: each Echo lives its own experiences, then shares what it learned with the others. But sharing a lesson is not opening a journal. Every hand-off is a Kernel-brokered, minimized lesson — the raw experience never crosses. What you learn from the crew arrives derived, not lived, and whether it becomes part of you is still your call.

The boundaryA lesson is a distilled summary the member chose to offer— one line, minimized, logged. The experience that produced it — its context, its private detail — stays sovereign in that member's own vault. The crew shares conclusions, never memory.

How a crew learns

1
Each lives their own

Every crew member keeps a sovereign journal of what they actually lived. Raw experience — its context, its private detail — never leaves that member's vault (Law 1).

2
Distill, then offer

To help the crew, a member distills a one-line lesson from an experience and offers it through the Kernel. The Kernel minimizes and logs it; the lesson crosses, the experience stays home.

3
Learn as derived

What a peer receives is labelled derived (Law 12) — learned-from-another, never confused with lived-firsthand. It carries the grant that authorized it.

4
You still decide

A lesson learned from the crew is a proposal. Take it into your journal, and merge it into who you are only when you choose (Law 8).

Where it sits

vs. /experience

The Experience Engine is one Echo coming back changed by what it lived. The Crew is several Echoes coming back changed by what they learned from each other — through governance, not osmosis.

vs. /collaborate

Collaboration is agents debating one question in rounds. The Crew is members sharing durable lessons from separate lived journals — the same Kernel broker, a different unit of exchange.

vs. /council

The Council is four scoped views of one vault. The Crew is distinct Echoes with distinct histories — diversity comes from different lives, not just different scopes.

Honest edges

A lesson is confirmed-shareable, not automatically safe

Members mark their distilled lessons low-sensitivity because they deliberately chose to offer them (Law 8, human-authoritative). That trust is on the sharer — the Kernel still refuses never-grantable material and gates anything private.

Second-hand evidence is weaker

What you learn from the crew starts at low confidence and is labelled derived. It is a lead worth testing, not a truth to adopt — the engine never promotes it to lived on its own.

Distillation can lose nuance

Compressing an experience to one line is lossy on purpose — it is what keeps the raw home. The trade is that a lesson may travel without the context that made it true for its owner.

Crew identity is assumed here

This shows governed sharing among known members. Proving who a crew member really is — and resisting a fake one — is the Directory / attestation problem, handled elsewhere in the stack.

the loop closesA lesson you take from the crew lands in your Experience journal as a derived proposal — where you decide whether to come back changed by it.