initial priming commit

canon/projects/markitect/concepts_seed_v0.1.md

@@ -0,0 +1,26 @@
+---
+id: CUST-CPT-MARK-2026-000001
+type: concept
+title: "Markitect — Seed Concepts v0.1"
+status: active
+owners: ["Bernd", "Custodian"]
+created: "2026-02-24"
+updated: "2026-02-24"
+scope:
+  domains: ["Markitect"]
+  sensitivity: internal
+tags: ["concepts", "knowledge", "schema"]
+---
+
+# Markitect — Seed Concepts v0.1
+
+1. **Artifact** — a unit of structured knowledge with metadata and lifecycle.
+2. **Provenance** — where an artifact came from (sources + context).
+3. **Canon** — curated, stable knowledge substrate; identity and continuity live here.
+4. **Working Memory** — operational notes; not identity-grade unless promoted.
+5. **Episodic Archive** — immutable log of events and interactions.
+6. **Promotion** — controlled movement from working memory into canon.
+7. **Supersession** — explicit replacement of an artifact while retaining history.
+8. **Relationship Graph** — explicit linking of artifacts for navigation and reasoning.
+9. **Canon Release** — signed snapshot of canonical state.
+10. **Retrieval Explainability** — ability to show why a piece of canon was retrieved.

canon/projects/markitect/project_charter_v0.1.md

@@ -0,0 +1,36 @@
+---
+id: CUST-PRJ-MARK-2026-000001
+type: charter
+title: "Markitect — Project Charter v0.1"
+status: active
+owners: ["Bernd", "Custodian"]
+created: "2026-02-24"
+updated: "2026-02-24"
+scope:
+  domains: ["Markitect"]
+  sensitivity: internal
+tags: ["information-management", "canon", "schemas", "knowledge"]
+---
+
+# Markitect — Project Charter v0.1
+
+## Purpose
+Build an efficient information management platform that turns messy inputs into structured, versioned, reusable knowledge artifacts.
+
+## Problem
+Projects accumulate fragmented knowledge across chats, notes, docs, tickets, and repos. Without a stable schema and curation workflow, institutional memory fails.
+
+## Outcome
+A system for:
+- capturing artifacts (chunks, concepts, decisions, patterns)
+- connecting them via explicit relationships
+- producing “canon releases” and reliable retrieval
+- enabling co-creation without confusion
+
+## Boundaries (v0.1)
+- Prioritize core primitives: artifact schema, linking, provenance, versioning.
+- Avoid UI complexity until the model is stable.
+
+## Success criteria (v0.1)
+- Canon artifacts can be generated, reviewed, merged, and released with integrity.
+- Retrieval is precise enough to support co-creation work daily.

canon/projects/markitect/roadmap_v0.1.md

@@ -0,0 +1,34 @@
+---
+id: CUST-RDM-MARK-2026-000001
+type: roadmap
+title: "Markitect — Roadmap v0.1"
+status: active
+owners: ["Bernd", "Custodian"]
+created: "2026-02-24"
+updated: "2026-02-24"
+scope:
+  domains: ["Markitect"]
+  sensitivity: internal
+tags: ["roadmap", "schema", "provenance", "retrieval"]
+---
+
+# Markitect — Roadmap v0.1
+
+## Phase 0 — Artifact Grammar
+- Core types: charter, concept, decision, procedure, roadmap, question, value
+- Relationship fields and lifecycle states
+- Provenance standard
+
+## Phase 1 — Curation Workflow
+- Draft → review → merge → release
+- Quality gates and checklists
+- Deprecation/supersession mechanism
+
+## Phase 2 — Retrieval Layer
+- Indexing pipeline (text + metadata)
+- RAG patterns optimized for canon integrity
+- “Explain why retrieved” provenance output
+
+## Phase 3 — Multi-space Support
+- Multiple domains/spaces with shared primitives
+- Portable rulesets across spaces (proto “jurisdiction” pattern)