initial priming commit

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.