# 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