State-hub connect and initial workplans

This commit is contained in:
2026-05-03 20:43:50 +02:00
parent b40ac33d11
commit 50d6866c64
10 changed files with 675 additions and 5 deletions

View File

@@ -0,0 +1,86 @@
---
id: KONT-WP-0001
type: workplan
title: "Repository Foundation And State Hub Integration"
domain: markitect
repo: kontextual-engine
status: active
owner: codex
topic_slug: markitect
created: "2026-05-03"
updated: "2026-05-03"
state_hub_workstream_id: "52ff9c49-edcf-4150-8895-c6b31f5aa075"
---
# KONT-WP-0001: Repository Foundation And State Hub Integration
## Purpose
Establish `kontextual-engine` as a properly scoped, State Hub connected
successor repo before implementation begins.
## F1.1 - Register repo with State Hub
```task
id: KONT-WP-0001-T001
status: done
priority: high
state_hub_task_id: "f11fbf85-6841-464d-b076-73811a161a8e"
```
Create or verify the State Hub repo record for `kontextual-engine` in the
`markitect` domain with the local host path `/home/worsch/kontextual-engine`.
## F1.2 - Add State Hub repo integration files
```task
id: KONT-WP-0001-T002
status: done
priority: high
state_hub_task_id: "7a56ea42-1690-4bd6-9640-29c3863717a6"
```
Add `CLAUDE.md`, `.custodian-brief.md`, `SCOPE.md`, `tpsc.yaml`, and
`docs/state-hub-integration.md` so future sessions can orient consistently.
## F1.3 - Establish authoritative workplan set
```task
id: KONT-WP-0001-T003
status: done
priority: high
state_hub_task_id: "950f43a4-e815-42b5-a167-eb48f0706d4d"
```
Create initial workplans for foundation, legacy scope extraction, and first
implementation slices using the ADR-001 file-backed convention.
## F1.4 - Run State Hub consistency sync
```task
id: KONT-WP-0001-T004
status: done
priority: high
state_hub_task_id: "6fefec5f-eff8-402a-ad87-bf4821468a3d"
```
From `/home/worsch/the-custodian/state-hub`, run:
```bash
make fix-consistency REPO=kontextual-engine
```
Verify the repo has no consistency failures after State Hub indexes the
workplan files.
## F1.5 - Decide initial implementation stack
```task
id: KONT-WP-0001-T005
status: todo
priority: medium
state_hub_task_id: "616e0476-7b65-4079-b545-13e0fc9436f7"
```
Choose the first implementation stack, dependency manager, test command, and
service framework. Record the decision before adding application code.

View File

@@ -0,0 +1,97 @@
---
id: KONT-WP-0002
type: workplan
title: "markitect-main System-Layer Extraction"
domain: markitect
repo: kontextual-engine
status: active
owner: codex
topic_slug: markitect
created: "2026-05-03"
updated: "2026-05-03"
state_hub_workstream_id: "e46d0962-7451-4b6c-b39f-461e35ba6a76"
---
# KONT-WP-0002: markitect-main System-Layer Extraction
## Purpose
Compare `markitect-main` against the `kontextual-engine` PRD/FRS and extract
only the behavior, tests, and concepts that belong in the headless knowledge
runtime layer.
## S2.1 - Complete first-pass scope assessment
```task
id: KONT-WP-0002-T001
status: done
priority: high
state_hub_task_id: "1d7609a6-605d-425b-ab51-9a77a82ff73d"
```
Document the first-pass migration/reimplementation assessment in
`docs/markitect-main-scope-assessment.md`.
## S2.2 - Inventory persistence and repository code
```task
id: KONT-WP-0002-T002
status: todo
priority: high
state_hub_task_id: "86a1bf90-db72-44a0-a5ad-6374e6de8454"
```
Review legacy filesystem/SQLite repositories, workspace database docs, prompt
run migrations, and related tests. Classify each item as migrate test,
reimplement concept, defer, or out of scope.
## S2.3 - Inventory infospace models and relationships
```task
id: KONT-WP-0002-T003
status: todo
priority: high
state_hub_task_id: "8b88b3fa-a905-44aa-a25f-993cc9d50f2c"
```
Review `markitect/infospace/` models, relationship parsing, graph export, and
example fixtures. Extract generic artifact, collection, relationship, and
evaluation concepts without importing project-layer assumptions.
## S2.4 - Inventory orchestration and run-manifest material
```task
id: KONT-WP-0002-T004
status: todo
priority: high
state_hub_task_id: "1f15f603-4f86-41f8-8a24-95c0e9c825f7"
```
Review prompt dependency resolution roadmap, run manifests, quality tables,
batch processor behavior, and workflow-related migrations. Produce a candidate
workflow model for engine implementation.
## S2.5 - Inventory API and query experiments
```task
id: KONT-WP-0002-T005
status: todo
priority: medium
state_hub_task_id: "0a1e5a4b-f64d-4228-8f0f-e174475253da"
```
Review query paradigms, GraphQL docs, search/indexing experiments, and error
handling. Decide which API/query ideas deserve new tests or design notes.
## S2.6 - Produce migration backlog
```task
id: KONT-WP-0002-T006
status: todo
priority: high
state_hub_task_id: "54a7e7a7-bf26-4f71-a8a5-9da48f5018c2"
```
Create a structured backlog of candidate tests, fixtures, modules, and
behaviors for `KONT-WP-0003`, grouped by FRS section and migration strategy.

