Ratify company canon v1.0 (DEC-2026-001, approved with edits)

Founder edits: Railiance role refined to reliable deployment & operations;
Operational Knowledge added as fourth ecosystem pillar. Edits propagated to
EcosystemMap and DogfoodPolicy. DEC-2026-001 resolved; workplan task
BINKY-WP-0002-T01 closed in file and hub.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

DecisionQueue.md

@@ -22,25 +22,23 @@ fallback_if_no_response: ""
 
 ## Open decisions
 
+*(none)*
+
+## Resolved decisions
+
 ### DEC-2026-001 — Ratify company canon v0
 
 ```yaml
 id: DEC-2026-001
 title: "Ratify company canon v0 (INTENT, AutonomyPolicy, and companion docs)"
 lane: red
-status: prepared
-created_at: "2026-07-16"
-needed_by: "2026-07-23"
-attention_cost: "30 min"
-agent_recommendation: "Review INTENT.md and AutonomyPolicy.md closely (they govern everything else); skim the rest. Approve with edits."
+status: resolved
+outcome: approved with edits
+resolved_at: "2026-07-16"
+resolved_by: Bernd
+edits: "Railiance role refined to reliable deployment & operations (code → SaaS ecosystems and products); Operational Knowledge added as fourth ecosystem pillar (value from experience). Edits propagated to EcosystemMap.md and DogfoodPolicy.md."
 evidence:
-  - INTENT.md
+  - INTENT.md (v1.0)
   - AutonomyPolicy.md
-  - history/260715-InitialExploration.md
-options: [approve, reject, revise, defer]
-fallback_if_no_response: "Canon stays draft; agents operate under conservative lane defaults; no external-facing artifacts produced."
+consequence: "Canon v1.0 in force; AutonomyPolicy lanes active; Green/Blue work may proceed unattended."
 ```
-
-## Resolved decisions
-
-*(append resolved items here: id, title, outcome, date, evidence)*

DogfoodPolicy.md

@@ -32,7 +32,7 @@ dogfood_case: ""
 date: ""
 pain: ""
 capability_used: ""
-pillar: coulomb | net_kingdom | railiance | cross
+pillar: coulomb | net_kingdom | railiance | operational_knowledge | cross
 before: ""
 after: ""
 effort: ""

EcosystemMap.md

@@ -26,9 +26,9 @@ architecture.
 Known assets (to verify/expand): OpsBridge, Keycape, OpenBao patterns, PECS,
 identity-canon, user-engine.
 
-### Railiance — reliable execution and coordination layer
-> Coordinates reliable workflows, deliveries, evidence chains, and operational
-> commitments.
+### Railiance — reliable deployment and operations layer
+> Turns code into SaaS ecosystems and products: reliable deployment,
+> operations, workflows, and operational commitments.
 
 Commercial angles: coordination products, evidence-backed communications,
 delivery/result tracking, workflow reliability.
@@ -36,6 +36,16 @@ delivery/result tracking, workflow reliability.
 Known assets (to verify/expand): coordination-engine, email-connect,
 citation-evidence.
 
+### Operational Knowledge — value from experience
+> Drives the business based on what it knows: turning operational experience
+> into structured, governed, executable knowledge.
+
+Commercial angles: operational knowledge audits, evidence-backed decision
+ledgers, capability maturity snapshots, agentic company cockpit.
+
+Known assets (to verify/expand): citation-evidence, consistency-frame,
+the-custodian / state-hub patterns, this repo's canon-and-queues model.
+
 ## Cross-pillar / unassigned assets
 
 To classify during cartography: ConfigAtlas, feature-control,
@@ -47,7 +57,7 @@ agentic company cockpit).
 
 ```yaml
 capability: <name>
-pillar: coulomb | net_kingdom | railiance | cross
+pillar: coulomb | net_kingdom | railiance | operational_knowledge | cross
 repos: []
 maturity: idea | prototype | internal_use | productizable | product
 dogfood_status: not_used | in_use | proven
@@ -56,11 +66,12 @@ owner: bernd
 notes: ""
 ```
 
-## Triad summary
+## Pillar summary
 
 ```text
-Coulomb      → discover and shape capability
-Net Kingdom  → secure and govern capability
-Railiance    → coordinate and deliver capability
-Binky / OK   → sell, operate, and prove capability
+Coulomb                → discover and shape capability
+Net Kingdom            → secure and govern capability
+Railiance              → deploy and operate capability (code → SaaS products)
+Operational Knowledge  → learn from experience and drive the business on it
+Binky / OK (company)   → sell, operate, and prove capability
 ```

INTENT.md

@@ -1,6 +1,6 @@
 # INTENT
 
-> Status: **draft v0.1** — 2026-07-16. Owner: Bernd Worsch. To be revised as the company canon grows.
+> Status: **v1.0 — ratified 2026-07-16** (DEC-2026-001, approved with edits). Owner: Bernd Worsch. To be revised as the company canon grows.
 
 ## Why this company exists
 
@@ -32,7 +32,8 @@ The ecosystem pillars and their roles:
 | --- | --- |
 | **Coulomb** | Discover, cluster, mature, and package reusable capabilities |
 | **Net Kingdom** | Identity, access, security, governance — make capability governable |
-| **Railiance** | Reliable coordination and delivery — turn intentions into fulfilled commitments |
+| **Railiance** | Reliable deployment and operations — turn code into saas ecosystems and products |
+| **Operational Knowledge** | Value from experience — drive your business based on what you know |  
 
 ## The core loop: the OK Flywheel
 

workplans/BINKY-WP-0002-operating-kernel-bootstrap.md

@@ -18,7 +18,7 @@ Review and approve/revise INTENT.md, AutonomyPolicy.md, and companion docs
 
 ```task
 id: BINKY-WP-0002-T01
-status: todo
+status: done
 priority: high
 state_hub_task_id: "80854b7d-0d0e-4c1d-be66-34d2df08955b"
 ```