The Autonomous Enterprise · AE Platform Layer · Module 07

Strategy Dashboard
The Unified Intelligence View
— All suites. All signals. One screen.

The Strategy Dashboard is the platform-layer aggregation surface. It reads from every domain suite currently running on the AE Platform and presents a unified intelligence view for C-suite consumers. Current scope covers the Autonomous Seller suite and Platform modules. Autonomous Buyer and Autonomous Supply Chain panels are on the roadmap as those suites deploy. It writes nothing, decides nothing, and infers nothing. It is only meaningful because the data fabric beneath it — validated by Data Governance and scheduled by GreenOps — is running correctly.

BigQuery · Materialised Views Looker Studio · 5 panels Read-only · No HITL · No ML CTO · CFO · CCO · Real-time Platform Layer · H3 · PI-8 · Minimal Risk
System Context — C4 Level 1

All suite datasets in. One C-suite view out.

The Strategy Dashboard depends on all operational modules — and every additional suite that joins the AE Platform adds a new data stream. It is the measure of how complete the platform deployment is, not the capstone of any single suite. Current AS Suite scope: 5 panels. Autonomous Buyer and Supply Chain panels are planned for H4 / PI-9 as those suites enter production.

Strategy Dashboard — System Context (C4 Level 1 · external actors and system boundary)
Platform-layer aggregation · all suite datasets · BigQuery materialised views · Looker Studio · read-only · C-suite consumers · current scope: AS Suite + Platform modules
Strategy Dashboard Module 07 · Platform Layer · H3 · PI-8 BigQuery materialised view layer 5 named views (one per panel) Looker Studio rendering Scheduled refresh per panel cadence Read-only · no writes to any source No HITL · No ML inference · Minimal Risk AS Suite scope · Buyer/SC panels roadmap H4 SOURCE DATASETS ae_ccai · AS Suite · CCAI Agent leads · turns · opportunities ae_contracts · AS Suite · ContractGuard clause risks · HITL counts ae_financial · AS Suite · RevRec AI classifications · queue depth ae_devices · AS Suite · Asset IQ RUL distribution · fleet risk ae_greenops · Platform · GreenOps carbon savings · ESG metrics ae_governance · Platform · Data Gov. validation rates · quarantine counts future: ae_buyer · ae_supplychain Buyer + Supply Chain (H4 · PI-9) CTO Full dashboard · all 5 panels Drill-through to HITL queues CFO / CCO RevRec posture · compliance panel
Strategy Dashboard
AS Suite sources
Platform sources
Future suites (H4 roadmap)
Panel Source Table

Five panels. Five refresh cadences. One HITL drill-through pattern.

Each panel has a distinct data source combination, refresh cadence, and consumer. HITL counts are presented as read-only indicators with drill-through links to the originating module queue. Each panel carries a declared freshness SLO — the maximum permissible data age before Cloud Monitoring fires a staleness alert. The dashboard takes no action; it surfaces the signal.

PanelViewSourcesRefreshFreshness SLOPrimary consumerHITL drill-through
Pipeline Healthsd_pipeline_healthae_ccai · ae_contracts · Salesforce REST15 min≤ 30 minCTO · Head of SalesHITL-01 · HITL-02 counts → originating queue
RevRec Posturesd_revrec_postureae_financial · ae_finrisk5 min≤ 10 minCFO · Finance ControllerHITL-04 queue depth → RevRec AI module
Fleet Intelligencesd_fleet_intelligenceae_devices + ae_governance quality flag JOIN1 hour≤ 75 minCTO · VP Field ServiceHITL-06 count → Asset IQ module queue
EU AI Act Compliancesd_compliance_postureAll HITL counts · Vertex AI Model Registry · ae_governance1 hour≤ 75 minCCO · Legal · CTOAll 11 HITL indicators → originating module queues
ESG / GreenOpssd_esg_summaryae_greenops.job_metrics · MTD aggregation1 hour≤ 90 minSustainability team · CFONone — read-only ESG summary
Dashboard Mockup

