HQ vs Runtime OS Boundary
Separate systems. Same math. Different execution responsibilities.
HQ

Command House What HQ computes

  • authority stack decisions
  • mode weighting: Shush / Carr / MAYD
  • placement and chamber residency
  • deploy class and monetization class
  • truth lane, proof lane, claim lane
  • invention, publishing, packaging, governance

Shared math profile

  • Truth Spine Core
  • Holmes
  • Carr Matrix
  • House Black Box
  • TS API Key permissions
  • F.P.A. / Polarity
Runtime OS

Separate Worker/System What Runtime OS executes

  • client-side session experience
  • Daisy Core entry artifact unlock behavior
  • Daisy Scan consequence flow
  • live route execution
  • presentation of the brilliant user-facing experience
  • delivery feel, timing, session state, transitions

Boundary contract

  • HQ calculates
  • Runtime OS executes
  • same math profile
  • different system boundary
  • no collapse of Runtime OS into HQ
This chamber exists to stop future flattening. Runtime OS is not a helper file inside HQ. It is a separate system that consumes the same mathematical authority.