Implement scope intent reconciliation

SCOPE.md

@@ -7,8 +7,8 @@
 
 ## One-liner
 
-File-backed application workspace and CLI for building, evaluating, inspecting,
-generating, routing, budgeting, archiving, and iterating concrete structured
+File-backed application workspace and current CLI for creating, developing,
+evaluating, inspecting, exporting, archiving, and iterating concrete structured
 knowledge spaces.
 
 ---
@@ -18,23 +18,44 @@ knowledge spaces.
 `infospace-bench` turns the infospace ideas that emerged in `markitect-main`
 into a focused successor project. It hosts real infospaces, their manifests,
 profiles, workflow declarations, deterministic fixtures, generation runs,
-inspection outputs, budget records, archive records, and pilot reports.
+inspection outputs, budget records, archive records, exports, and pilot reports.
 
-The repo is intentionally above the lower layers:
+The strategic layer model remains:
 
-- `markitect-tool` owns markdown syntax, structured markdown validation, and
-  reusable Markitect contracts.
-- `kontextual-engine` owns durable persistence, orchestration, permissions,
-  retrieval, and runtime system concerns.
-- `artifact-store` owns durable content-addressed package identity, storage,
-  retention, and archive backend concerns.
-- `llm-connect` owns reusable provider routing primitives and quality-ledger
+- `markitect-tool` owns the syntax layer: markdown structure, structured
+  markdown validation, document transformations, and reusable Markitect
+  contracts.
+- `kontextual-engine` owns the system layer: durable persistence,
+  orchestration, permissions, retrieval, workflow runtime, and audit concerns.
+- `infospace-bench` owns the application layer: concrete applied knowledge
+  spaces, their lifecycle, evaluation methodology, and reference pilots.
+
+Current supporting integrations include:
+
+- `artifact-store` for durable content-addressed packages, archive identity,
+  storage, retention, and archive backend concerns.
+- `llm-connect` for reusable provider-routing primitives and quality-ledger
   policy mechanics.
-- `infospace-bench` owns concrete applied knowledge spaces and their lifecycle.
 
+These supporting integrations do not redefine the strategic layer ownership.
 The default operating mode is file-backed and inspectable. Optional integrations
 are explicit, reviewable adapters rather than hidden infrastructure drift.
 
+`infospace-bench` should also act as a reference environment for applied
+knowledge-engineering practice: concrete pilots, reviewable outputs, reusable
+patterns, and clear evidence of what should move into lower layers.
+
+---
+
+## Primary Actors
+
+- Knowledge engineers and developers building structured content systems
+- Researchers and practitioners organizing or analyzing domain knowledge
+- Automation systems (`atm`) executing scoped knowledge workflows
+- LLM agents (`agt`) helping generate, review, and refine infospaces
+- Human reviewers deciding when generated artifacts, metrics, and archives are
+  good enough to trust or preserve
+
 ---
 
 ## In Scope
@@ -44,12 +65,16 @@ are explicit, reviewable adapters rather than hidden infrastructure drift.
   domain-specific workflow templates
 - Running deterministic fixture workflows and explicit live provider workflows
   for generation, extraction, relation mapping, evaluation, and reports
+- Reviewing, pruning, revising, refining, and exporting knowledge artifacts as
+  infospaces evolve
 - Evaluating entity quality, collection quality, viability thresholds, metrics
   history, and plan-vs-actual generation behavior
 - Inspecting entities, relations, artifact graphs, provenance, workflow runs,
   provider metadata, budget records, and archive records
 - Capturing reusable applied patterns that may later move into lower-layer repos
 - Maintaining reference pilots that make abstract infospace concepts concrete
+- Documenting best-practice evidence for applied knowledge engineering without
+  turning this repo into the reusable infrastructure layer
 - Planning and recording one-way syncs from file-backed artifacts into an engine
   adapter while keeping the local manifest authoritative
 - Archiving reviewed infospace snapshots through `artifact-store` without making
@@ -105,6 +130,9 @@ are explicit, reviewable adapters rather than hidden infrastructure drift.
 - Status: implemented application-layer workspace with a Python CLI, test suite,
   reference docs, committed pilots, and deterministic fixtures
 - Package entry point: `infospace-bench` / `python3 -m infospace_bench`
+- Service posture: `INTENT.md` still treats "service" as a strategic maturity
+  target, but this repo does not currently ship a standalone server or API
+  service; the implemented surface is file-backed plus CLI
 - Current CLI surface: lifecycle, artifact add/export/validate, readiness
   status, entity and relation listing, metrics/checks, history diffs, viability,
   graph export, workflow inspect/plan/run, source generation, routing ledger
@@ -133,6 +161,8 @@ are explicit, reviewable adapters rather than hidden infrastructure drift.
 
 - `artifacts/index.yaml` is the authoritative manifest for an infospace in this
   repo.
+- Service or API behavior must be added explicitly; it should not be inferred
+  from the strategic service wording in `INTENT.md`.
 - Generated outputs, budget records, metrics, workflow runs, and reports are
   evidence for review; they do not silently become durable engine state.
 - Live LLM output is review material. Scaling from a one-chapter or bounded run