relaycore CLAUDE.md

RelayCore Runtime Contract For Claude

Claude should use RelayCore as the durable memory backend for this repository.

RULES.md is the versioned editorial source for durable methodology and runtime rules. Sync it into RelayCore with relaycore sync-rules --rules-file RULES.md whenever the file changes.

Hard Rules

• Native Claude memory is not the project memory system.
• Do not assume built-in memory will be available in future sessions.
• Do not treat prior chat recall as an acceptable substitute for RelayCore.
• Any project decision that should survive the current session must be written to RelayCore.

Minimum Task Sequence

1. memory_auto_prepare
2. if unavailable, fall back to memory_begin_task and memory_context
3. short preflight describing the loaded relevant rules, decisions, lessons, and rejected paths
4. work
5. memory_add or memory_propose for durable outcomes
6. memory_commit_task

What Must Go To RelayCore

• accepted decisions
• rejected options and reasons
• reusable rules
• lessons learned
• task progress that another runtime may need
• artifact references that matter later

What Does Not Need Durable Storage

• ephemeral chain-of-thought
• transient drafting text
• one-off exploration that does not affect future work
• formatting chatter that has no project value

Retrieval Guidance

• Prefer memory_context with a bounded token budget.
• Prefer memory_auto_prepare for startup bootstrap and memory_context for bounded follow-up retrieval.
• Prefer compact summaries over dumping full historical transcripts.
• Read active decisions, rules, lessons, and relevant rejected knowledge before making new decisions.
• If RULES.md changes, sync it into RelayCore before considering the rule change complete.
• If the task involves planning, design, implementation, automation, or refactoring, preflight should explicitly verify whether the external-reference baseline rule applies.

Mission Control Boundary

• Treat Mission Control command publishing as a manual operator override path.
• Default to agent-driven command publication during normal runtime collaboration.
• Use the web UI command form only for fallback dispatch, debugging, or session seeding.