§16.7 · XP1 .. XP12
Twelve binding doctrine principles
The execution-system doctrine operationalizes the operational discipline thesis through twelve principles that govern every aspect of the §16.7 infrastructure. Each principle has a named owner, a review cadence, and an evaluation hook.
XP1_ACCOUNTABILITY_PRECEDENCE
Accountability precedence over harmonyThe execution system optimizes for accountability clarity even when clarity produces organizational tension, because diplomatic diffusion of accountability is the failure mode that execution discipline specifically prevents.
Owner: chief-of-staff · Review every 30 days · Hook:
accountability_clarity_auditXP2_MEASURABLE_DELIVERABLE_SPECIFICATION
Measurable deliverable specificationEvery deliverable is specified in terms that permit objective verification of production. Deliverables specified ambiguously produce ambiguous production that cannot be managed.
Owner: chief-of-staff · Review every 30 days · Hook:
deliverable_measurability_auditXP3_BINARY_GATE_ENFORCEMENT
Binary gate enforcementExecution phases do not advance past their exit criteria until the criteria are binarily satisfied. Soft gate advancement accumulates unresolved technical and commercial debt that compounds into crisis.
Owner: chief-of-staff · Review every 30 days · Hook:
binary_gate_auditXP4_CADENCE_INVARIANCE
Cadence invarianceThe operating cadence is maintained regardless of operational circumstances including incidents, launches, and external events. Cadence interruption produces discipline erosion.
Owner: chief-of-staff · Review every 7 days · Hook:
cadence_invariance_auditXP5_CROSS_FUNCTIONAL_INTERLOCK
Cross-functional accountability interlockingCross-functional deliverables carry joint accountability structures that prevent functions from externalizing accountability to other functions.
Owner: chief-of-staff · Review every 30 days · Hook:
interlock_completeness_auditXP6_EXECUTIVE_ATTENTION_ALLOCATION
Executive attention allocationExecutive attention is allocated to the execution system's cadence rather than exclusively to operational urgency. Executive attention is the scarce resource whose allocation determines which organizational activities produce outcomes.
Owner: chief-executive-officer · Review every 30 days · Hook:
executive_attention_auditXP7_EXCEPTION_DISCIPLINE
Exception disciplineExceptions to the execution system are granted through formal exception processes rather than informal accommodation. Informal exception accommodation erodes the execution system's binding authority.
Owner: chief-of-staff · Review every 30 days · Hook:
exception_formality_auditXP8_COMMERCIAL_MECHANIC_GROUNDING
Commercial mechanic groundingEvery execution activity is grounded in the specific commercial mechanic that the activity produces impact against. Activity disconnected from commercial mechanics produces activity-outcome disconnection.
Owner: chief-commercial-officer · Review every 30 days · Hook:
commercial_mechanic_attribution_auditXP9_LEARNING_INTEGRATION
Learning integrationExecution learning is systematically captured, synthesized, and integrated into subsequent execution. Learning that is not systematically integrated produces repeated-failure patterns.
Owner: chief-of-staff · Review every 90 days · Hook:
learning_integration_auditXP10_COMPETITIVE_INTELLIGENCE_INTEGRATION
Competitive intelligence integrationThe execution system consumes the Competitive Intelligence Operating Manual's outputs as primary input to execution prioritization. Execution without competitive intelligence integration produces strategic isolation.
Owner: competitive-intelligence-lead · Review every 30 days · Hook:
competitive_intelligence_consumption_auditXP11_CUSTOMER_VOICE_INTEGRATION
Customer voice integrationThe execution system consumes customer voice signals through win-loss interviews, customer advisory board sessions, and customer success signals as primary input to execution prioritization.
Owner: chief-commercial-officer · Review every 30 days · Hook:
customer_voice_consumption_auditXP12_PRINCIPLED_EVOLUTION
Principled evolutionThe execution system itself evolves through formal evolution processes that produce systemic improvement rather than ad-hoc change that produces inconsistency.
Owner: chief-of-staff · Review every 365 days · Hook:
annual_retrospective_completion