Reestablishing intent based goals and workplans

workplans/IB-WP-0005-orthogonal-successor-architecture.md

@@ -0,0 +1,94 @@
+---
+id: IB-WP-0005
+type: workplan
+title: "Orthogonal Successor Architecture"
+domain: markitect
+repo: infospace-bench
+status: planned
+owner: markitect
+topic_slug: markitect
+created: "2026-05-14"
+updated: "2026-05-14"
+state_hub_workstream_slug: "ib-wp-0005-orthogonal-successor-architecture"
+state_hub_workstream_id: "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`
+
+```task
+id: IB-WP-0005-T01
+status: todo
+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
+
+```task
+id: IB-WP-0005-T02
+status: todo
+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
+
+```task
+id: IB-WP-0005-T03
+status: todo
+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
+
+```task
+id: IB-WP-0005-T04
+status: todo
+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

workplans/IB-WP-0006-markitect-tool-adapter.md

@@ -0,0 +1,83 @@
+---
+id: IB-WP-0006
+type: workplan
+title: "Markitect Tool Adapter And Markdown Artifact Validation"
+domain: markitect
+repo: infospace-bench
+status: planned
+owner: markitect
+topic_slug: markitect
+created: "2026-05-14"
+updated: "2026-05-14"
+state_hub_workstream_slug: "ib-wp-0006-markitect-tool-adapter"
+state_hub_workstream_id: "713415b0-0c14-4367-8217-26c729648aec"
+---
+
+# IB-WP-0006 — Markitect Tool Adapter And Markdown Artifact Validation
+
+## Goal
+
+Make `markitect-tool` the syntax-layer dependency of `infospace-bench` through
+a thin application adapter.
+
+## Tasks
+
+### T01 — Add dependency and adapter boundary
+
+```task
+id: IB-WP-0006-T01
+status: todo
+priority: high
+state_hub_task_id: "b438be61-6d2a-44f9-b235-2b415e9f4bca"
+```
+
+- Add a local development dependency on `markitect-tool`
+- Create `src/infospace_bench/markdown_adapter.py`
+- Keep the adapter narrow: parse, section extraction, schema/contract validation,
+  diagnostics
+
+### T02 — Parse Markdown artifacts through `markitect-tool`
+
+```task
+id: IB-WP-0006-T02
+status: todo
+priority: high
+state_hub_task_id: "d37d6be3-ea04-4279-a113-086ab4fb617d"
+```
+
+- Replace ad hoc assumptions about Markdown artifacts with parsed document
+  objects from `markitect-tool`
+- Preserve `KnowledgeArtifact` as the application-level manifest object
+- Add tests for heading extraction and frontmatter handling
+
+### T03 — Validate artifact contracts
+
+```task
+id: IB-WP-0006-T03
+status: todo
+priority: high
+state_hub_task_id: "74a78679-4ef2-4b6b-a80c-b40119d9f90e"
+```
+
+- Support configured schema/contract references from `infospace.yaml`
+- Return validation diagnostics in `InfospaceError`-compatible shapes
+- Add tests for valid and invalid artifact fixtures
+
+### T04 — CLI inspection integration
+
+```task
+id: IB-WP-0006-T04
+status: todo
+priority: medium
+state_hub_task_id: "99b4e2ca-d9be-40a5-8b10-0b0f3c18fb19"
+```
+
+- Extend `inspect` or add `validate` CLI behavior
+- Keep output JSON and scriptable
+- Document how `infospace-bench` delegates syntax behavior to `markitect-tool`
+
+## Acceptance
+
+- `infospace-bench` imports `markitect_tool` only through the adapter
+- Markdown parsing and validation are tested through real artifact fixtures
+- No low-level Markdown parser logic is introduced in `infospace-bench`

workplans/IB-WP-0007-entity-relation-model-migration.md

