tegwick
b93df3aa68
W1: Document user-scope MCP config location in ~/.claude/CLAUDE.md —
adds verification and re-registration commands, warns against
settings.json (saves ~12K tokens per registration session).
W2: scripts/register_project.sh + make register-project —
5-step automation: API health → topic lookup → MCP check →
CLAUDE.md from template → progress event.
W3: state-hub/scripts/project_claude_md.template —
parameterised CLAUDE.md with {PROJECT_NAME}/{DOMAIN}/{TOPIC_ID}
placeholders; used by register_project.sh.
W4: Add custodian_topic_id + domain to all 6 canon project charters —
lets agents grep for topic IDs without touching the API.
W5: state-hub/mcp_server/TOOLS.md — compact 30-line tool reference
card; replaces reading the full server.py (~350 lines).
W6: Switch .mcp.json to absolute path + PYTHONPATH env so cwd is not
required; add scripts/patch_mcp_cwd.py for post-registration fix.
Update ~/.claude.json to match (cwd kept for belt-and-suspenders).
W7 (SessionStart hook) deferred: no SessionStart hook type in Claude
Code; PreToolUse with empty matcher fires before every tool call.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
39 lines
1.3 KiB
Markdown
39 lines
1.3 KiB
Markdown
---
|
|
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"]
|
|
custodian_topic_id: "5571d954-0d30-4950-980d-7bcaaad8e3e2"
|
|
domain: markitect
|
|
---
|
|
|
|
# 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.
|