View File

@@ -0,0 +1,120 @@
---
id: KONT-WP-0003
type: workplan
title: "Headless Knowledge Engine Implementation"
domain: markitect
repo: kontextual-engine
status: active
owner: codex
topic_slug: markitect
created: "2026-05-03"
updated: "2026-05-03"
state_hub_workstream_id: "0fd08391-e8c9-4f1b-ace4-06439f958e88"
---
# KONT-WP-0003: Headless Knowledge Engine Implementation
## Purpose
Build the first usable `kontextual-engine` runtime around the PRD/FRS contract:
persistent knowledge artifacts, collections, relationships, ingestion,
retrieval, workflows, and agent-operable context.
## I3.1 - Scaffold package and test harness
```task
id: KONT-WP-0003-T001
status: todo
priority: high
state_hub_task_id: "3d3400a5-63ee-4c64-8bfb-fd3caa1ce787"
```
Create the initial Python package, dependency metadata, test harness, and CI
commands after the stack decision in `KONT-WP-0001`.
## I3.2 - Implement artifact and collection model
```task
id: KONT-WP-0003-T002
status: todo
priority: high
state_hub_task_id: "638ce4d0-b96b-4d8f-8bd9-4c77acad0a59"
```
Implement core models for artifacts, metadata, collections, domains, and
relationships. Cover FR-001 through FR-011 with focused unit tests.
## I3.3 - Implement storage abstraction
```task
id: KONT-WP-0003-T003
status: todo
priority: high
state_hub_task_id: "41c84f25-96b0-40eb-b2b4-834938cf9bb9"
```
Define repository interfaces and the first backend. Start with the simplest
backend that can support deterministic tests, then document the path to SQLite
or service-backed persistence.
## I3.4 - Implement ingestion and normalization interfaces
```task
id: KONT-WP-0003-T004
status: todo
priority: high
state_hub_task_id: "0be5fff9-f4a2-4aee-86b9-b84feef477f7"
```
Define format-agnostic ingestion contracts. Add a markdown adapter boundary
that can later call `markitect-tool`, without embedding markdown primitives in
this repo.
## I3.5 - Implement query and retrieval API
```task
id: KONT-WP-0003-T005
status: todo
priority: high
state_hub_task_id: "c8841fab-6dd1-47e1-a794-798bef1663e7"
```
Provide programmatic query over identifiers, metadata, content references, and
relationships. Cover FR-030 and FR-031 with tests.
## I3.6 - Implement workflow run model
```task
id: KONT-WP-0003-T006
status: todo
priority: high
state_hub_task_id: "0d62f47c-339a-4d86-9ab0-737bd4ab553c"
```
Represent workflow runs, steps, dependencies, inputs, outputs, structured
errors, and derived artifacts. Cover FR-040 through FR-052.
## I3.7 - Implement agent context surface
```task
id: KONT-WP-0003-T007
status: todo
priority: medium
state_hub_task_id: "96689817-e8e9-42e4-9af3-f03021e3ae4e"
```
Provide a provider-neutral context assembly API so agents can inspect
knowledge state, trigger operations, and receive traceable results.
## I3.8 - Define service API boundary
```task
id: KONT-WP-0003-T008
status: todo
priority: medium
state_hub_task_id: "0f4748f9-934a-438c-ac2d-e9796ad98818"
```
Decide and document the first HTTP/RPC service boundary after the programmatic
API is stable enough to avoid framework-driven architecture.