Five panels. One screen. Sub-5-second render on cached views.

The Looker Studio dashboard renders all five panels from BigQuery BI Engine-accelerated materialised views with a Looker Studio cache TTL of 15 minutes. Each panel shows its last refresh timestamp. HITL counts drill through to the originating module queue. Render time is sub-5 seconds on cached views; cold-cache render (after TTL expiry) is sub-12 seconds on BI Engine.

Looker Studio · AE Platform Strategy Dashboard
Last full refresh: 08:00 UTC
Pipeline Health15 min
€4.2M
Pipeline MTD
87%
Qualification rate
3
HITL-01 pending
↗ drill: HITL-01 queue · CCAI Sales Agent
RevRec Posture5 min
94%
Auto-classified
7
HITL-04 queue
2.1h
Avg HITL SLA
↗ drill: HITL-04 queue · RevRec AI
Fleet Intelligence1 hr
2
RUL critical
11
RUL <30%
1,847
Monitored assets
MCH-0042 highlighted · ↗ drill: HITL-06 · Asset IQ
EU AI Act Compliance1 hr
11/11
HITL checks ✓
5/5
Model cards current
0.93
DQ avg score
● COMPLIANT
ESG / GreenOps Platform · MTD
18.4
kgCO₂eq saved MTD
14/22
Jobs deferred
41%
Avg carbon reduction
CSRD
Scope 3 Cat. 11 eligible
Production Readiness · SLO · IAM · Observability

Five views. Five SLOs. One IAM boundary. Zero silent failures.

Every data-serving surface on the AE Platform carries a documented freshness SLO, an IAM access boundary, and a Cloud Monitoring alerting policy. The Strategy Dashboard is no exception. The interactive section below models the live SLO state, the BigQuery IAM role bindings that enforce panel-level access control, and the Cloud Monitoring alert conditions that fire when any materialised view breaches its freshness SLO. Simulate a staleness breach to see the alert path activate.

