infospace-bench/workplans/IB-WP-0012-replacement-readiness-cli-parity.md

id, type, title, domain, repo, status, owner, topic_slug, created, updated, state_hub_workstream_slug, state_hub_workstream_id

id	type	title	domain	repo	status	owner	topic_slug	created	updated	state_hub_workstream_slug	state_hub_workstream_id
IB-WP-0012	workplan	Replacement Readiness And CLI Parity Gate	markitect	infospace-bench	planned	markitect	markitect	2026-05-14	2026-05-14	ib-wp-0012-replacement-readiness-cli-parity	72b6a923-cad5-450b-b658-b35a00cecd4d

IB-WP-0012 — Replacement Readiness And CLI Parity Gate

Goal

Decide when infospace-bench can be treated as the replacement for the in-scope infospace features from markitect-project.

Tasks

T01 — Legacy command parity table

id: IB-WP-0012-T01
status: todo
priority: high
state_hub_task_id: "b48edb8e-b0af-4d46-9714-9830725d0773"

• Map legacy commands such as status, entities, chapters, evaluate, eval-summary, relations, classify, viability, check, history, history-diff, bind-discipline, process, stale-mappings, and graph
• Mark each as replaced, reframed, delegated, deferred, or retired
• Add replacement command/API examples

T02 — End-to-end acceptance suite

id: IB-WP-0012-T02
status: todo
priority: high
state_hub_task_id: "12eb0f88-4483-48ad-b156-79fa7c2171b7"

• Build tests around the bootstrap pilot and pruned legacy pilot
• Cover lifecycle, validation, entity/relation parsing, evaluation history, metrics, viability, workflow run, and export
• Keep all tests deterministic by default

T03 — Documentation and migration guide

id: IB-WP-0012-T03
status: todo
priority: high
state_hub_task_id: "cd4ee529-1ca0-4214-80fc-000af5c16b11"

• Write a guide for moving legacy MarkiTect infospaces into infospace-bench
• Explain which functionality moved to markitect-tool and kontextual-engine
• Include explicit non-goals

T04 — Replacement decision record

id: IB-WP-0012-T04
status: todo
priority: medium
state_hub_task_id: "ca88d1c5-b83f-47c9-90d0-58cedc7ca6f7"

• Record whether the old infospace feature set is replaced enough for new work
• List residual gaps and owning repos
• Update State Hub with the decision

Acceptance

• Replacement readiness is evidence-based, not aspirational
• Users have a command/API migration path
• Remaining gaps are explicitly owned by the correct repo