Design Principles

These principles govern the architecture of the Endgame system. They define how products are conceived, bounded, and assembled. They operate alongside two companion standards: the Formulation Engineering Standard, which governs formulation, and the Classification Framework, which governs class structure and escalation. The governing objective is maximum physiological capability with minimum catalogue redundancy.

[[1. SYSTEMS OVER ISOLATED PRODUCTS]]
Products are built around complete physiological functions, grouped by function rather than ingredient, outcome, or marketing category.

Each product is defined by a complete physiological function. Single ingredients and single outcomes generally do not constitute a product. Marketing categories do not define the range. Restore is built as a complete overnight recovery system, spanning sleep onset, nervous system down-regulation, and recovery. The market sells sleep aids built on sedation alone.

[[2. MODULARITY & STRUCTURAL INTEGRATION]]
Each product is a module that functions independently and integrates with the wider system. Module boundaries are deliberate. Each function sits in the SKU that owns it rather than being duplicated across products. Any class can be added or removed without disrupting what is already running.

Boundaries between modules are drawn deliberately. Where a dedicated product owns a function, others defer to it. Any overlap is deliberate, placed where compounds reinforce each other. Shield layers onto Core without disturbing it, and organ-specific support can be added only while it is needed and removed once it is not.

[[3. LEAN SYSTEM PRINCIPLE]]
[ 3.1 ] Core Constraint
The system is designed to reduce how many products a user needs to buy.
This governs catalogue architecture, not individual SKU scope. Consolidation is a consequence of strict physiological design criteria. Products are engineered around function and coherence first.

[ 3.2 ] Design Constraint
Products are designed to do one or more of the following:

■ Replace multiple conventional SKUs, or
■ Enable multiple operating modes from a single SKU, or
■ Provide escalation only where disproportionate load exists, or
■ Deliver a function the system requires that no other SKU provides.

[ 3.3 ] SYSTEM LEVEL IMPLICATIONS
[ 3.3.1 ] SKU Compression
Endgame deliberately avoids bloated product lines.
Catalogue growth is not a success metric. Capability density, physiological coherence, and synergy are.

[ 3.3.2 ] Capability Density
Products deliver more physiological function per unit than market norms.
Ingredients are selected for system contribution, not visual complexity.
Capability density is increased through functional integration, not ingredient accumulation.

[ 3.3.3 ] Modular Output
Where the formulation allows, a single SKU supports multiple operating modes.
Complexity is expressed through behaviour, not ingredient count.

[ 3.3.4 ] Application by Product Class
Core. Collapses the daily stack into a single SKU.
Shield. Consolidates multiple defensive domains into one protocol.
Impulse & Augment. Provide multiple valid performance operating modes from two SKUs.

[ 3.3.5 ] Escalation Logic
Base systems handle most cases.
Targeted SKUs exist only where physiological demand materially exceeds baseline coverage.

[ 3.3.6 ] What This Principle Rejects
SKU inflation, redundant overlap, novelty without function. Ingredients or products introduced for trend alignment, label complexity, or perceived innovation rather than genuine physiological contribution.

[ 3.3.7 ] Outcome
More capability with fewer decisions.

[[4. SYSTEM COUPLING]]
Products are designed to interact and produce emergent states, with deliberate overlap where compounds meaningfully reinforce each other.

This is not additive stacking. It is system coupling. Overlap between products is placed deliberately, at the points where compounds reinforce each other. When Impulse and Augment are deployed together, performance states emerge that neither produces alone.

[ 4.1 ] Scope & Boundaries
These principles govern system architecture only. Formulation is governed by the Formulation Engineering Standard: dosing, bioavailability, transparency, overlap governance, and the subtractive-design guardrails, namely evidence gating including trademark discipline, sensory and experiential fit, and format following dose. Class structure and escalation are governed by the Classification Framework. This standard references those and does not restate them.

This document defines how the system is organised. It does not govern how products are formulated or classified.