Files
infospace-bench/workplans/IB-WP-0004-reference-infospace-pilot.md
2026-05-14 11:32:25 +02:00

2.1 KiB

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-0004 workplan Reference Infospace Pilot markitect infospace-bench done markitect markitect 2026-05-03 2026-05-14 ib-wp-0004-reference-infospace-pilot 8940a180-646a-4b20-b41f-c56719adfb0e

IB-WP-0004 — Reference Infospace Pilot

Goal

Create the first maintained reference infospace in this repo. The large markitect-main/examples/infospace-with-history/ corpus remains the primary future migration candidate; this workplan starts with a small purpose-built bootstrap corpus so baseline behavior is easy to inspect.

Tasks

T01 — Decide pilot corpus scope

id: IB-WP-0004-T01
status: done
priority: high
state_hub_task_id: "5042482f-a14c-4ae5-8d1a-19039dc97010"
  • Choose between a small purpose-built corpus and a pruned Wealth of Nations/VSM corpus
  • Record the decision in docs/

T02 — Migrate configuration and methodology

id: IB-WP-0004-T02
status: done
priority: high
state_hub_task_id: "a0909309-775b-4220-94f5-6ca811d44caf"
  • Adapt infospace.yaml
  • Bring over metrics methodology and tutorial material where still valid
  • Remove generated output bulk unless needed as fixtures

T03 — Define source provenance and artifact policy

id: IB-WP-0004-T03
status: done
priority: medium
state_hub_task_id: "10c001a3-ce42-4f1b-8b9a-9965844a94cb"
  • Record source origin, license/public-domain status where applicable, and transformation history expectations
  • Decide which generated outputs are committed versus regenerated

T04 — Run first baseline evaluation

id: IB-WP-0004-T04
status: done
priority: medium
state_hub_task_id: "b5e43c2a-b29c-4cb6-b33c-b4db631d0079"
  • Execute lifecycle and evaluation baseline from IB-WP-0002 and IB-WP-0003
  • Save reports under the pilot infospace output structure

Acceptance

  • A concrete infospace exists in infospaces/
  • The pilot demonstrates lifecycle, evaluation, and inspection behavior
  • Migration from markitect-main is traceable and intentionally scoped