State-hub connect and initial workplans

.claude/rules/architecture.md

@@ -0,0 +1,20 @@
+# Architecture Notes
+
+The intended architecture is layered:
+
+```text
+markitect-tool     -> syntax layer
+kontextual-engine  -> system/runtime layer
+infospace-bench    -> application layer
+```
+
+The first implementation should establish repo shape before service shape:
+
+- `infospaces/` for concrete infospace projects
+- `schemas/` or dependency references for artifact schemas
+- `workflows/` for application-level workflow definitions
+- `reports/` for evaluation and inspection outputs
+- `docs/` for migration and design records
+
+Use direct dependencies on lower-layer projects only where they clarify the
+boundary. Avoid copying infrastructure wholesale from `markitect-main`.

.claude/rules/repo-boundary.md

@@ -0,0 +1,19 @@
+# Repo Boundary
+
+`infospace-bench` owns application-level infospace usage. It must not absorb
+lower-layer responsibilities.
+
+Belongs here:
+
+- Infospace definitions and examples
+- Application workflow definitions
+- Evaluation and inspection reports
+- Migration notes from `markitect-main`
+- Workplans for applied infospace capabilities
+
+Belongs elsewhere:
+
+- Markdown parsing and structural syntax primitives: `markitect-tool`
+- Runtime persistence and orchestration: `kontextual-engine`
+- LLM provider abstraction: `llm-connect` or equivalent
+- Final production domain artifacts: the relevant domain repo

.claude/rules/repo-identity.md

@@ -0,0 +1,11 @@
+# Repo Identity
+
+- Project: `infospace-bench`
+- Domain: `markitect`
+- State Hub repo slug: `infospace-bench`
+- State Hub topic ID: `5571d954-0d30-4950-980d-7bcaaad8e3e2`
+- Purpose: application-layer workspace and service for concrete infospaces.
+
+This repo is a scoped successor to the application-level infospace work in
+`markitect-main`. It should preserve and extend the parts that help create,
+evaluate, inspect, and evolve real knowledge spaces.

.claude/rules/session-protocol.md

@@ -0,0 +1,8 @@
+# Session Protocol
+
+1. Read `SCOPE.md`, `INTENT.md`, and the active workplan before making changes.
+2. Check `git status --short` and preserve user changes.
+3. Use State Hub as the coordination record when available.
+4. Keep repo artifacts traceable: workplans, docs, configs, metrics, and outputs
+   should explain what changed and why.
+5. Prefer narrow, inspectable changes over broad platform work.

.claude/rules/stack-and-commands.md

@@ -0,0 +1,17 @@
+# Stack And Commands
+
+The implementation stack is not established yet. Until it is, prefer
+documentation and small scaffold changes over choosing frameworks prematurely.
+
+Useful commands:
+
+```bash
+git status --short
+rg --files
+```
+
+State Hub registration was completed with:
+
+```bash
+/home/worsch/the-custodian/state-hub/.venv/bin/custodian register-project --domain markitect --path /home/worsch/infospace-bench
+```

.claude/rules/workplan-convention.md

@@ -0,0 +1,9 @@
+# Workplan Convention
+
+- Workplans live in `workplans/`.
+- Prefix new workplans with `IB-WP-`.
+- Use YAML frontmatter with `id`, `type`, `title`, `domain`, `repo`, `status`,
+  `owner`, `topic_slug`, `created`, and `updated`.
+- Include task blocks with stable IDs, status, priority, and optional State Hub
+  task IDs.
+- Keep workplans tied to this repo's PRD/FRS requirements and State Hub context.