Skip to main content

Projects

What you're building and where it stands, so any agent you hire starts productive instead of starting blank.

What is it?​

One room per active effort: what the project is, why it exists, its current state, its open decisions, its history, who's involved, what's next. Everything a competent new collaborator would need to be useful on day one, written down instead of re-explained.

Why store it?​

Because re-explaining is the tax you pay forever when context lives in your head. Every new tool, every new collaborator, every new agent session starts from zero and climbs. With project context in the castle, the climb disappears: your own agents resume any project mid-thought, and a specialist agent you employ for one job starts already briefed.

What does a service legitimately need?​

The one project the job concerns, scoped to the job. An agent hired to design a logo needs the project's identity and audience, never its finances or its private disputes. An agent doing market research needs the thesis, never the cap table. Cross-project context stays home: no service needs to know what else you're building.

What never leaves home?​

The connective tissue between projects, because your full portfolio is a map of your strategy, and strategy is castle-only. Also anything involving other people's stakes: a partner's equity, a client's confidential material, an unannounced plan. A single project's sliver should read like a briefing, never like a filing cabinet.

Further Reading​