View Freshness SLO · Cloud Monitoring · Real-time status
Each materialised view has a declared freshness SLO. SLO breach triggers a Cloud Monitoring alert policy → PagerDuty → on-call SRE. BigQuery BI Engine slot reservation: 1 GB · all sd_* views. Looker Studio cache TTL: 15 min.
BigQuery IAM · Access Control Model
IAM enforced at three layers: (1) BigQuery dataset-level roles scoped to sd_* views only — no access to ae_* source tables. (2) Looker Studio workspace-level access lists per consumer role. (3) Column-level security on regulated fields (HITL audit records, revenue figures) via BigQuery column masking policies.
CTO · Head of Sales · VP Field Service
BQ role: roles/bigquery.dataViewer
scoped to: ae-platform.sd_views.*
Looker workspace: strategy-dashboard-full
panels: all 5
Column masking: revenue fields visible · HITL queue counts visible · SHAP explanations: drill-through only (originating module)
CFO · Finance Controller · Sustainability
BQ role: roles/bigquery.dataViewer
scoped to: ae-platform.sd_views.revrec, sd_views.esg
Looker workspace: strategy-dashboard-finance
panels: RevRec Posture · ESG/GreenOps
Column masking: revenue figures visible · fleet RUL data masked · HITL counts for HITL-04 only
CCO · Legal · Compliance
BQ role: roles/bigquery.dataViewer
scoped to: ae-platform.sd_views.compliance, sd_views.revrec
Looker workspace: strategy-dashboard-compliance
panels: EU AI Act Compliance · RevRec Posture
Column masking: all 11 HITL check indicators visible · revenue figures masked · audit log access via separate BigQuery audit role (not Looker)
Regulatory audit access: EU AI Act auditors access HITL audit records directly in BigQuery via a separate roles/bigquery.dataViewer binding on ae-platform.ae_audit.* — no Looker seat required. The Strategy Dashboard compliance panel is a summary view; the primary evidence chain lives in BigQuery and is immutable.
Cloud Monitoring · Alerting Policies · Observability
Five alert policies — one per materialised view — monitor refresh lag against each panel's freshness SLO. Breach → Cloud Monitoring notification channel → PagerDuty → on-call SRE. Stale views display a visible staleness banner in Looker Studio; they never silently surface outdated data as current.
Alert Policy Definitions
sd_pipeline_health — alert if last_refresh_age > 30 min
Severity: WARNING · Notification: Slack #ae-platform-ops
sd_revrec_posture — alert if last_refresh_age > 10 min
Severity: CRITICAL · Notification: PagerDuty P1 · Finance on-call
sd_fleet_intelligence — alert if last_refresh_age > 75 min
Severity: WARNING · Notification: Slack #ae-platform-ops
sd_compliance_posture — alert if last_refresh_age > 75 min
Severity: CRITICAL · Notification: PagerDuty P1 · CCO on-call
sd_esg_summary — alert if last_refresh_age > 90 min
Severity: WARNING · Notification: Slack #ae-platform-ops
Graceful Degradation Behaviour
SLO warning (view lagging but not breached): Panel shows amber staleness indicator with last-refresh timestamp highlighted. Data is still served; operator is alerted.
SLO breach (view beyond SLO threshold): Panel overlays a "Data stale — last valid refresh: HH:MM UTC" banner. Metric values are hidden. Drill-through links disabled. Alert fires.
Cloud Run refresh job failure: Cloud Monitoring dead-man alert fires if no successful refresh job completion is recorded within 2× the panel's cadence. Separate alert from staleness — covers job crash vs slow execution.
Stale data is never presented as current. The compliance panel showing 11/11 HITL checks COMPLIANT when the underlying view is 4 hours old would be a regulatory risk — the alert + banner pattern prevents this.
Architecture Decision Records

Three dashboard decisions. Each chosen over a real alternative — with cost evidence.

ADR-SD01 — Strategy Dashboard
BigQuery materialised views over direct Looker Studio data source connections
Looker Studio can connect directly to BigQuery tables with no intermediate view layer. Rejected for three reasons: (1) Direct connections expose the dashboard to schema migrations in source modules — if Asset IQ changes ae_devices, a direct connection breaks immediately. Materialised views provide an abstraction boundary. (2) Direct queries run at dashboard load time, generating BigQuery slot consumption on every session. Materialised views pre-compute on a schedule, amortising compute cost. (3) The materialised view layer is queryable by any BigQuery principal with read access — the same data the CTO sees in Looker is queryable via SQL, enabling regulatory audit access without a Looker seat.
Trade-off quantified: Direct queries at 10 daily CTO sessions × 5 panels × ~500 MB scan each = ~25 GB/day on-demand BigQuery cost (~$0.125/day at $5/TB). Materialised view refreshes = 5 scheduled jobs/day at ~200 MB each = ~1 GB/day ($0.005/day). Materialised view approach reduces query cost by ~95% at this session volume, and eliminates schema-coupling risk entirely.
Accepted · Platform Layer · Strategy Dashboard
ADR-SD02 — Strategy Dashboard
Per-panel refresh cadence over a single global refresh interval
A single global refresh interval (e.g., 15 minutes for all panels) was considered. Rejected because the five panels have materially different staleness tolerances. The RevRec posture panel needs 5-minute freshness — the Finance Controller checks it multiple times daily and SLA compliance depends on queue visibility. The fleet intelligence panel is acceptable at 1-hour freshness because Asset IQ's HITL-06 notification is the operational alert path, not the dashboard. Running fleet queries at 5-minute cadence produces unnecessary BigQuery compute cost with no operational benefit. Per-panel cadence balances freshness with cost.
Cost delta: sd_fleet_intelligence at 5-minute cadence = 288 refreshes/day × 400 MB scan = ~115 GB/day ($0.58/day). At 1-hour cadence = 24 refreshes/day × 400 MB = ~9.6 GB/day ($0.048/day). Per-panel cadence saves ~$0.53/day on fleet view alone — ~$190/year — with zero operational loss because HITL-06 is the real-time alert path for critical fleet events.
Accepted · Platform Layer · Strategy Dashboard
ADR-SD03 — Strategy Dashboard
HITL drill-through to originating module queue — not HITL action from dashboard
An alternative proposed surfacing HITL approval/denial buttons directly in the Strategy Dashboard. Rejected on architectural grounds. The Strategy Dashboard is a platform-layer read-only surface — adding write paths to HITL queues would require IAM changes, HITL audit trail modifications, and EU AI Act Article 14 logging currently scoped to the originating module. More practically, HITL decisions require context — the SHAP explanation, the confidence score, the flagged clause — that lives in the originating module's queue UI, not in a dashboard panel. The drill-through pattern is deliberate: it surfaces the signal at the dashboard level and routes the decision to where the context lives.
IAM risk of alternative: Adding write paths from the Strategy Dashboard would require expanding its IAM scope from roles/bigquery.dataViewer to roles/bigquery.dataEditor on ae_audit — a significant privilege escalation for a surface consumed by 20+ C-suite users. The read-only constraint is not a design limitation; it is an access control property.
Accepted · Platform Layer · Strategy Dashboard
Stakeholder Rebuttals

