a product extension of you.md

You are the context.
Your bots are the workforce.

You.md gives every agent the right version of you. Bot.md gives the work a persistent team: people-like roles, durable memory, clear ownership, and the ability to keep moving across projects, machines, models, and harnesses. It is one authenticated product system, not a second account.

Read the thesis ↓Open the alignment desk

the owner layer

you.md

identity · memory · goals · trust

the delegated layer

bot.md

roles · teams · work · continuity

the sharp idea

Stop managing sessions.
Manage the workforce.

The current agent world makes every conversation look like a new project. That is backwards. Projects, goals, bots, and outcomes are durable. Sessions are just the places where work happens.

You.md

the person

Identity, private memory, preferences, projects, machines, models, skills, source context, and the rules that make an agent feel like it already knows you.

Bot.md

the team

Persistent delegated teammates with mandates, personalities, memory, relationships, authority, review obligations, and responsibility for outcomes.

The magic is not that a bot can code. It is that Houston can open the portfolio in the morning and know what matters, what moved, what is blocked, and what decision is next without reconstructing it from forty sessions.

one control plane

A fleet that feels like one mind.

Bot.md does not replace Claude Code, Codex, Cursor, Grok, OpenCode, Hermes, or the next harness. It makes them interchangeable execution surfaces for durable bot work.

bot.md / control room

morning portfolio briefing

● evidence live

focusMake sessions disappear into work.

lead botProject Lead / watching 4 workstreams

changed2 artifacts since last review

next decisionApprove connected-access proof

You

identity, memory, values, private context

→

Bot teams

roles, mandates, memory, relationships

→

Work graph

goals, runs, artifacts, review

the durable objects

Sessions become evidence.

The work graph is what survives. A session can start on a laptop, continue in the cloud, hand off to a reviewer, and still belong to the same bot-owned goal.

human

You

One owner with a coherent brain, not a user record replicated across apps.

direction

Project + goal

The durable scope and outcome that make every run legible.

agency

Bot + team

A named delegate with responsibility, personality, and limits.

execution

Run + session

A bounded attempt in a harness, machine, or model—not the primary unit of organization.

truth

Artifact + review

Evidence that something changed, passed, failed, or still needs a decision.

trust

Capability + lease

A scoped, expiring permission to act through API, MCP, CLI, browser, or computer use.

the trust boundary

Connected does not mean all-powerful.

Long-tail software has no API. Bots still need to work there. The answer is a governed capability layer—not raw cookies pasted into prompts or a vault that every bot can read.

preferred path

API → MCP → CLI

Typed, observable, least-privileged tools are the default. The bot sees structured results, not secrets.

typedauditedrevocable

fallback path

Browser → computer use

A local helper holds the live session. The bot receives a narrow access lease and redacted evidence, not the underlying cookie.

origin-boundtime-limitedhuman approval

“Share my login with this bot” should mean grant this bot a narrow capability through the local helper—not paste a credential into a Markdown file.

research changed the plan

Absorb the runtime.
Own the product.

Rakazo proves much of the persistent-teammate substrate. botdirectory.ai proves that portable Markdown bot definitions can seed distribution. The aligned direction is to fork and integrate the useful runtime primitives into the core You.md/Bot.md stack, with You.md authentication as the only private entry point.

internal runtime source

Rakazo-derived runtime

Persistent bots, routines, memory, shared/private computers, browser and terminal access, provider adapters, portable workspaces, and model credentials. Houston's repository is already an Apache-2.0 fork; useful primitives become native infrastructure, not a third product.

forkcustomizeattribute

ecosystem seed

botdirectory.ai

One Markdown file per bot, community pull requests, categories, integrations, and a public JSON feed. Useful as a compatibility importer—not the complete workforce product.

provenancecuratevalidate

adopt

Roster + work surface

Keep the bot emotionally legible and let activity, artifacts, computer state, and approvals explain one another.

differentiate

Portfolio control plane

Goals, context projection, cross-harness identity, session reconciliation, and the morning briefing belong above runtime sessions.

protect

Original trust language

Borrow interaction principles, not marks, copy, illustrations, or pixel-level layouts from reference products.

The product is unified: botdirectory.ai can help seed discovery. Rakazo-derived code helps the integrated runtime execute. You.md authenticates and gives Bot.md the context, trust, and accountability that make a bot a real teammate.

proof before sprawl

Start with one team.
Make it undeniable.

The first proof should happen inside You.md. If a two-bot team can eliminate one real morning/night ritual, the new abstraction is working.

Align the model

Approve the one-product boundary, `BOT.md` schema, You.md authentication, session projection, and credential policy.

exit: one source of truth

Make one team real

Project Lead + Reviewer inside one authenticated You.md project. Reconcile existing sessions and produce the morning briefing.

exit: the ritual disappears

Cross the fleet

Run the same bot through the integrated runtime on one local and one remote computer. Stop, resume, hand off, and preserve evidence.

exit: the work survives the machine

Open the primitive

Publish the schema, validator, runtime/harness contract, and forkable bot templates. Require You.md auth for install and execution.

exit: developers can adopt it

Earn the trust layer

Expand hosted coordination, encrypted vault brokering, governed browser sessions, audit, and managed execution inside You.md.

exit: adoption without surrender

alignment desk

Make the vision sharper.

This page is a collaboration object. Mark the questions that feel settled, then leave notes. Your notes are saved locally in this browser so the artifact can travel with the conversation.

Does “You.md is you; Bot.md is your bots” feel like one authenticated product system with a native workforce layer?

Is Project Lead + Reviewer the right first team to prove coordination and trust?

Which real project and morning/night ritual should be the first measurable proof?

Where should autonomous action stop and owner approval begin?

What should be open for adoption, and what must remain inside You.md's trust boundary?

Which Rakazo-derived runtime primitives should be integrated first, and what temporary compatibility seam keeps upstream synchronization safe?

Should Botdirectory.ai be mirrored, curated, or supported through a compatible importer?

private review notes

stored locally · not uploaded

You are the context.Your bots are the workforce.