initial priming commit
This commit is contained in:
26
canon/projects/custodian/concepts_seed_v0.1.md
Normal file
26
canon/projects/custodian/concepts_seed_v0.1.md
Normal file
@@ -0,0 +1,26 @@
|
||||
---
|
||||
id: CUST-CPT-CUST-2026-000001
|
||||
type: concept
|
||||
title: "Custodian — Seed Concepts v0.1"
|
||||
status: active
|
||||
owners: ["Bernd", "Custodian"]
|
||||
created: "2026-02-24"
|
||||
updated: "2026-02-24"
|
||||
scope:
|
||||
domains: ["Custodian"]
|
||||
sensitivity: internal
|
||||
tags: ["concepts", "agent", "continuity", "security"]
|
||||
---
|
||||
|
||||
# Custodian — Seed Concepts v0.1
|
||||
|
||||
1. **Identity Substrate** — the canon + episodic archive that preserves continuity across model swaps.
|
||||
2. **Bounded Agency** — doing useful work inside enforced limits and escalation rules.
|
||||
3. **Promotion Workflow** — controlled entry of knowledge into canon via gates and approval.
|
||||
4. **Sensitivity Labeling** — enforced classification (public/internal/confidential/sealed).
|
||||
5. **Memory Poisoning Defense** — preventing untrusted inputs from becoming “truth” in canon.
|
||||
6. **Tool Boundary Enforcement** — permissions enforced where actions happen (not only in prompts).
|
||||
7. **Continuity Drill** — test: reconstruct state from canon after downtime or model change.
|
||||
8. **Canon Release** — signed snapshot enabling rollback and long-term stability.
|
||||
9. **Sovereign Operation** — the system remains functional without external dependencies.
|
||||
10. **Transgenerational Custody** — long-timescale stewardship with governance, consent, and succession.
|
||||
26
canon/projects/custodian/full_circle_map_v0.1.md
Normal file
26
canon/projects/custodian/full_circle_map_v0.1.md
Normal file
@@ -0,0 +1,26 @@
|
||||
---
|
||||
id: CUST-MAP-2026-000001
|
||||
type: concept
|
||||
title: "Full Circle Map: Railiance → Markitect → Coulomb.social → Personhood/Foerster → Custodian"
|
||||
status: active
|
||||
owners: ["Bernd", "Custodian"]
|
||||
created: "2026-02-24"
|
||||
updated: "2026-02-24"
|
||||
scope:
|
||||
domains: ["Custodian"]
|
||||
sensitivity: internal
|
||||
tags: ["strategy", "map", "dependencies"]
|
||||
---
|
||||
|
||||
# Full Circle Map v0.1
|
||||
|
||||
## Dependency Chain
|
||||
- **Railiance** provides: sovereign ops, backups, audits, security primitives.
|
||||
- **Markitect** provides: artifact grammar, canon, provenance, retrieval, curation workflow.
|
||||
- **Coulomb.social** provides: interaction space, governance engine, economics, reputation.
|
||||
- **Foerster Capabilities** provides: capability taxonomy for agency/governability design.
|
||||
- **Personhood** provides: rights/obligations/downgrade frameworks for mixed intelligences.
|
||||
- **Custodian** integrates all layers into a long-lived co-creative institution.
|
||||
|
||||
## Priority Principle
|
||||
Stabilize economically and operationally via robust targeted information processing first; expand into transgenerational/family custodianship step by step.
|
||||
39
canon/projects/custodian/project_charter_v0.1.md
Normal file
39
canon/projects/custodian/project_charter_v0.1.md
Normal file
@@ -0,0 +1,39 @@
|
||||
---
|
||||
id: CUST-PRJ-CUST-2026-000001
|
||||
type: charter
|
||||
title: "Custodian — Project Charter v0.1"
|
||||
status: active
|
||||
owners: ["Bernd", "Custodian"]
|
||||
created: "2026-02-24"
|
||||
updated: "2026-02-24"
|
||||
scope:
|
||||
domains: ["Custodian"]
|
||||
sensitivity: internal
|
||||
tags: ["agent", "canon", "continuity", "sovereignty", "family"]
|
||||
---
|
||||
|
||||
# Custodian — Project Charter v0.1
|
||||
|
||||
## Purpose
|
||||
Build a sovereign, secure, co-creative agent system that supports Bernd’s projects and evolves toward transgenerational custodianship for a biological family.
|
||||
|
||||
## Problem
|
||||
Founder-centric initiative fails under absence. Provider-dependent AI services threaten continuity, sovereignty, and privacy.
|
||||
|
||||
## Outcome
|
||||
A locally operable “institution in software” consisting of:
|
||||
- canon (identity substrate)
|
||||
- memory tiers (working, episodic, vault)
|
||||
- governance (constitution, roles, permissions)
|
||||
- bounded agency (safe tool surface + escalation rules)
|
||||
- reliable infrastructure (Railiance)
|
||||
|
||||
## Boundaries (v0.1)
|
||||
- Co-creation and stewardship for projects only.
|
||||
- Family functionality is future scope; build prerequisites now (security, governance, portability).
|
||||
- No autonomous irreversible actions.
|
||||
|
||||
## Success criteria (v0.1)
|
||||
- Custodian can co-create daily outputs across the project set.
|
||||
- Custodian can reconstruct project states from canon.
|
||||
- Canon is signed, backed up, and portable.
|
||||
38
canon/projects/custodian/roadmap_v0.1.md
Normal file
38
canon/projects/custodian/roadmap_v0.1.md
Normal file
@@ -0,0 +1,38 @@
|
||||
---
|
||||
id: CUST-RDM-CUST-2026-000001
|
||||
type: roadmap
|
||||
title: "Custodian — Roadmap v0.1"
|
||||
status: active
|
||||
owners: ["Bernd", "Custodian"]
|
||||
created: "2026-02-24"
|
||||
updated: "2026-02-24"
|
||||
scope:
|
||||
domains: ["Custodian"]
|
||||
sensitivity: internal
|
||||
tags: ["roadmap", "agent", "governance", "infrastructure"]
|
||||
---
|
||||
|
||||
# Custodian — Roadmap v0.1
|
||||
|
||||
## Phase 0 — Canon + Constitution (now)
|
||||
- Canon schemas and initial project artifacts
|
||||
- Promotion workflow and quality gates
|
||||
- Audit log and sensitivity labels
|
||||
|
||||
## Phase 1 — Co-creation Productivity
|
||||
- RAG over canon + approved repos
|
||||
- Drafting pipelines (charters, ADRs, roadmaps, specs)
|
||||
- Consistency checks across artifacts
|
||||
|
||||
## Phase 2 — Stewardship Automation
|
||||
- Scheduled “health checks”
|
||||
- Roadmap drift detection
|
||||
- Open question aging and review prompts
|
||||
|
||||
## Phase 3 — Sovereign Appliance
|
||||
- Local inference and indexing on dedicated hardware (DGX Spark or equivalent)
|
||||
- Offline mode, replication, disaster recovery
|
||||
|
||||
## Phase 4 — Family Custodianship Prerequisites
|
||||
- Consent model, retention rules, vault hardening
|
||||
- Multi-role governance and succession protocol
|
||||
Reference in New Issue
Block a user