Operating Principles
The Architecture Principles mix two kinds of principle: those about how systems are structured (architecture) and those about how work is performed (operating). This page separates them and adds operating-specific principles evidenced across the ecosystem. It is a reclassification and extension — the existing principles page is unchanged.
Split of the existing 12 principles
| # | Principle | Kind |
|---|---|---|
| 1 | Reproducibility & complete provenance | Both — leans Operating (how work is recorded) |
| 2 | Definition vs. derivation (inputs ≠ outputs) | Architecture |
| 3 | Knowledge is referenced, never owned | Architecture |
| 4 | Stage is state, not location | Architecture |
| 5 | Composable, opt-in services | Architecture |
| 6 | Measurement / evaluation is first-class | Operating |
| 7 | No speculative abstraction (four-part test) | Operating (how we decide to build) |
| 8 | Honest realization labelling | Operating (how we document) |
| 9 | Layered leverage (capability flows upward) | Architecture |
| 10 | Phase-gated, reviewable change | Operating |
| 11 | Deterministic rules decide; AI explains | Operating (how decisions are made) |
| 12 | Capabilities are first-class & repo-independent | Architecture |
Architecture principles (structure): 2, 3, 4, 5, 9, 12. Operating principles (work): 1, 6, 7, 8, 10, 11 — plus the additions below.
Operating Principles (how work is performed)
Each is grounded in documented evidence.
O1. Humans own capture, review, and approval
The founder’s irreducible responsibilities are capture, review, and approval; classification, enrichment, and structuring are automated where possible. (Source: FIP “founder responsibility boundary”.)
O2. Nothing is ever auto-sent
No externally-visible output (email, proposal, published report) leaves the ecosystem without a human approval
gate. (Source: outreachagent “golden rule”; assessment ready_for_review → approved.)
O3. Deterministic first; AI explains, never decides
Routing, retrieval, scoring, and recommendations are deterministic; an LLM narrates results from structured facts only. (Source: assessment engine §13; PersonalOps “determinism-first, no embeddings at runtime”.) — the operating form of Principle 11.
O4. Capture first
Prioritise low-friction capture over structuring completeness — “capture now, classify on review.” Most intelligence is lost because it is never captured. (Source: FIP Principle 9.)
O5. Maturity is a human quality gate
Intelligence advances through maturity states only by founder judgement about evidence, not an automation milestone. (Source: FIP “maturity as quality gate”.)
O6. Immutable, versioned contracts; consumers pin versions
Published products are immutable and versioned; consumers depend on an exact version and treat it as a
read-only contract. (Source: intelproducts pack contract; ADR-0004 (WIL) immutable runs.)
O7. Evidence-first; record uncertainty
Documentation and decisions are based on documented evidence; unknowns are labelled, never invented. (Source: Principle 8; this portal throughout.)
O8. Phase-gated change with architecture review
Work proceeds in small, independently reviewable phases; each ends with an architecture review before the next begins. (Source: WIL implementation philosophy; the portal’s own A–E phases.)
O9. One-way feedback (never mutate a consumed artefact)
Feedback improves the system by producing a new immutable version, never by mutating an artefact others already consume. (Source: ADR 0005 (proposed) Hermes design; immutable-runs principle.)
Operating vs Architecture at a glance
graph LR
subgraph ARCH["Architecture Principles — how systems are STRUCTURED"]
A2[Definition vs derivation]
A3[Knowledge referenced, not owned]
A4[Stage is state]
A5[Composable services]
A9[Layered leverage]
A12[Capabilities first-class]
end
subgraph OPS["Operating Principles — how WORK is performed"]
O1a[Humans own capture/review/approval]
O2a[Nothing auto-sent]
O3a[Deterministic decides / AI explains]
O4a[Capture first]
O7a[Evidence-first]
O8a[Phase-gated review]
end
ARCH -. governs .-> OPS
Related
- Architecture Principles (the source list; unchanged)
- AI Collaboration Model · Portfolio Operating Model