BlueHourTechnical Reference
Interfaces, governance and architectural decisions
For enterprise architects: layer interfaces, authority models, security boundaries, architectural decisions and open reconciliation items. Detailed implementation specifications may be discussed through a qualified technical architecture review.
Layer interfaces and dependencies
| Layer | Provides | Depends on | Control boundary |
|---|---|---|---|
| 1. Data / Source of Truth | Authoritative records with provenance; Source-authority registry (which system is authoritative for which fact); Integrity exceptions | None | Write authority per record class. Only the registered authoritative source may assert a fact; every other copy is a reference. |
| 2. Integration / Workflow | Executed workflow steps; API calls and integration events; Dependency map updates | Data / Source of Truth | Integration contracts and the dependency map. A workflow may call only the systems its contract names. |
| 3. Agents / Skills | Agent actions and proposals; Action receipts (what was done, by whom, under what authority); Escalations | Data / Source of Truth, Integration / Workflow, Model Orchestration, Security / Governance | Bounded autonomy. An agent acts only within its registered scope and limits; anything beyond them escalates to a person. |
| 4. Model Orchestration | Model selection and routing; Usage and cost records; Policy exceptions | Data / Source of Truth, Security / Governance | Approved model list and execution policy. Switching providers must not require rebuilding what depends on them. |
| 5. Security / Governance | Allow, deny and escalate decisions; Approvals with named owners; Audit and accountability records | Data / Source of Truth | Policy enforcement points at run time, for people and agents. This layer is where failure propagation is meant to stop. |
| 6. CX / EX Value Flows | Customer and employee experiences; Value delivered; Recourse and explanation requests | Integration / Workflow, Agents / Skills, Security / Governance | Customer-facing authority. What an agent may promise or commit to a customer, and how a customer reaches a person. |
| 7. Measurement / BigBoard | Economic and operating measures; Conversion Yield and BlueHour Units; Complexity position against the Operating Complexity Ceiling | Data / Source of Truth, Integration / Workflow, Agents / Skills, Model Orchestration, Security / Governance, CX / EX Value Flows | Measurement integrity. A measure carries its source and confidence; modeled figures are never presented as realized results. |
| 8. Operating Model Design & Governance | MOM designs and activation decisions; Decision rights; Complexity thresholds and operating constraints | Measurement / BigBoard | Lifecycle control. No MOM expands without evidence; any MOM can be held or stopped. |
Authority model
Every consequential action in the architecture executes in one of four modes. CIMShield never holds unlimited authority over enterprise systems.
| Mode | Meaning | Record |
|---|---|---|
| Already in force | A limit approved in advance that applies continuously (for example a cumulative release ceiling). | Owner of the limit, approval date |
| Automated within approved limits | Executes without waiting because a named owner authorized this action, for this scope, in advance. | Owner, reason, trigger, outcome |
| Requires approval | Waits for a named person to authorize it at the time. | Approver, evidence, decision, outcome |
| Unavailable | The architecture has no control or no authority to perform it. | Recorded as a gap |
Security boundaries
In the architecture
Layer 5, Security / Governance, carries policy enforcement points for people and agents. CIMShield acts only through those defined controls. It complements cybersecurity and enterprise risk management and replaces neither.
On this website
Centralized discovery, compartmentalized security. A static site with no shared authentication, cookies, storage or trust with any other BlueHour site; strict Content-Security-Policy; no third-party requests. The only data collected is what a visitor chooses to type into the executive assessment request, delivered to BlueHour through Netlify Forms.
Architectural decisions
| ID | Decision | Rationale |
|---|---|---|
| ADR-001 | One canonical data source | Architecture, BlueHour60 and scenario data are authored once and generated into the page scripts and the downloadable JSON, so the site cannot hold two definitions of the same thing. |
| ADR-002 | BlueHour60 is the naming authority | MOM numbers, names and purposes are copied from BlueHour60 v1.0 and never edited here. Where another document differs, the canonical name is used and the difference recorded. |
| ADR-003 | Deterministic simulation | No randomness, clock or network in any engine. Identical inputs give identical outputs; scenario state is held in the page address so a run can be replayed and shared. |
| ADR-004 | No hard-coded favorable outcome | The comparison runs the Traditional Operating Model with the visitor's own decisions. Poor decisions are penalized on every path, including modernization. |
| ADR-005 | Proposed mappings are labeled | Associations among layers, IP, CIM, MOMs and outcomes that are not in BlueHour documentation are marked proposed. |
| ADR-006 | Compartmentalized security | Static site, no cookies, storage, logins, analytics or third-party requests; one request form posting to this domain (Netlify Forms). Strict Content-Security-Policy with scripts and styles only from this domain; fonts self-hosted. |
| ADR-007 | Separation of concerns | Presentation (HTML/CSS), architecture data (/data) and simulation logic (/assets/js/engine) are separate files. |
Reconciliation register
Differences between source documents, and items awaiting canonical definition. Nothing listed as open has been resolved by invention.
| ID | Topic | Status | Detail |
|---|---|---|---|
| R-01 | MOM-405 name | Resolved by canon | Some documents refer to MOM-405 as "Truth Verification". The canonical BlueHour60 v1.0 name is Truth Preservation, which this site uses. No MOM was renamed. |
| R-02 | CIM functions | Documented | Earlier documents describe four CIM functions; CIMVolley was added in November 2026. BlueHour60.com's lifecycle line uses "Guard" for the protective function. See the CIM evolution record. |
| R-03 | Entropio / Entropics | Open | Earlier documents use "Entropics". This site uses Entropio and records the earlier name rather than treating the two as equivalent without confirmation. |
| R-04 | TRX, First100 / First365, KTLO 2.0, MOM Lab | Open | Named in the architecture without canonical definitions. Shown as definition pending; nothing has been invented to fill them. |
| R-05 | Totality scope | Open | Earlier materials describe Totality as a broader enterprise coherence view; the current architecture defines it as BUY-HOLD-SELL capital discipline. The site follows the current definition. |
| R-06 | MOM operating specifications | Open | The architecture calls for a 14-field operating specification per MOM. Canonical names and purposes exist for all 60; the fuller specifications on this site cover five MOMs and are marked proposed. The other 55 show the specification as pending. |
| R-07 | Mappings | Open | Layer, outcome, IP and MOM associations on this site are proposed architectural mappings pending BlueHour approval. They change no canonical MOM. |
Versions
| Specification | Version | Date |
|---|---|---|
| BlueHourArchitecture.com architecture data | 2.0.0 | 2026-11-02 |
| BlueHour60 reference architecture | v1.0 | 2026-10-04 |
| CIM capability set | 5 capabilities | 2026-11-01 |
| Simulation engine and scenario | 2.0.0 | 2026-11-02 |