Generated new set of workplans

SCOPE.md

@@ -5,142 +5,116 @@
 
 ---
 
-## One-liner
+## One-Liner
 
-AI-first, headless knowledge engine that makes structured knowledge persistent,
-queryable, orchestratable, and operable across formats.
+Headless knowledge operations engine for turning heterogeneous information
+assets into persistent, contextual, governed, retrievable, transformable, and
+agent-operable knowledge.
 
 ---
 
 ## Core Idea
 
-`kontextual-engine` is the system-layer successor to the platform portions of
-`markitect-main`. It should preserve the useful ideas around infospaces,
-knowledge artifacts, relationships, retrieval, workflow execution, and agent
-context, while avoiding the old repo's mixed ownership of markdown primitives,
-UI, provider integrations, and project/domain content.
+`kontextual-engine` provides reusable backend capabilities for making fragmented
+information operational. It is meant to sit behind applications, automation,
+workflows, services, and AI agents that need durable knowledge assets rather
+than disconnected files, documents, records, notes, datasets, generated outputs,
+or content collections.
 
-The engine owns the runtime contract for persistent knowledge systems. Lower
-level syntax operations belong in `markitect-tool`; concrete domain workspaces
-belong in `infospace-bench`.
+The engine owns stable asset identity, source provenance, metadata,
+relationships, lifecycle state, permission-aware retrieval, traceable
+transformation, workflow state, auditability, exportability, and controlled
+agent operation.
+
+It should support CMS-like, DMS-like, ECM-like, file-service, knowledge-base,
+research-support, and AI-assisted workflow use cases without becoming a finished
+end-user application in any one category.
 
 ---
 
 ## In Scope
 
-- Persistent storage and lifecycle management for knowledge artifacts.
-- Collections/domains, metadata, and relationships between artifacts.
-- Multi-format ingestion interfaces and normalized internal representations.
-- Query, retrieval, indexing, and composition APIs.
-- Workflow orchestration for transformation, generation, and analysis.
-- Agent-facing context continuity and operation surfaces.
-- Integration adapters for lower-layer tools such as `markitect-tool`.
-- Structured errors, deterministic behavior where applicable, and auditable
-  state transitions.
+- Knowledge asset registry with stable asset IDs.
+- Persistent management of source, normalized, and derived asset forms.
+- Source references, provenance, ingestion history, and lifecycle state.
+- Multi-format ingestion and normalization for common knowledge assets.
+- Metadata, classification, custom schemas, contextual entities, and typed
+  relationships.
+- Search, filtering, querying, source-grounded snippets, relationship retrieval,
+  and permission-aware access.
+- Traceable transformations that produce derived artifacts with lineage.
+- Workflow and job orchestration for ingestion, enrichment, validation, review,
+  transformation, publication, archival, synchronization, and export.
+- Actors, permissions, policy checks, review gates, audit logs, and
+  fail-closed operation for ambiguous access.
+- Agent-safe operation through explicit, bounded, permissioned, auditable, and
+  reviewable APIs.
+- Service and programmatic APIs, adapter boundaries, extension hooks, events,
+  observability, export, and portability.
 
 ---
 
 ## Out of Scope
 
-- Low-level markdown parsing, schema primitives, document transforms, or CLI
-  tooling that belongs in `markitect-tool`.
-- Visual UI applications, rendering plugins, or WYSIWYG editing.
-- Domain-specific infospace content or benchmark corpora that belong in
-  `infospace-bench`.
-- Direct ownership of LLM provider adapters; use `llm-connect` or equivalent.
-- Finance, issue tracking, profile management, release tooling, and other
-  legacy `markitect-main` utilities unrelated to the engine contract.
-- A CLI-first product posture; any CLI should remain an administrative or
-  development convenience over service/programmatic APIs.
+- A finished end-user ECM, DMS, CMS, intranet, workspace, or file-sharing
+  product by itself.
+- A visual website builder, WYSIWYG authoring suite, or document editor.
+- A file sync client or simple file browser.
+- A markdown-specific tooling layer; low-level markdown operations belong in
+  `markitect-tool` or equivalent adapters.
+- A pure vector database, standalone search appliance, or generic chatbot over
+  documents.
+- A domain-specific knowledge base with hard-coded legal, support, research, or
+  marketing semantics.
+- Direct ownership of every enterprise connector, AI provider, embedding model,
+  search backend, workflow engine, or deployment platform.
+- Direct ownership of LLM provider adapters; use `llm-connect` or equivalent
+  provider-neutral integrations.
 
 ---
 
 ## Relevant When
 
