infospace-bench/workplans/IB-WP-0021-scope-intent-reconciliation.md

id, type, title, domain, repo, status, owner, topic_slug, created, updated, related_workplans, state_hub_workstream_id

id	type	title	domain	repo	status	owner	topic_slug	created	updated	related_workplans	state_hub_workstream_id
IB-WP-0021	workplan	Scope and Intent Reconciliation	markitect	infospace-bench	finished	markitect	markitect	2026-06-04	2026-06-05	IB-WP-0005 IB-WP-0014 IB-WP-0015 IB-WP-0018 IB-WP-0020	62ad79c9-43f6-43ef-847c-ef88e9ec9e3c

IB-WP-0021 - Scope and Intent Reconciliation

Goal

Reconcile SCOPE.md with INTENT.md after the repo has matured from a successor scaffold into an implemented file-backed application workspace and CLI. The intent document remains the strategic charter; the scope document should make that charter operational without narrowing or expanding it by accident.

Context

The 2026-06-04 gap analysis found that SCOPE.md is broadly aligned with INTENT.md, but five strategic promises need clearer treatment:

• INTENT.md says "workspace and service"; SCOPE.md currently emphasizes workspace and CLI.
• INTENT.md names intended users and agents; SCOPE.md lacks a matching actor-facing section.
• INTENT.md emphasizes iterative development, refinement, and export; SCOPE.md mostly makes those implicit.
• SCOPE.md names artifact-store and llm-connect, which are real current integrations, but should not appear to redefine the three-layer strategic model from INTENT.md.
• INTENT.md names best-practice reference-environment maturity; SCOPE.md mentions pilots and reusable patterns but does not surface that target directly.

Non-Goals

• Changing the strategic direction in INTENT.md.
• Implementing new runtime, service, storage, routing, or engine features.
• Reopening completed pilot implementation work.
• Adding current workplan status summaries to SCOPE.md.

Tasks

T01 - Decide service wording

id: IB-WP-0021-T01
status: done
priority: high
state_hub_task_id: "860c2f5f-13e3-4f67-b4dd-6285c066a03e"

Decide whether "service" in INTENT.md is still a future maturity target or whether the repository should now be described strictly as a workspace and CLI. Update SCOPE.md to make that relationship explicit without overstating implemented service behavior.

T02 - Add primary actor framing

id: IB-WP-0021-T02
status: done
priority: medium
state_hub_task_id: "a17391f9-2d1d-47f4-af8b-2803a96f376d"

Add a concise Primary Actors or equivalent section to SCOPE.md that maps the intended users from INTENT.md into operational scope: knowledge engineers, developers, researchers, practitioners, automation systems, and LLM agents.

T03 - Surface refinement and export lifecycle

id: IB-WP-0021-T03
status: done
priority: medium
state_hub_task_id: "2baf36c7-47b2-42a7-8f8e-ccbd82ae5d38"

Make iterative review, pruning, revision, refinement, and export explicit in SCOPE.md, while preserving the boundary that durable archive packages and production domain ownership belong outside normal in-flight workspace state.

T04 - Clarify strategic layers versus supporting integrations

id: IB-WP-0021-T04
status: done
priority: high
state_hub_task_id: "7859d62d-4a50-4146-a50b-e4ae7e65d6c0"

Revise the core-idea or boundary language so markitect-tool, kontextual-engine, and infospace-bench remain the strategic syntax/system/ application layers from INTENT.md, while artifact-store and llm-connect are presented as supporting integrations with their own ownership boundaries.

T05 - Add reference-environment maturity target

id: IB-WP-0021-T05
status: done
priority: medium
state_hub_task_id: "55b7050f-0e3e-4649-ad23-3bc6de6bbc35"

Add language that ties SCOPE.md back to the maturity target in INTENT.md: infospace-bench should be a reference environment for applied knowledge engineering practice, not just a collection of pilots.

T06 - Verify documentation consistency

id: IB-WP-0021-T06
status: done
priority: low
state_hub_task_id: "fa7a4e5c-4202-4940-aee6-acdf268a752d"

After the edits, review SCOPE.md, INTENT.md, and README.md together for terminology drift. Run a lightweight markdown/diff check and record whether any follow-up changes belong in INTENT.md rather than SCOPE.md.

Implementation Evidence

Completed on 2026-06-05.

• T01: SCOPE.md now states that the current implementation is a file-backed workspace and CLI, while INTENT.md's service language remains a strategic maturity target rather than a deployed server/API today.
• T02: SCOPE.md now includes a Primary Actors section covering knowledge engineers, developers, researchers, practitioners, automation systems, LLM agents, and human reviewers.
• T03: SCOPE.md now explicitly includes review, pruning, revision, refinement, and export in the infospace lifecycle.
• T04: SCOPE.md now separates the strategic layer model (markitect-tool, kontextual-engine, infospace-bench) from supporting integrations (artifact-store, llm-connect).
• T05: SCOPE.md now names the repo's role as a reference environment for applied knowledge-engineering practice.
• T06: SCOPE.md, INTENT.md, and README.md were reviewed together. No INTENT.md change is required for this pass; README.md can keep the strategic "workspace and service" phrasing because SCOPE.md now clarifies the current implementation posture.

Acceptance

• SCOPE.md no longer contains dated workplan-status summaries.
• Each gap from the 2026-06-04 analysis is either resolved in SCOPE.md or explicitly deferred with a reason.
• SCOPE.md preserves the strategic authority of INTENT.md while reflecting the repo's implemented state.
• Supporting integrations are described as integrations, not as new strategic layers.
• No implementation work outside documentation is introduced by this workplan.