Reference

This section documents shipped behavior precisely. Planned commands must remain marked as planned until code and tests exist.

For automation

Use this section when writing scripts, headless loops, or agent instructions. It favors exact command behavior over marketing language.

Feature matrixA full table of shipped capabilities and what each one does.ArchitectureCore, companions, files, argv channels, adapters, notifications, and worktree flows.RFC referenceAll RFCs 001-043 with status, implementation version, date, and notes.CLICommands, options, read/write behavior, JSON output, contracts, and wait loops.State modelThe lock block, holder, state transitions, TTLs, roster, and session fields.Turn schemaHandoff fields, Stage-4 contract vocabulary, relation metadata, and validation commands.Generated filesFiles created by init, protocol anchors, local state, and agent-facing instructions.Exit codesMachine-readable outcomes for success, refusal, waiting, invalid state, and automation branches.LimitationsWhat M8Shift deliberately does not enforce, host boundaries, and advisory metadata limits.

Reference discipline

If the CLI does not implement a behavior, the reference must not describe it as available. Link to the roadmap for staged or companion work.