generated from coulomb/repo-seed
53 lines
2.2 KiB
Markdown
53 lines
2.2 KiB
Markdown
---
|
|
id: IB-DR-0012
|
|
title: Replacement Readiness Decision
|
|
date: "2026-05-14"
|
|
decision: replacement-ready-for-new-in-scope-infospace-work
|
|
status: accepted
|
|
workplan: IB-WP-0012
|
|
---
|
|
|
|
# Replacement Readiness Decision
|
|
|
|
## Decision
|
|
|
|
`infospace-bench` is replacement-ready for new in-scope infospace work that was
|
|
previously attempted inside `markitect-project` / `markitect-main`.
|
|
|
|
Not a name-for-name CLI clone: replacement readiness means the successor stack
|
|
has an evidence-backed migration path, tests, pilots, and explicit ownership for
|
|
remaining gaps.
|
|
|
|
## Evidence
|
|
|
|
- Lifecycle, manifest, validation, entity/relation parsing, checks, viability,
|
|
history, workflows, engine sync planning, and CLI behavior are covered by the
|
|
test suite.
|
|
- `infospaces/bootstrap-pilot/` proves the repo-native lifecycle and workflow
|
|
baseline.
|
|
- `infospaces/wealth-vsm-legacy-slice/` proves a pruned legacy migration from
|
|
the old Wealth/VSM experiment.
|
|
- `docs/legacy-command-parity.md` gives users a command and API migration path.
|
|
- `docs/legacy-infospace-migration-guide.md` gives a repeatable migration
|
|
process.
|
|
|
|
## Residual Gaps And Owners
|
|
|
|
| Gap | Owner | Decision |
|
|
| --- | --- | --- |
|
|
| Rich source/chapter triage view | `infospace-bench` | Deferred; use manifest export and workflows meanwhile. |
|
|
| Classification workflow fixtures | `infospace-bench` | Deferred; implement as explicit workflows, not hidden provider calls. |
|
|
| Discipline composition command | `infospace-bench` | Deferred; config support exists, operational checks need a focused follow-up. |
|
|
| Stale mapping detection | `infospace-bench` + `kontextual-engine` | Deferred until provenance policy and durable asset comparison are settled. |
|
|
| Durable graph/retrieval/runtime | `kontextual-engine` | Delegated by design. |
|
|
| Markdown parser/schema engine | `markitect-tool` | Delegated by design. |
|
|
|
|
## Consequences
|
|
|
|
- New in-scope infospace work should start in `infospace-bench`.
|
|
- Low-level markdown behavior should be added to `markitect-tool`.
|
|
- Durable runtime concerns should be integrated through `kontextual-engine`
|
|
boundaries rather than built into this repo.
|
|
- Legacy bulk generated output should be migrated only when it has a current,
|
|
scoped use and can be covered by tests.
|