initial priming commit

canon/projects/railiance/concepts_seed_v0.1.md

@@ -0,0 +1,26 @@
+---
+id: CUST-CPT-RAIL-2026-000001
+type: concept
+title: "Railiance — Seed Concepts v0.1"
+status: active
+owners: ["Bernd", "Custodian"]
+created: "2026-02-24"
+updated: "2026-02-24"
+scope:
+  domains: ["Railiance"]
+  sensitivity: internal
+tags: ["concepts", "reliability", "ops"]
+---
+
+# Railiance — Seed Concepts v0.1
+
+1. **Sovereign Ops** — operations that remain functional without external provider control.
+2. **Restore Drill** — a periodic exercise proving the system can be recovered from backups.
+3. **Reproducible Deployment** — same inputs produce the same deployed system.
+4. **Policy at the Tool Boundary** — enforce permissions where the agent calls tools.
+5. **Secrets Hygiene** — secrets never enter plaintext logs, canon, or chat transcripts.
+6. **Immutable Audit Log** — append-only record of actions and changes.
+7. **Degrade Gracefully** — partial functionality under constrained resources/connectivity.
+8. **Operational Minimalism** — minimize moving parts and required human attention.
+9. **Continuous Verification** — automated checks that detect drift and breakage early.
+10. **Version Pinning** — explicit version control of runtime dependencies to avoid surprise changes.

canon/projects/railiance/project_charter_v0.1.md

@@ -0,0 +1,39 @@
+---
+id: CUST-PRJ-RAIL-2026-000001
+type: charter
+title: "Railiance — Project Charter v0.1"
+status: active
+owners: ["Bernd", "Custodian"]
+created: "2026-02-24"
+updated: "2026-02-24"
+scope:
+  domains: ["Railiance"]
+  sensitivity: internal
+tags: ["devops", "reliability", "automation", "sovereignty"]
+---
+
+# Railiance — Project Charter v0.1
+
+## Purpose
+Build a robust, automated DevOps and operational reliability foundation that supports long-lived projects under sovereignty constraints (local-first, provider-independent).
+
+## Problem
+Modern stacks become brittle due to vendor coupling, hidden dependencies, and operational complexity. Founder-driven operations do not scale and do not survive absences.
+
+## Outcome
+A repeatable operational substrate:
+- reproducible deployments
+- automated backups and recovery drills
+- integrity checks and audit trails
+- secure secret management
+- portable infrastructure templates
+
+## Boundaries (v0.1)
+- Focus on pragmatic reliability engineering and automation.
+- Prefer boring, proven primitives over cleverness.
+- No “platform for everyone” ambition until internal stability is proven.
+
+## Success criteria (v0.1)
+- One-click (or scripted) deploy + restore for the Custodian stack.
+- Routine evidence: logs, checks, and recovery tests.
+- Clear runbooks and minimal operational burden.

canon/projects/railiance/roadmap_v0.1.md

@@ -0,0 +1,36 @@
+---
+id: CUST-RDM-RAIL-2026-000001
+type: roadmap
+title: "Railiance — Roadmap v0.1"
+status: active
+owners: ["Bernd", "Custodian"]
+created: "2026-02-24"
+updated: "2026-02-24"
+scope:
+  domains: ["Railiance"]
+  sensitivity: internal
+tags: ["roadmap", "devops", "security", "continuity"]
+---
+
+# Railiance — Roadmap v0.1
+
+## Phase 0 — Baseline (now)
+- Repo layout + IaC baseline
+- Logging + metrics + alerting minimal set
+- Backup strategy + encrypted snapshots
+- Restore drill (documented)
+
+## Phase 1 — Custodian as a Service (internal)
+- Containerized runtime + pinned versions
+- Automated indexing and scheduled maintenance jobs
+- Key management + secret rotation protocol
+- Immutable audit log storage
+
+## Phase 2 — Hardening
+- Threat model + prompt-injection controls for memory
+- Policy enforcement at tool boundary
+- Canary tests and regression suite automation
+
+## Phase 3 — Portability
+- Hardware migration playbook (workstation → DGX Spark → other)
+- Offline mode guarantee + sync strategy