infospace-bench/workplans/IB-WP-0010-kontextual-engine-integration-boundary.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-0010	workplan	Kontextual Engine Integration Boundary	markitect	infospace-bench	planned	markitect	markitect	2026-05-14	2026-05-14	ib-wp-0010-kontextual-engine-integration-boundary	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

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

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

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

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