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.4 KiB
Markdown
39 lines
1.4 KiB
Markdown
---
|
||
id: CUST-PRJ-FOER-2026-000001
|
||
type: charter
|
||
title: "Foerster Capabilities — Project Charter v0.1"
|
||
status: active
|
||
owners: ["Bernd", "Custodian"]
|
||
created: "2026-02-24"
|
||
updated: "2026-02-24"
|
||
scope:
|
||
domains: ["Foerster Capabilities"]
|
||
sensitivity: internal
|
||
tags: ["taxonomy", "systems-theory", "agency", "governance"]
|
||
custodian_topic_id: "64418556-3206-457a-ba29-6884b5b12cf3"
|
||
domain: foerster_capabilities
|
||
---
|
||
|
||
# Foerster Capabilities — Project Charter v0.1
|
||
|
||
## Purpose
|
||
Create a systems-theoretic taxonomy of computational agency grounded in Foerster’s Non-Trivial Machines, integrating behavior, resources, interaction properties, and governability.
|
||
|
||
## Problem
|
||
Existing capability classifications are fragmented (complexity, architecture, AI tasks, cybernetics, governance/risk). We lack a shared multidimensional map.
|
||
|
||
## Outcome
|
||
A rigorous capability space:
|
||
- dimensions such as governability, reliability, adaptivity, reflexivity, autonomy/sovereignty
|
||
- operational tests / indicators where possible
|
||
- mappings from systems (agents/services/orgs) into the space
|
||
- connections to governance and risk controls
|
||
|
||
## Boundaries (v0.1)
|
||
- Establish vocabulary, dimension definitions, and orthogonality discussions.
|
||
- Produce diagrams and examples rather than chasing completeness.
|
||
|
||
## Success criteria (v0.1)
|
||
- A paper-grade outline + a stable diagrammatic “map”.
|
||
- A small library of example classifications (LLM agent, company process, service).
|