infospace-bench/docs/replacement-acceptance-matrix.md

Replacement Acceptance Matrix

Date: 2026-05-14

Purpose

This matrix defines what evidence is required before infospace-bench can be considered a replacement for each in-scope legacy infospace behavior from markitect-project.

Matrix

Legacy behavior	Successor behavior	Evidence required	Workplan	Status
Create an infospace config	File-backed infospaces/<slug>/infospace.yaml and manifest	Lifecycle tests, CLI create/inspect docs	IB-WP-0002	baseline done
Load and inspect an infospace	Structured config/artifact model and JSON CLI	Tests for load, missing config, structured errors	IB-WP-0002	baseline done
Add/list artifacts	Manifest-backed artifact registration	Tests for add, duplicate rejection, inspect output	IB-WP-0002	baseline done
Parse entity Markdown	Entity parser built on markitect-tool document sections	Entity fixture tests, diagnostics for missing sections	IB-WP-0006, IB-WP-0007	done
Validate entity/relation shape	Contract/schema validation through markitect-tool	Valid/invalid fixture tests, diagnostic mapping	IB-WP-0006, IB-WP-0007	baseline done
List entities	Entity listing from parsed artifact model	CLI/API example and fixture tests	IB-WP-0007	done
Parse and list relations	Relation triplet model and endpoint checks	Relation fixture tests, graph edge tests	IB-WP-0007	done
Export semantic graph	Infospace graph model with Mermaid/DOT output	Graph output tests and pilot report	IB-WP-0007, IB-WP-0008	partial baseline
Run collection checks	Methodology-owned metrics in infospace-bench	Deterministic metric tests and fixture output	IB-WP-0008	partial baseline
Check viability	Threshold report from metrics	Viability tests and CLI/report output	IB-WP-0008	partial baseline
Write evaluation results	Evaluation files with structured metadata	Round-trip tests and pilot fixture	IB-WP-0008	done
Maintain metrics history	Snapshot history append/read/diff	History and history-diff tests	IB-WP-0008	done
Evaluate with LLM assistance	Provider-neutral assisted evaluation workflow	Dry-run plan, adapter contract, audited output	IB-WP-0009	boundary done
Process source chapters	Explicit infospace workflow stages	Deterministic runner tests, generated artifact provenance	IB-WP-0009	deterministic baseline done
Track stale outputs	Digest/provenance comparison	Tests after workflow provenance exists	IB-WP-0009	deferred
Persist durable assets	Optional engine-backed repository adapter	Dry-run sync tests and integration design	IB-WP-0010	planned
Run a legacy-derived pilot	Pruned infospace-with-history migration	Pilot corpus, migration report, parity comparison	IB-WP-0011	planned
Provide command migration path	Legacy command parity guide	Command table and examples	IB-WP-0012	planned

Replacement Gates

Gate A: Syntax Delegation

Passes when all Markdown parsing and validation in infospace-bench goes through the markitect-tool adapter.

Required workplans:

• IB-WP-0006

Gate B: Application Semantics

Passes when entities, relations, metrics, viability, evaluation history, and graphs work over real fixtures.

Required workplans:

• IB-WP-0007
• IB-WP-0008

Gate C: Workflow Parity

Passes when deterministic source-to-output workflows replace the old process command shape and assisted stages are explicit, dry-runnable, and auditable.

Required workplans:

• IB-WP-0009

Gate D: Engine Boundary

Passes when file-backed operation remains the default and kontextual-engine integration is available through an explicit adapter contract.

Required workplans:

• IB-WP-0010

Gate E: Legacy Pilot Proof

Passes when a pruned legacy pilot demonstrates the successor stack on migrated content.

Required workplans:

• IB-WP-0011
• IB-WP-0012

Non-Goals

• Full CLI name-for-name compatibility with legacy markitect infospace.
• Moving low-level Markdown parser code into infospace-bench.
• Recreating legacy prompt/provider code directly.
• Committing the full generated Wealth of Nations/VSM output tree as the first pilot.
• Building a database or workflow engine inside infospace-bench.

Readiness Statement

infospace-bench is a replacement candidate today, not a full replacement. It becomes replacement-ready only after the gates above produce committed tests, docs, pilots, and State Hub decisions.