infospace-bench/workplans/IB-WP-0002-infospace-lifecycle-baseline.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-0002	workplan	Infospace Lifecycle Baseline	markitect	infospace-bench	done	markitect	markitect	2026-05-03	2026-05-14	ib-wp-0002-infospace-lifecycle-baseline	b5972baf-1fb4-4375-a8e3-6e6d6d6fb97c

IB-WP-0002 — Infospace Lifecycle Baseline

Goal

Implement the first file-backed baseline for creating, loading, updating, inspecting, and exporting infospaces.

FRS Coverage

• FR-001 to FR-004: infospace lifecycle
• FR-010 to FR-012: knowledge artifact population
• FR-020 to FR-021: structure and relationships
• FR-070 to FR-071: export and derived artifacts
• FR-090 to FR-091: structured errors and explicit failures

Tasks

T01 — Define repo-local infospace layout

id: IB-WP-0002-T01
status: done
priority: high
state_hub_task_id: "c8aaa52e-db89-42e3-9ebc-cb89be3f4d30"

• Define infospaces/<slug>/infospace.yaml
• Define artifact, output, evaluation, metrics, and report directories
• Document required and optional files

T02 — Define configuration model

id: IB-WP-0002-T02
status: done
priority: high
state_hub_task_id: "a96c3439-89e4-40d0-8731-fe6b39a8f451"

• Reimplement the useful markitect/infospace/config.py concepts
• Keep references to schemas, workflows, sources, disciplines, and viability thresholds explicit
• Avoid importing runtime orchestration concerns

T03 — Implement artifact model and loader

id: IB-WP-0002-T03
status: done
priority: high
state_hub_task_id: "36ad8a84-f4fd-48ca-bc6f-94827ac03481"

• Model artifact identity, source path, type, provenance, and relationships
• Support deterministic loading from file-backed projects
• Return structured errors for invalid layouts

T04 — Add lifecycle CLI

id: IB-WP-0002-T04
status: done
priority: medium
state_hub_task_id: "bfa70d92-c896-4133-8b93-0ece3e53c649"

• Provide minimal commands for create, inspect, add-artifact, and export
• Keep command outputs scriptable and traceable

Acceptance

• A new infospace can be created from a template
• An existing infospace can be loaded and inspected
• Artifacts can be added and listed
• Invalid configs produce structured, visible errors