Four objections. Each with an architectural answer.

CTO · S-01
Is a read-only dashboard worth its own platform module?
"This is a Looker Studio dashboard over BigQuery. It writes nothing, decides nothing, uses no ML. Why is this a platform module instead of a reporting artifact?"
Architectural response
The dashboard is a platform module because of what it aggregates, not what it does. It is the only surface in the AE Platform that presents cross-suite intelligence — pipeline health from the AS Suite, workforce signals from AHR (future), compliance posture from the Platform Governance layer — in a single materialised view. The BigQuery materialised view layer is a queryable data product that any BigQuery principal can access for regulatory audit. The EU AI Act compliance panel — presenting live HITL completion rates, model card currency, and data quality scores across all 11 compliance checkpoints — is architecturally significant. No other module has visibility across all of these simultaneously.
Evidence: ADR-SD01 (materialised view as queryable platform asset) · sd_compliance_posture (11 HITL checkpoints across all suites)
Enterprise Architect · S-08
What happens to the dashboard when a source module is quarantined?
"If Data Governance quarantines APAC-East data and Asset IQ stops producing RUL predictions for those units, what does the fleet panel show?"
Architectural response
The fleet intelligence materialised view includes a data_quality_flag field from ae_governance. Units with stale features due to quarantine are shown with a grey data_unavailable indicator — not a green/amber/red status. The panel caption notes "N units: data pending reinstatement" when quarantine count is non-zero. Stale data is never presented as current. The compliance posture panel also surfaces the quarantine event — the Data Governance section shows the current quarantine count and steward resolution status. The dashboard degrades gracefully with visible flags.
Evidence: sd_fleet_intelligence view (data_quality_flag JOIN with ae_governance) · sd_compliance_posture (quarantine count)
CFO · S-03
How fresh is the data — what's the worst-case lag?
"If I open the dashboard at 08:45 and the fleet panel last refreshed at 08:00, I'm looking at 45-minute-old data for a panel that might show a critical asset. What's the actual worst-case lag?"
Architectural response
Worst-case data lag per panel: RevRec Posture and FinRisk — max 5 minutes stale (SLO: 10 min). Pipeline Health — max 15 minutes (SLO: 30 min). Fleet Intelligence and Compliance Posture — max 1 hour (SLO: 75 min). For fleet intelligence, 1-hour-old data is operationally acceptable because Asset IQ's HITL-06 notification reaches the Field Service Manager directly — the dashboard is not in that alert path. If a critical fleet event occurs during the 1-hour window, the FSM is notified directly. Each panel shows its last refresh timestamp, and Cloud Monitoring alerts before SLO breach.
Evidence: ADR-SD02 (per-panel refresh cadence) · SLO table (this module) · Asset IQ HITL-06 (direct notification to FSM, not via dashboard)
CCO · S-02
Does the compliance panel constitute EU AI Act documentation?
"If a regulator asks for EU AI Act compliance documentation, can I show them the compliance panel? Or is it a summary of documentation that lives elsewhere?"
Architectural response
The compliance posture panel is a summary view — it answers "is the posture healthy right now?" The actual EU AI Act documentation a regulator needs is: HITL audit records in Firestore and BigQuery (Article 14), SHAP explanations in BigQuery (Article 13), Model Cards in Vertex AI Model Registry (Article 11), and Data Governance lineage records (Article 11). All are queryable directly via a dedicated auditor BigQuery role — no Looker seat required. The compliance panel is the dashboard warning light — it tells the CCO when something needs attention. The service manual is in BigQuery, open, auditable, and permanent.
Evidence: sd_compliance_posture (aggregates HITL rates from ae_audit) · BigQuery HITL audit records · Vertex AI Model Cards · Data Governance lineage chain · IAM: auditor role on ae_audit.* (separate from Looker access)
Interactive Demo

