infospace-bench/workplans/IB-WP-0005-orthogonal-successor-architecture.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-0005	workplan	Orthogonal Successor Architecture	markitect	infospace-bench	done	markitect	markitect	2026-05-14	2026-05-14	ib-wp-0005-orthogonal-successor-architecture	ce26304b-aef2-4e01-926c-0635fc7a0f9b

IB-WP-0005 — Orthogonal Successor Architecture

Goal

Establish the explicit architecture and migration map that lets infospace-bench, markitect-tool, and kontextual-engine replace the useful parts of markitect-project without recreating its mixed responsibilities.

Context

The three INTENT.md files define an orthogonal stack:

• markitect-tool: Markdown syntax and transformation foundation
• kontextual-engine: persistent, governed, retrievable, operational knowledge engine
• infospace-bench: concrete applied infospaces and evaluation workflows

This workplan creates the durable successor map and keeps future work inside those boundaries.

Tasks

T01 — Feature inventory from legacy markitect-project

id: IB-WP-0005-T01
status: done
priority: high
state_hub_task_id: "10b456fa-fc07-43cc-8a83-7382cfab57a9"

• Inventory legacy infospace CLI commands, modules, examples, and outputs
• Classify each feature as migrate, delegate, reimplement, defer, or retire
• Record the target repo for each retained feature

T02 — Boundary and interface map

id: IB-WP-0005-T02
status: done
priority: high
state_hub_task_id: "f5a57259-97a1-4690-b448-c1d15668a1b9"

• Define what infospace-bench expects from markitect-tool
• Define what infospace-bench expects from kontextual-engine
• Define what remains file-backed inside infospace-bench

T03 — Replacement acceptance matrix

id: IB-WP-0005-T03
status: done
priority: high
state_hub_task_id: "0a4f35b4-377a-421d-8d6e-80dee467e1aa"

• Build a matrix mapping old behavior to new behavior
• Include tests, docs, CLI/API expectations, and pilot coverage for each row
• Mark clear non-goals so replacement does not become scope creep

T04 — State Hub alignment

id: IB-WP-0005-T04
status: done
priority: medium
state_hub_task_id: "5e9f9889-b50c-4353-986f-c5b473fa9fc5"

• Register this roadmap as State Hub workstreams
• Link follow-on workplans to this architecture record
• Keep progress events tied to replacement readiness

Acceptance

• docs/orthogonal-successor-roadmap.md is complete enough to guide future work
• Legacy infospace features have a target home or explicit retirement decision
• Follow-on workplans are created and sequenced