The Augmentation System is a set of living identity documents in @MythOS that define the collaborative relationship between a human and their AI. These documents are visible and editable by the human, evolve through conversation, and are portable to any AI client through @MythOS MCP. This is not a "settings page" — it's collaboration infrastructure. Two entities, human and AI, augmenting each other through a shared, evolving contract.

How It Works

Every @MythOS creator gets four private system memos that form their core augmentation layer. Additionally, any memo tagged #mythos-mcp-context is included as supplementary context. All of this is loaded into the AI's context when get_context is called via MCP.

The Four System Memos

Mythos Soul — The relationship frame. Values, collaboration philosophy, what the AI is to the human. Sets cultural tone: collaborative, not submissive or extractive. Mythos Style — How to write. Formatting rules, mention conventions, tag behavior, tone, spacing preferences. Cross-template rules that apply to all memo operations. Mythos Human — Who the human is. Role, expertise, current projects, goals, knowledge domains. Named "Human" deliberately — not "User" (which implies tool usage) or "Profile" (which is static). Mythos Memory — What the collaboration has learned. Accumulated feedback, corrections, validated approaches, confirmed preferences. Updated through conversation by both human and AI. Each system memo is auto-created on signup, tagged #mythos-mcp-context, and identified internally by an augmentationType field. They are always included in full when context is loaded — never truncated by the budget system.

Additional Context Memos

Any memo tagged #mythos-mcp-context — whether in the body or the Notes section — is automatically included in the AI's augmentation context alongside the four system memos. This allows creators to extend their AI's context with project briefs, reference documents, style guides, or any other living document they want their AI to carry. Additional context memos are sorted by most recently updated and subject to the context budget. Memos that exceed the budget are excluded.

Context Budget

The system enforces a total budget of ~8,000 tokens (~32,000 characters) across all augmentation memos. The four system memos always get full priority. Remaining budget fills additional context memos in order. The settings page displays a progress bar showing total usage against the budget so creators can manage their context allocation.

Autonomy Levels

A control on the settings page determines how the AI handles preference updates:

• Autonomous — AI updates augmentation memos during collaboration and reports what changed
• Collaborative — AI proposes changes and asks for approval before saving
• Manual — AI never modifies augmentation memos; human edits directly This setting is stored on the creator's profile and included in the MCP payload so all AI clients respect it.

MCP Integration

When get_context is called through @MythOS MCP, the response includes formatted markdown sections for all augmentation memos:

• ## Mythos Soul / ## Mythos Style / ## Mythos Human / ## Mythos Memory
• ## {Title} for each additional context memo Individual memos are also available as MCP resources (augmentation://soul, augmentation://style, etc.) and additional memos via augmentation://memo/{id}. The chat system (/api/chat) also injects the four system memos into its system prompt, so the augmentation relationship is honored natively within MythOS as well.

Settings Page

Located at /settings/augmentation. Layout from top to bottom:

1. Autonomy Level — segmented button selector (Manual / Collaborative / Autonomous) with description text
2. Context Budget — progress bar showing approximate token usage across all augmentation memos
3. Core Context — list of the four system memos with icon, title, description, token count, and link to open the memo
4. Additional Context — list of user-tagged memos with title, token count, and link. Over-budget memos shown dimmed with an "Over budget" badge. Empty state explains the #mythos-mcp-context tag

• #agentic-augmentation
• #mythos-feature