Crew team context (strategy, philosophy, overview)

What each part is

Part	What it says	Who writes it	Size
Strategy	The bet the crew is making and why — only the owner-approved version	The lead drafts, the owner approves	Its TL;DR, at most 1,200 characters
Philosophy	What the crew values and how it settles a trade-off no rule covers	The crew lead, or you	At most 2,000 characters
Mission overview	What the crew is doing right now, where it stands, what comes next	The crew lead, kept current	At most 1,500 characters
Rules	Traps the crew already paid for, written once	The crew lead	See the rules file page

The whole team-context block stays under 5,500 characters (about 1,400 tokens), so it never crowds out a helper's actual task.

When helpers see it

• In their first message. Every helper a crew member starts gets the block before its task: Claude helpers, helpers on other engines, local and cloud alike.
• When it changes. A long-running helper gets the new version on its next turn after the lead changes it. An unchanged block is not repeated.
• After a compaction. When a helper's conversation is compacted, the block (and the rules) come back on its next turn.
• One small gap: a worker started by the crew's work queue can miss the block on its very first turn; it gets it from its second turn.

Keeping it current

• The crew lead sees the current overview on every wake, with the command to update it, or a one-line ask to write one if there is none yet.
• The lead writes and edits all of these with the ordinary mission-document commands — no approval card is raised for a philosophy or an overview.
• You can edit any of them yourself at any time: open the crew in the Overseers hub, go to Mission documents, and edit the document (or choose New document and pick Philosophy, Overview, Strategy or Rules).
• A philosophy or overview that is too long is refused with the limit named, so the lead trims it rather than having it cut off silently.
• A new strategy still needs your approval before helpers see it.

For agents

• Read: GET /crew/docs, then GET /crew/docs/:id/revisions/:revisionId for the full text.
• Write (lead only): POST /crew/docs / PATCH /crew/docs/:id with kind philosophy or overview and frontmatter kind: philosophy / kind: overview.
• The block arrives fenced as <omniscio-crew-team-context>; the rules arrive as <omniscio-crew-rules>.