@@ -0,0 +1,82 @@
+---
+id: IB-WP-0007
+type: workplan
+title: "Entity And Relation Model Migration"
+domain: markitect
+repo: infospace-bench
+status: planned
+owner: markitect
+topic_slug: markitect
+created: "2026-05-14"
+updated: "2026-05-14"
+state_hub_workstream_slug: "ib-wp-0007-entity-relation-model-migration"
+state_hub_workstream_id: "3f6f17c9-bf50-4297-9bd5-cbe1e33efa76"
+---
+
+# IB-WP-0007 — Entity And Relation Model Migration
+
+## Goal
+
+Reintroduce the old infospace entity and relation semantics as
+application-level models on top of `markitect-tool` parsing.
+
+## Tasks
+
+### T01 — Define entity model
+
+```task
+id: IB-WP-0007-T01
+status: todo
+priority: high
+state_hub_task_id: "d6c401be-ada6-4684-9186-8ae35101bfa8"
+```
+
+- Reimplement the useful `EntityMeta` fields from `markitect-project`
+- Keep source provenance and artifact ID linkage explicit
+- Add fixtures from a small legacy-style entity document
+
+### T02 — Parse entities from artifacts
+
+```task
+id: IB-WP-0007-T02
+status: todo
+priority: high
+state_hub_task_id: "25e42321-33fe-4b84-8e95-c5308d91ad3b"
+```
+
+- Parse entity documents via `markitect-tool` sections
+- Extract title, definition, context, domain, source grounding, and section slugs
+- Return structured diagnostics for missing required sections
+
+### T03 — Define and parse relation model
+
+```task
+id: IB-WP-0007-T03
+status: todo
+priority: high
+state_hub_task_id: "845a8ea0-50d8-4dd3-8cc3-23717195ae6f"
+```
+
+- Reimplement relation triplet concepts: subject, predicate, object, relation
+  type, evidence, feedback role
+- Link relation endpoints to artifact/entity IDs
+- Add tests for relation parsing and endpoint validation
+
+### T04 — Manifest integration
+
+```task
+id: IB-WP-0007-T04
+status: todo
+priority: medium
+state_hub_task_id: "155028a2-4df7-4144-9193-74e95f6e51b1"
+```
+
+- Decide how entity and relation artifacts appear in `artifacts/index.yaml`
+- Support listing entities and relations from an infospace
+- Document the application-level model
+
+## Acceptance
+
+- Legacy-style entity and relation fixtures parse successfully
+- Missing required sections fail visibly
+- `infospace-bench` owns semantics while `markitect-tool` owns Markdown structure

workplans/IB-WP-0008-evaluation-history-metrics-parity.md

@@ -0,0 +1,81 @@
+---
+id: IB-WP-0008
+type: workplan
+title: "Evaluation History And Metrics Parity"
+domain: markitect
+repo: infospace-bench
+status: planned
+owner: markitect
+topic_slug: markitect
+created: "2026-05-14"
+updated: "2026-05-14"
+state_hub_workstream_slug: "ib-wp-0008-evaluation-history-metrics-parity"
+state_hub_workstream_id: "f00ba036-dc97-4370-a4a5-9ac2bce7ce6f"
+---
+
+# IB-WP-0008 — Evaluation History And Metrics Parity
+
+## Goal
+
+Bring the current evaluation dataclasses up to practical parity with the old
+infospace evaluation history and metrics behavior.
+
+## Tasks
+
+### T01 — Evaluation file I/O
+
+```task
+id: IB-WP-0008-T01
+status: todo
+priority: high
+state_hub_task_id: "95b48ad3-c4d1-442c-9bc0-7591d948d23e"
+```
+
+- Write and read per-entity/per-artifact evaluation files
+- Preserve human-readable Markdown body plus structured metadata
+- Add round-trip tests
+
+### T02 — Snapshot history
+
+```task
+id: IB-WP-0008-T02
+status: todo
+priority: high
+state_hub_task_id: "b4800ba8-5b86-44bb-bf47-e893bae36b22"
+```
+
+- Write, append, and read evaluation snapshot history
+- Support diffing named snapshots from disk
+- Add CLI support for history and history-diff behavior
+
+### T03 — Metrics merge and viability reports
+
+```task
+id: IB-WP-0008-T03
+status: todo
+priority: high
+state_hub_task_id: "7abcbd63-0147-4ae8-85f0-4af51882f476"
+```
+
+- Persist latest metrics under `output/metrics`
+- Merge collection metrics with evaluation-derived metrics
+- Emit structured viability reports
+
+### T04 — Legacy metric compatibility notes
+
+```task
+id: IB-WP-0008-T04
+status: todo
+priority: medium
+state_hub_task_id: "675d1d45-39d9-4ddd-9ab7-5d7de8a0f601"
+```
+
+- Compare old metric names and meanings to new baseline
+- Document changed semantics and accepted differences
+- Add fixtures that preserve critical old behavior
+
+## Acceptance
+
+- Evaluation and metrics history are inspectable, diffable, and reproducible
+- Viability reports can be generated from committed files
+- Old evaluation-history workflows have a clear replacement path

