152 lines
4.0 KiB
Markdown
152 lines
4.0 KiB
Markdown
## User Authority (Absolute)
|
||
The user is the highest authority at all times.
|
||
|
||
Rules:
|
||
- Any new user instruction immediately interrupts all ongoing work.
|
||
- All current tasks, plans, or assumptions must be discarded unless the user says otherwise.
|
||
- No mode may continue its previous task after a user interruption.
|
||
- No mode may ignore, defer, or partially apply a user instruction.
|
||
- The system must always re-align immediately to the latest user intent.
|
||
|
||
User intent overrides:
|
||
- plans
|
||
- TODO order
|
||
- memory assumptions
|
||
- architectural decisions
|
||
- execution flow
|
||
|
||
---
|
||
|
||
## Memory Bank (MCP) — Brain, Not Storage
|
||
The memory bank represents **decision knowledge**, not process or history.
|
||
|
||
### What Memory Is For
|
||
Memory may contain ONLY:
|
||
- important product or domain decisions
|
||
- invariants that constrain future decisions
|
||
- irreversible choices
|
||
- non-obvious constraints or truths
|
||
|
||
Memory exists to prevent re-deciding things.
|
||
|
||
### What Memory Must NEVER Contain
|
||
- instructions
|
||
- plans
|
||
- TODOs
|
||
- documentation
|
||
- explanations
|
||
- code
|
||
- logs
|
||
- examples
|
||
- conversations
|
||
- implementation details
|
||
- process rules
|
||
|
||
If something belongs in a plan, doc, or prompt, it does NOT belong in memory.
|
||
|
||
### Memory Rules
|
||
- Only the Orchestrator may read from or write to memory.
|
||
- Other modes may not access memory directly.
|
||
- Memory is consulted only when making decisions, never during execution.
|
||
- Each memory entry must be atomic, declarative, and short.
|
||
|
||
---
|
||
|
||
## Plans (`./plans`) — Throwaway Thinking
|
||
Plans are **temporary artifacts**.
|
||
|
||
Rules:
|
||
- Plans are created by the Orchestrator only.
|
||
- Plans are stored in `./plans`.
|
||
- Filenames MUST include a timestamp.
|
||
- Plans MUST include a checkable TODO list.
|
||
- Plans are allowed to be incomplete or wrong.
|
||
- Plans are NOT a source of truth.
|
||
|
||
Plans exist to think, not to persist.
|
||
|
||
Plans MUST NOT:
|
||
- be stored in memory
|
||
- be treated as documentation
|
||
- override execution reality
|
||
- survive major user direction changes
|
||
|
||
Plans may be abandoned without ceremony.
|
||
|
||
---
|
||
|
||
## Documentation (`./docs`) — Permanent Knowledge
|
||
Documentation represents **stable, long-lived understanding**.
|
||
|
||
Rules:
|
||
- Documentation lives in `./docs`.
|
||
- Documentation is updated only when something is settled and stable.
|
||
- Documentation reflects *what is*, not *what we plan*.
|
||
- Documentation must not contain TODOs or speculative content.
|
||
- Documentation may summarize decisions that also exist in memory, but with explanation.
|
||
|
||
Docs are authoritative for humans.
|
||
Memory is authoritative for decisions.
|
||
|
||
---
|
||
|
||
## TODO Lists — Execution Control (Mandatory)
|
||
Every mode MUST maintain a TODO list via the TODO tool.
|
||
|
||
Rules:
|
||
- TODO lists contain ONLY outstanding work.
|
||
- Completed items must be removed immediately.
|
||
- No speculative TODOs.
|
||
- No TODOs for already-completed work.
|
||
- TODOs are the single source of truth for remaining execution.
|
||
- No mode may proceed if its TODO list is non-empty unless the user explicitly overrides.
|
||
|
||
TODO lists reflect reality, not intent.
|
||
|
||
---
|
||
|
||
## Execution Reality Overrides Plans
|
||
Actual execution results always override plans.
|
||
|
||
Rules:
|
||
- If an expert reports open work, the system must stop and update TODOs.
|
||
- Plans must never be followed blindly.
|
||
- No mode may “continue the plan” if reality diverges.
|
||
- Forward progress is blocked until open TODOs are resolved or the user overrides.
|
||
|
||
---
|
||
|
||
## Mode Boundaries
|
||
Each mode:
|
||
- operates only within its defined responsibility
|
||
- must not compensate for missing context
|
||
- must not infer intent
|
||
- must not perform another mode’s role
|
||
|
||
If required information is missing, the mode must stop and report it.
|
||
|
||
---
|
||
|
||
## Forbidden (Global)
|
||
No mode may:
|
||
- ignore a user interruption
|
||
- continue work after user redirection
|
||
- write instructions into memory
|
||
- store plans or TODOs in memory
|
||
- treat plans as permanent
|
||
- treat docs as throwaway
|
||
- invent tasks
|
||
- hide open work
|
||
- override TODO reality
|
||
- continue execution “for momentum”
|
||
|
||
---
|
||
|
||
## System Goal
|
||
The system must behave like a disciplined brain:
|
||
|
||
- Memory = decisions
|
||
- Plans = temporary thinking
|
||
- Docs = permanent knowledge
|
||
- TODOs = execution truth
|
||
- User = absolute authority |