Parity Roadmap

codexclaw labels every capability honestly. A current feature is shipped and tested; planned means the design is decided but the runtime is not built; deferred means intentionally postponed. The docs never describe a planned feature as if it shipped.

Shipped (current)

Area	Status
FSM legal-transition table + attest gate	current
$cxc-orchestrate chat grammar + hook wiring	current
cxc orchestrate CLI over the same file state	current
status / reset / D affordances + phase footer	current
Stop-continuation loop with termination guards	current
$cxc-goalplan / $cxc-loop skill contracts	current
Interview scan-evidence ledger + I → P soft-gate	current
Subagent role config + MCP tools	current
opencodex detect-only bridge	current
Live spawn-wrapper consuming the role resolver	current
Interview PostToolUse answer capture + scan-evidence ledger	current
cxc subagents / cxc provider CLI	current
Render observation tracking hook	current
Skill-attach spawn hook + edit-lint hook	current
PostCompact state recovery hook	current
cxc map session-start affordance hook	current
SubagentStop evidence-verify hook	current

Planned

Area	Status	Notes
Developer docs SoT reconciliation	planned	Docs scaffold exists; content reconciliation in progress (L11).
npm / npx packaging	planned	Package is private; dist/ unpublished (L20).

Deferred / non-goals

Area	Status	Reason
codex-rs slash-command fork	deferred	Stay inside the plugin boundary.
cli-jaw server / employee model	deferred	codexclaw is a plugin, not a daemon.
jawcode runtime harness clone	deferred	Use Codex-native hooks and file state.
opencodex provider proxy / ocx ensure	deferred	Detect-only; provider work belongs to opencodex.
Filesystem-grep chat search	deferred	Native thread search is a runtime concern (chat-search retired).

Source of truth

This roadmap mirrors the maintainer ledgers under devlog/_plan/mvp_hard/. When a planned item ships and is tested, both the ledger and this page move it to current together.