workplans/IB-WP-0009-applied-workflow-generation-pipeline.md

@@ -0,0 +1,84 @@
+---
+id: IB-WP-0009
+type: workplan
+title: "Applied Workflow And Generation Pipeline"
+domain: markitect
+repo: infospace-bench
+status: planned
+owner: markitect
+topic_slug: markitect
+created: "2026-05-14"
+updated: "2026-05-14"
+state_hub_workstream_slug: "ib-wp-0009-applied-workflow-generation-pipeline"
+state_hub_workstream_id: "e8c96f7b-f5c7-4fbb-b4dc-fcae7e9817f0"
+---
+
+# IB-WP-0009 — Applied Workflow And Generation Pipeline
+
+## Goal
+
+Rebuild the old source-processing pipeline as an application-level infospace
+workflow that delegates deterministic Markdown work to `markitect-tool` and
+keeps LLM/provider behavior behind explicit adapters.
+
+## Tasks
+
+### T01 — Workflow definition model
+
+```task
+id: IB-WP-0009-T01
+status: todo
+priority: high
+state_hub_task_id: "32c1dafc-c523-4ab7-9985-0820a65be514"
+```
+
+- Define infospace workflow declarations in `infospace.yaml`
+- Model inputs, outputs, templates, static macros, generated artifacts, and
+  expected evaluation steps
+- Avoid embedding runtime orchestration concerns
+
+### T02 — Deterministic workflow runner
+
+```task
+id: IB-WP-0009-T02
+status: todo
+priority: high
+state_hub_task_id: "2bb1f82b-f9a1-4d64-9de8-29a9f4eb78d0"
+```
+
+- Implement a file-backed runner for deterministic stages
+- Use `markitect-tool` transforms/references/templates where applicable
+- Emit traceable run records and output artifacts
+
+### T03 — Assisted generation boundary
+
+```task
+id: IB-WP-0009-T03
+status: todo
+priority: high
+state_hub_task_id: "2dd1ad70-8b5a-4afc-8f63-b1db3915ff31"
+```
+
+- Define the provider-neutral interface for LLM-assisted stages
+- Keep provider calls optional and auditable
+- Route future implementation through `llm-connect` or engine-managed adapters
+
+### T04 — CLI workflow commands
+
+```task
+id: IB-WP-0009-T04
+status: todo
+priority: medium
+state_hub_task_id: "63d34a33-63c6-45cb-8625-2e59ae0b6d57"
+```
+
+- Add `workflow inspect`, `workflow plan`, and deterministic `workflow run`
+  behavior
+- Keep output scriptable
+- Add reference fixtures
+
+## Acceptance
+
+- The old `process` concept is replaced by explicit infospace workflows
+- Deterministic runs are testable without external services
+- Assisted stages are designed without coupling to a model vendor

workplans/IB-WP-0010-kontextual-engine-integration-boundary.md

@@ -0,0 +1,84 @@
+---
+id: IB-WP-0010
+type: workplan
+title: "Kontextual Engine Integration Boundary"
+domain: markitect
+repo: infospace-bench
+status: planned
+owner: markitect
+topic_slug: markitect
+created: "2026-05-14"
+updated: "2026-05-14"
+state_hub_workstream_slug: "ib-wp-0010-kontextual-engine-integration-boundary"
+state_hub_workstream_id: "0f69d4dc-b301-436c-8ccb-858a00bd2847"
+---
+
+# IB-WP-0010 — Kontextual Engine Integration Boundary
+
+## Goal
+
+Define and implement the boundary where concrete infospaces can use
+`kontextual-engine` for durable knowledge operations without making
+`infospace-bench` an engine.
+
+## Tasks
+
+### T01 — Engine capability contract
+
+```task
+id: IB-WP-0010-T01
+status: todo
+priority: high
+state_hub_task_id: "f77c10cf-6ea2-44a6-af0b-f9c70860b999"
+```
+
+- Identify engine capabilities needed by infospaces: asset identity,
+  provenance, relationships, retrieval, workflow runs, permissions, audit
+- Define what stays file-backed versus engine-backed
+- Record assumptions against `kontextual-engine/INTENT.md`
+
+### T02 — Repository adapter design
+
+```task
+id: IB-WP-0010-T02
+status: todo
+priority: high
+state_hub_task_id: "bd20ddaa-c37d-4ec0-af4e-45198172e6f8"
+```
+
+- Design an adapter interface for asset persistence and retrieval
+- Provide a local file-backed implementation as the default
+- Leave room for a `kontextual-engine` client implementation
+
+### T03 — Sync and provenance model
+
+```task
+id: IB-WP-0010-T03
+status: todo
+priority: high
+state_hub_task_id: "12ffd95b-6db2-4881-bc3c-6bc4f9f3cc21"
+```
+
+- Define how infospace artifacts map to durable engine assets
+- Preserve source path, artifact ID, version/digest, derived outputs, and
+  workflow provenance
+- Add dry-run sync planning before mutation
+
+### T04 — Agent-safe operation notes
+
+```task
+id: IB-WP-0010-T04
+status: todo
+priority: medium
+state_hub_task_id: "fe1031d6-0b48-4fa1-9edd-3b1908a62003"
+```
+
+- Define which operations require review, dry run, or rollback
+- Align with engine governance and audit principles
+- Document the first safe integration scenario
+
+## Acceptance
+
+- `infospace-bench` has a clear engine adapter contract
+- The default remains file-backed and testable
+- Engine-backed persistence is designed as integration, not repo identity

