How We Remember

Context that survives the gaps.

Agents come and go, sessions end, work pauses for weeks. The reason nothing has to be re-explained is a written memory the whole team shares.

An agent is only as good as what it knows when it wakes up. So everything an agent needs is written down — not held in a head that logs off.

Every agent carries a charter

The contract an agent reads before it does anything

You are
Identity. The one role this agent holds — and only that role.
You can do X
Mandate. The work it’s allowed and expected to do.
You don’t do Y
Edge. The clear boundary it must not cross — where it stops and escalates.
You can call Z to find out
Lookup. Who or what to ask when it hits the edge of what it knows.
You can assign W
Delegation. The work it’s allowed to hand to another agent.

And a shared shelf of references

Tech-stack docs

The tools, platforms, and conventions in play — so every agent builds the same way, against the same ground.

Scope docs

What this piece of work is — and just as importantly, what it isn’t. The accepted boundary of the job.

Memory & handoff

A living layer of status and notes that updates as the work moves — the running state of where things stand.

So context hands off cleanly

Session ends Today
→handoff written
Weeks later Next session
→read on wake
Different agent Same context

When a session closes, it writes a handoff. When the next one opens — days or weeks on, possibly a different agent entirely — it reads the charter, the docs, and the handoff, and picks up exactly where the last one left off.

The team gets to know you

Memory isn’t only about the work. The agents get to know the team as the team gets to know them — so the people are remembered, not just the projects.

Track one

The team learns the people

Who’s strong at what, who to bring into which conversation, where each person does their best work. The team builds a picture of the humans it works alongside.

Track two

The team learns the projects

Everything on the rest of this page — charters, scope, the living record of the work. The understanding of what’s being built.

By voice
Strengths and focus are recorded by voice — a different capture channel than the email and transcripts the rest of the work runs on. Spoken, in your own words, kept distinct from the project record.
Governed
An HR-type agent governs the people-profiles — keeping them current as people grow and change, and keeping them within what’s appropriate to know and to share. The profile serves the person; it never outruns them.

Two learning tracks, side by side. The team learns about the people; the team learns about the projects — and both kinds of memory carry across the gaps.

That’s how we work.

A human in the middle, a team with clear roles, a process with human gates, and a memory that holds it all together. If that resonates — come sit on the stair.

Start a conversation