Three events. Watch the materialised views refresh. Watch the panels update.

Select a suite event and run the simulation. The left panel shows the source event arriving and the materialised view refresh firing. The right panel shows the five dashboard panels — watch the relevant one highlight and update.

⚠ Simulation note: event steps are compressed to 700ms intervals for illustration. In production, actual refresh cadences are 5 minutes (RevRec), 15 minutes (Pipeline), and 1 hour (Fleet / Compliance / ESG) — Cloud Run scheduled jobs, not real-time push. The demo illustrates the event → view → panel causality chain, not the real-world timing.
Suite Event
Deal Closed · Pipeline Update
RUL Alert · Fleet Event
HITL SLA Slip · Compliance Amber
Source Event Feed
IDLE
Select an event and press Run
Strategy Dashboard · Live
READY
Pipeline Health 15 min
€4.2M
Pipeline MTD · 3 HITL-01 pending
↗ 3 HITL-01 items → CCAI queue
RevRec Posture 5 min
94%
Auto-classified · 7 HITL-04 queue
↗ 7 HITL-04 items → RevRec AI queue
Fleet Intelligence 1 hr
2
RUL critical · 11 amber · 1,847 monitored
↗ MCH-0042 · HITL-06 open → Asset IQ queue
EU AI Act Compliance 1 hr
11/11
HITL checks · 5/5 model cards current
● COMPLIANT
↗ HITL-04 SLA at 85% → RevRec AI queue
ESG / GreenOps Platform 1 hr
18.4
kgCO₂eq saved MTD
14/22
Jobs deferred
41%
Carbon reduction
CSRD SCOPE 3
Category 11 eligible
Materialised view: idle last refresh: 08:00
Event Source
originating system
View Refreshed
materialised view
Panel Updated
Looker Studio panel
HITL Drill-through
originating queue
AE Platform Navigation
Three platform modules.
The foundation was first.

Data Governance (H1 · PI-1) is the prerequisite that makes this dashboard meaningful. GreenOps (H3 · PI-7) contributes the ESG panel. The Strategy Dashboard (H3 · PI-8) closes the platform layer for the AS Suite. Autonomous Buyer and Supply Chain panels follow in H4 · PI-9. Deployment order: M-08 → M-06 → M-07.

M-08
Data Governance · H1 Foundation →
The prerequisite. Nothing the dashboard shows is valid without it.
M-06
← GreenOps Platform
Produces the ESG panel data · carbon-aware scheduling
INDEX
← AE Platform Index