Files

tegwick b93df3aa68 Implement registration UX wishlist W1–W6 (260224)

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>

2026-02-24 22:22:53 +01:00

1.5 KiB

Raw Blame History

id, type, title, status, owners, created, updated, scope, tags, custodian_topic_id, domain

type

title

status

owners

created

updated

scope

Coulomb.social — Project Charter v0.1

Purpose

Build a co-creation platform and socio-economic experiment that enables humans and AI agents to collaborate on challenges with clear rules, incentives, and evolving governance.

Problem

Current collaboration systems either:

centralize control (slow, bureaucratic), or
decentralize without governance (chaotic, unsafe). Mixed-intelligence societies require explicit interaction rules.

Outcome

A platform where:

challenges and solutions are exchanged with clear obligations
trust and reputation emerge from traceable behavior
rulesets can evolve and be ported across spaces (“jurisdictions”)
agents can participate under bounded permissions

Boundaries (v0.1)

Prove core loop before scaling: challenge → work → deliverable → acceptance → reputation.
Governance is a first-class product feature, not a later add-on.

Success criteria (v0.1)

A small number of users (and agents) can co-create reliably with low coordination overhead.
Rule enforcement and auditability prevent obvious failure modes.

1.5 KiB Raw Blame History