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>
38 lines
1.4 KiB
Markdown
38 lines
1.4 KiB
Markdown
---
|
|
id: CUST-PRJ-PERS-2026-000001
|
|
type: charter
|
|
title: "Personhood — Project Charter v0.1"
|
|
status: active
|
|
owners: ["Bernd", "Custodian"]
|
|
created: "2026-02-24"
|
|
updated: "2026-02-24"
|
|
scope:
|
|
domains: ["Personhood"]
|
|
sensitivity: internal
|
|
tags: ["law", "rights", "obligations", "agents", "jurisdictions"]
|
|
custodian_topic_id: "084430ab-c630-48dc-9e1d-d07d1e8fce3c"
|
|
domain: personhood
|
|
---
|
|
|
|
# Personhood — Project Charter v0.1
|
|
|
|
## Purpose
|
|
Develop a multidimensional, testable framework of personhood for mixed-intelligence societies, enabling experimental legal rule systems with tiered rights/obligations and downgrade mechanisms.
|
|
|
|
## Problem
|
|
Binary personhood breaks under heterogeneous agents (humans, AIs, orgs, hybrids). We need portable terminology, tests, and rule modules that jurisdictions can adopt and evolve.
|
|
|
|
## Outcome
|
|
- a dimensional personhood space (capability-based, substrate-independent)
|
|
- a modular rights/obligations library
|
|
- violation → downgrade logic (enforceable within platforms)
|
|
- portability across “interaction spaces” (marketplaces, communities)
|
|
|
|
## Boundaries (v0.1)
|
|
- Focus on conceptual and operational primitives, not a single “ideal law”.
|
|
- Emphasize clarity, testability, and portability.
|
|
|
|
## Success criteria (v0.1)
|
|
- A coherent framework that can be implemented as platform governance.
|
|
- Example jurisdictions and rule packs for specific interaction spaces.
|