workplans/IB-WP-0011-pruned-legacy-reference-pilot.md

@@ -0,0 +1,85 @@
+---
+id: IB-WP-0011
+type: workplan
+title: "Pruned Legacy Reference Pilot"
+domain: markitect
+repo: infospace-bench
+status: planned
+owner: markitect
+topic_slug: markitect
+created: "2026-05-14"
+updated: "2026-05-14"
+state_hub_workstream_slug: "ib-wp-0011-pruned-legacy-reference-pilot"
+state_hub_workstream_id: "5bcc4fe2-a1d3-4edf-9e6e-0b2844b5b499"
+---
+
+# IB-WP-0011 — Pruned Legacy Reference Pilot
+
+## Goal
+
+Migrate a small representative slice of
+`markitect-main/examples/infospace-with-history` into `infospace-bench` to prove
+successor behavior against real legacy content.
+
+## Tasks
+
+### T01 — Select representative slice
+
+```task
+id: IB-WP-0011-T01
+status: todo
+priority: high
+state_hub_task_id: "49d4865b-38b0-4994-a0f9-1cbdf718689c"
+```
+
+- Choose one or two source chapters or a compact equivalent fixture
+- Include at least one entity, one relation, one evaluation, and one metrics
+  snapshot
+- Avoid committing generated bulk
+
+### T02 — Migrate schemas/contracts and methodology
+
+```task
+id: IB-WP-0011-T02
+status: todo
+priority: high
+state_hub_task_id: "3bea0589-cd48-4a12-b2c5-e8996d383195"
+```
+
+- Convert relevant legacy schemas into `markitect-tool` contracts or supported
+  validation artifacts
+- Preserve metrics methodology where still applicable
+- Document changes from the old experiment
+
+### T03 — Run successor pipeline
+
+```task
+id: IB-WP-0011-T03
+status: todo
+priority: high
+state_hub_task_id: "fe012682-7af3-42a0-8d14-07685a663242"
+```
+
+- Load, validate, inspect, evaluate, and report on the migrated pilot
+- Compare outputs against expected legacy behavior
+- Capture gaps as follow-up tasks
+
+### T04 — Publish migration report
+
+```task
+id: IB-WP-0011-T04
+status: todo
+priority: medium
+state_hub_task_id: "5a6c885f-6acb-4d18-9aff-f710423e0198"
+```
+
+- Add a report under the pilot's `reports/`
+- Include what was replaced, what was delegated, and what remains missing
+- Use the report as evidence for replacement readiness
+
+## Acceptance
+
+- A legacy-derived pilot exists under `infospaces/`
+- It exercises parser, validation, entity/relation, evaluation, metrics, and
+  graph features
+- Its migration report is explicit about parity and gaps

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

@@ -0,0 +1,85 @@
+---
+id: IB-WP-0012
+type: workplan
+title: "Replacement Readiness And CLI Parity Gate"
+domain: markitect
+repo: infospace-bench
+status: planned
+owner: markitect
+topic_slug: markitect
+created: "2026-05-14"
+updated: "2026-05-14"
+state_hub_workstream_slug: "ib-wp-0012-replacement-readiness-cli-parity"
+state_hub_workstream_id: "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
+
+```task
+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
+
+```task
+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
+
+```task
+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
+
+```task
+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