-- A project needs durable knowledge artifacts instead of one-off file parsing.
-- Agents need stable context and retrievable state across sessions.
-- Workflows must ingest, normalize, transform, compose, and query knowledge.
-- Multiple formats and external tooling need a common runtime layer.
-- A higher-level application needs a headless knowledge service.
+- A project needs stable knowledge asset identity rather than path-only file
+  references.
+- Heterogeneous documents, files, markdown, PDFs, datasets, notes, records, or
+  generated outputs need a common operational layer.
+- Search, retrieval, transformations, workflows, and AI operations must preserve
+  provenance, permissions, and auditability.
+- Derived summaries, reports, extracts, classifications, or generated artifacts
+  must remain traceable to source assets and operation context.
+- AI agents need bounded, permissioned, source-grounded context and explicit
+  operation surfaces.
+- A higher-level product needs a headless knowledge engine rather than another
+  monolithic content application.
 
 ---
 
 ## Not Relevant When
 
-- The task is only markdown syntax manipulation or schema validation.
-- The primary need is an end-user visual application.
-- The work is domain-specific corpus curation without runtime needs.
-- Provider-specific LLM client behavior is the main concern.
+- The task is only low-level markdown syntax manipulation or schema validation.
+- The primary need is a polished end-user UI.
+- The desired product is a file synchronization client or office editor.
+- A project only needs a vector index without durable identity, provenance,
+  permissions, workflows, audit, or derived artifact lineage.
+- The work is domain-specific corpus curation without reusable engine needs.
 
 ---
 
 ## Current State
 
-- Status: scoping / foundation.
-- Implementation: documentation and workplans only.
-- Stability: evolving.
-- Usage: successor planning for the in-scope system-layer parts of
-  `markitect-main`.
+- Status: foundation complete; roadmap re-scoped around the V0.2 knowledge
+  operations vision.
+- Implementation: first runtime slice exists for artifacts, collections,
+  relationships, in-memory storage, ingestion adapters, query, workflow run
+  manifests, and agent-facing context packages.
+- Next work: execute `KONT-WP-0004` through `KONT-WP-0010`, starting with the
+  architecture rebase and then building durable governed asset operations.
 
 ---
 
-## How It Fits
+## Keywords
 
-- Upstream dependencies: `markitect-tool` for syntax-layer primitives,
-  `llm-connect` for provider-neutral LLM access, storage backends to be chosen.
-- Downstream consumers: `infospace-bench`, future knowledge services, agents,
-  and automation systems.
-- Often used with: State Hub for planning/coordination, markitect ecosystem
-  repos for adjacent responsibilities.
-
----
-
-## Terminology
-
-- Preferred terms: knowledge artifact, collection, relationship, ingestion,
-  normalization, workflow, context, operation.
-- Also known as: Kontextual Engine, knowledge runtime, headless knowledge
-  engine.
-- Potentially confusing terms: "infospace" is a conceptual collection pattern
-  inherited from `markitect-main`, not necessarily a project directory or a
-  UI-facing workspace.
-
----
-
-## Related / Overlapping
-
-- `markitect-main` — legacy mixed platform; source for candidate behavior and
-  tests, not the target architecture.
-- `markitect-tool` — syntax layer for markdown and structured document
-  primitives.
-- `infospace-bench` — application/project layer for concrete knowledge spaces.
-- `llm-connect` — LLM provider abstraction that this repo may call but should
-  not replace.
-- `the-custodian/state-hub` — coordination and repo/workplan index.
-
----
-
-## Getting Oriented
-
-- Start with: `INTENT.md`, `wiki/ProductRequirementsDocument.md`,
-  `wiki/FunctionalRequirementsSpecification.md`.
-- Key files / directories: `docs/`, `workplans/`, `SCOPE.md`, `CLAUDE.md`.
-- Entry points: none yet; implementation starts from the workplans.
-
----
-
-## Provided Capabilities
-
-```capability
-type: service
-title: Persistent knowledge runtime
-description: Provides the planned system layer for storing, querying, transforming, and orchestrating structured knowledge artifacts across formats.
-keywords: [knowledge, runtime, persistence, orchestration, retrieval]
-```
-
-```capability
-type: automation
-title: Agent-operable knowledge workflows
-description: Provides planned APIs and workflow surfaces that let agents access context, trigger transformations, and operate over durable knowledge state.
-keywords: [agent, workflow, context, automation, knowledge]
-```
+knowledge, content, assets, provenance, retrieval, governance, audit,
+workflow, transformation, agent-safe, API-first, metadata, relationships,
+ingestion, export, portability