Intent and specification files

INTENT.md

@@ -0,0 +1,110 @@
+# INTENT
+
+## Purpose
+
+This repository exists to provide a **workspace and service for creating, developing, evaluating, and inspecting structured knowledge spaces (“infospaces”)**.
+
+It enables the practical exploration and application of structured knowledge systems in concrete domains such as books, projects, research corpora, and organizational knowledge.
+
+---
+
+## Primary Utility
+
+The repository provides an environment that:
+
+* Defines and manages **explicit infospaces as first-class artifacts**
+* Supports iterative development of structured knowledge collections
+* Enables evaluation, inspection, and refinement of knowledge quality and structure
+* Applies transformation, generation, and analysis workflows to real-world content
+* Serves as a testbed for methods, patterns, and tooling in knowledge engineering
+
+It turns abstract knowledge tooling into **concrete, inspectable knowledge systems**.
+
+---
+
+## Intended Users
+
+* Knowledge engineers and developers working on structured content systems
+* Researchers and practitioners organizing and analyzing domain knowledge
+* Automation systems (`atm`) executing knowledge workflows within a defined scope
+* LLM agents (`agt`) contributing to the generation and refinement of infospaces
+
+---
+
+## Strategic Role in the System
+
+This repository is part of a layered knowledge system with clearly separated responsibilities:
+
+- markitect-tool     → makes markdown structured and manipulable
+- kontextual-engine  → makes knowledge persistent and operable
+- **infospace-bench**    → makes knowledge concrete and meaningful
+
+These layers correspond to a deliberate separation of concerns:
+
+* **Syntax layer** — structuring and transforming semi-structured data (markdown)
+* **System layer** — operating, persisting, and orchestrating knowledge
+* **Application layer** — applying knowledge systems to real-world contexts
+
+This repository occupies the **application layer** and should maintain **clear boundaries** to the others.
+
+This repository acts as the **project and experimentation layer**:
+
+* It sits above the knowledge engine (`kontextual-engine`)
+* It uses tooling primitives (e.g. `markitect-tool`) via the engine or directly
+* It defines **real-world instances of structured knowledge systems**
+* It provides a space to **validate approaches, workflows, and abstractions**
+
+It is where knowledge systems are **applied, tested, and evolved in context**.
+
+---
+
+## Strategic Boundaries
+
+This repository is **not** intended to:
+
+* Provide low-level tooling for markdown or structured content manipulation
+* Act as a general-purpose knowledge engine or runtime platform
+* Define reusable infrastructure primitives or core system contracts
+* Replace domain-specific repositories for finalized artifacts
+
+Its responsibility is limited to **working with concrete infospaces and their lifecycle**.
+
+---
+
+## Design Principles
+
+* **Concrete over abstract**
+  Focus on real, inspectable knowledge artifacts rather than generic capabilities
+
+* **Exploration and iteration**
+  Infospaces evolve through experimentation, evaluation, and refinement
+
+* **Separation from infrastructure**
+  Tooling and engine concerns remain outside this repository
+
+* **Traceability and inspectability**
+  All knowledge transformations and evaluations should be observable
+
+* **Reusability of patterns**
+  Successful approaches can be extracted into lower layers or reused across infospaces
+
+---
+
+## Maturity Target
+
+A mature version of this repository should:
+
+* Support the **full lifecycle of infospaces** from creation to evaluation and export
+* Provide **clear visibility into structure, quality, and relationships** within knowledge spaces
+* Enable efficient **AI-assisted development and refinement of knowledge artifacts**
+* Serve as a **reference environment for best practices in knowledge engineering**
+* Produce reusable insights and patterns that inform lower-layer systems
+
+---
+
+## Stability Note
+
+Changes to this file represent a **deliberate shift in how infospaces are defined, developed, or used** within the system.
+
+Such changes should be made with explicit intent, as they influence the direction of knowledge engineering practices across the ecosystem.
+