State-hub connect and initial workplans

SCOPE.md

@@ -0,0 +1,88 @@
+# SCOPE
+
+> This file helps humans and agents quickly understand what this repository is
+> for, when it is relevant, and where its boundaries are.
+
+---
+
+## One-liner
+
+Application-layer workspace and service for building, evaluating, inspecting,
+and evolving concrete structured knowledge spaces.
+
+---
+
+## Core Idea
+
+`infospace-bench` turns the infospace ideas that emerged in `markitect-main`
+into a focused successor project. It should host real infospaces, their
+configuration, evaluation runs, inspection outputs, workflow traces, and export
+experiments.
+
+The repo is intentionally above the lower layers:
+
+- `markitect-tool` owns markdown syntax and document transformation primitives.
+- `kontextual-engine` owns persistence, orchestration, and runtime system
+  concerns.
+- `infospace-bench` owns concrete applied knowledge spaces and their lifecycle.
+
+---
+
+## In Scope
+
+- Defining infospaces as first-class, inspectable project artifacts
+- Populating infospaces from real sources and domain-specific configurations
+- Evaluating entity quality, collection quality, structure, and viability
+- Inspecting relationships, provenance, metrics history, and workflow outputs
+- Running application-level generation, transformation, and analysis workflows
+- Capturing reusable patterns that may later move into lower-layer repos
+
+---
+
+## Out of Scope
+
+- Low-level markdown parsing, schema syntax primitives, or rendering engines
+- Generic persistence infrastructure or workflow orchestration platforms
+- General content management, publishing, or WYSIWYG editing
+- Reusable libraries that belong in `markitect-tool` or `kontextual-engine`
+- Silent coupling to a single LLM vendor or runtime
+
+---
+
+## Relevant When
+
+- A real corpus, book, project, or organization needs an explicit infospace
+- Knowledge artifacts need systematic evaluation and iteration history
+- Relationship structure and quality metrics need to be inspected over time
+- Agent-assisted knowledge development needs scoped project context
+- A MarkiTect infospace experiment needs to be migrated or reimplemented
+
+---
+
+## Not Relevant When
+
+- The work is only markdown syntax manipulation
+- The work is engine/runtime infrastructure
+- A finalized domain repository should own the production artifact
+- A few simple documents only need ordinary editing
+
+---
+
+## Current State
+
+- Status: newly bootstrapped successor repo
+- Source intent: `INTENT.md`, PRD, and FRS in `wiki/`
+- Upstream comparison target: `/home/worsch/markitect-main`
+- State Hub registration: `infospace-bench` under the `markitect` domain
+- First workplans: lifecycle scaffold, MarkiTect migration triage, evaluation
+  framework, and reference infospace pilot
+
+---
+
+## Getting Oriented
+
+- Start with: `INTENT.md`, `wiki/ProductRequirementsDocument.md`,
+  `wiki/FunctionalRequirementsSpecification.md`
+- Migration assessment: `docs/markitect-main-scope-assessment.md`
+- Workplans: `workplans/`
+- State Hub rules: `CLAUDE.md` and `.claude/rules/`