Mission Control doc

Integration Matrix

fusion-layer-integration-matrix.md

Fusion-Layer Integration Matrix — Vertical Integrations × Physical AI × Company Lens × Capabilities

Date: 2026-05-12 Status: Composition / spec — the connecting layer between vertical-fusion-checklist (current-state inventory) + milestones-manifesto (forward-looking build) + the actual fusion layer (per PLATFORM.md Interfaces). Companion to: vertical-fusion-checklist.md + milestones-manifesto.md + v_platform/PLATFORM.md Ontology System §Interfaces. Purpose: Each vertical integration (voice / VPS / RMM / Backup / MDR / PSA / etc.) cross-references fusion-layer interfaces used + physical AI dimension + company lens variants + capabilities enabled. This is the fusion layer — not a feature on top of it.

Terminology lock (per operator 2026-05-12): ADE Factory = val-forge throughout this matrix + sibling MC docs. Per ADR-011 + ADR-025.

Context: Why the Fusion Layer

Per PLATFORM.md Ontology System §Interfaces:

"Interfaces — the fusion-layer primitive. A focus point for OODA loops, genies, and value-engines that lets the same logic run across many concrete subtypes — physical OR virtual. This is what makes ValOS the fusion layer, not a feature on top of it. A genie targets the interface, never the concrete subtype, so the same code runs across fleet ops AND comms ops AND engagements."

The fusion is in the cross-reference. A vertical integration like "RMM" isn't its own siloed feature — it's the Asset interface + Site interface + Operator interface running endpoint-management logic across multiple concrete subtypes (Windows endpoint + macOS endpoint + Linux server + mobile + rugged device + kiosk + manufacturing PLC) across multiple company lenses (MSP IT services + manufacturing OT + healthcare devices + retail kiosks) with multiple capability shapes (monitor + automate + remote + patch + script).

Same logic; many subtypes. That's the fusion.

The Eight Fusion-Layer Interfaces

Per PLATFORM.md Ontology System §Interfaces:

#	Interface	Kind	Concrete subtypes (examples — list grows like coral)
I1	WorkSpace	physical	Factory · Office · Vehicle · Greenfield · Field site · Remote work-from-home
I2	Asset	physical	Robot · Camera · PLC · Drone · RF-sensor · Endpoint (Windows / macOS / Linux / mobile / iOS / Android / ChromeOS) · Server · Network gear · Kiosk · Signage · Rugged device · Manufacturing portable · IoT sensor · Vehicle hardware
I3	Site	physical	HQ · Branch · Customer-site · Field-installation · Data center · Co-located rack · Edge location
I4	Conversation	virtual	email · Teams · SMS · voice · webchat · WhatsApp · Instagram · Facebook · Telegram · Signal · in-app chat
I5	Engagement	virtual	legal-matter · healthcare-placement · MSP-ticket · sales-deal · debt-recovery-case · construction-project · manufacturing-job · service-contract · investment-decision · DR-incident · marketing-campaign
I6	Operator	virtual	human · agent (val-agent / val-orchestrator) · role (technician / manager / executive) · system-account · service-account · external-user
I7	Document	virtual	PDF · DOCX · transcribed-audio · scraped-web · markdown · structured-data (JSON / CSV / XML) · spreadsheet · presentation · image-with-OCR · video-with-transcript
I8	Schedule	virtual	appointment · shift · delivery · maintenance-window · backup-window · patch-window · audit-cycle · invoicing-cycle · sprint · cycle · recurring-task

Master Integration Matrix

Each vertical integration cross-references: Interfaces Used + Physical AI Hooks + Company Lens + Capabilities + Mission Categories.

Communications + Comms

Voice / Comms (val-switch + carrier partner)

Dimension	Detail
Vertical integration ID	L8.12 (per fusion checklist)
Interfaces used	I4 Conversation (voice subtype) + I6 Operator (human + agent) + I8 Schedule (call-back appointments)
Physical AI hooks	Phone hardware (SIP phones / WebRTC clients / mobile) + Carrier infrastructure (SBC / SIP trunks / PSTN gateways)
Company lens variants	Per-vertical: legal-firm hold-on-call vs MSP technician dispatch vs healthcare patient-callback vs manufacturing customer-service vs SBR debtor-call-strategy
Capabilities enabled	Inbound routing + outbound dispatch + recording + transcription + agent-assist + IVR + queue management + call-back scheduling + conference + voicemail
Mission categories	`comms.voice.inbound.v1` / `outbound.v1` / `record.v1` / `transcribe.v1` (via val-ingest cross-cut)
Cross-cuts	val-ingest (transcripts) + val-orchestrator (call-flow) + val-policy (recording consent) + val-ledger (call b_facts)
Reference	doc 25 F167 + F168 + ADR-022 candidate

Email / SMS / Teams / WhatsApp / Webchat (val-switch omni-channel)

Dimension	Detail
Interfaces used	I4 Conversation (email/SMS/Teams/WhatsApp/webchat subtypes) + I6 Operator + I7 Document (attachments)
Physical AI hooks	n/a (purely digital channels)
Company lens	Per-vertical: legal client correspondence vs MSP support ticket vs healthcare patient notification vs SBR debtor outreach
Capabilities	Multi-channel inbound + outbound + thread continuity + attachment ingestion + delivery confirmation + read receipts
Reference	doc 25 F167

Hosting + Infrastructure

VPS / DNS / Web Hosting (val-host candidate)

Dimension	Detail
Vertical integration ID	L8.13 + L3.13 (val-host engine candidate)
Interfaces used	I2 Asset (server / DNS record / certificate) + I3 Site (Customer-site / Data center / Edge location) + I8 Schedule (renewal windows + patch windows)
Physical AI hooks	Cloud infrastructure (AWS / Azure / GCP) + bare-metal servers + edge devices + DNS infrastructure providers
Company lens	Per-client: client-A website hosting vs client-B email infrastructure vs client-C custom application; per-deployment scope
Capabilities	Provisioning + DNS management + reverse proxy + certificate auto-renewal + monitoring + per-tenant isolation + cost reporting
Mission categories	`host.provision.v1` / `host.cert.renew.v1` / `host.dns.update.v1` / `host.proxy.config.v1`
Cross-cuts	val-grid (CA + cert chain) + val-cargo (Cloudflare / Route 53 APIs) + val-policy (per-tenant capability binding)
Reference	doc 25 F167 + F168 + milestone M8

Endpoint + RMM

RMM / UEM / MDM Consolidation (ValOS native; informed by zerotouch.ai + Tactical RMM)

Dimension	Detail
Vertical integration ID	L8.2 + L2.6 (cross-platform Rust agent)
Interfaces used	I2 Asset (Endpoint / Server / Network gear / Mobile / IoT / Kiosk) + I3 Site (HQ / Branch / Customer-site / Field-installation) + I6 Operator (technician + system-account) + I8 Schedule (patch windows + monitoring intervals)
Physical AI hooks	Substantial — embodied agents on Windows / macOS / Linux / iOS / iPadOS / tvOS / watchOS / Android / ChromeOS / servers / VMs / kiosks / signage / rugged / manufacturing portable / RF sensors. Same agent runtime; subtype-aware capability dispatch.
Company lens	Per-MSP-client: SBR debt-recovery laptops (low-touch consumer) vs New Era IT (AU) MSP fleet (operator-team-managed) vs manufacturing-vertical PLCs (OT scope) vs healthcare clinic kiosks (patient-facing)
Capabilities	Monitor (CPU/disk/memory/services/events) + Remote access (desktop/shell/file/registry) + Automation (scheduled scripts + remediation) + Alerting (email/SMS/webhook) + Patching (Windows + Chocolatey + apt + macOS pkg + mobile OTA) + Scripting (bash + batch + PowerShell + Python + Nushell + Deno)
Mission categories	`mission.monitor.endpoint.v1` + `automation.run.v1` + `patch.apply.v1` + `software.install.v1` + (remote-access via val-cargo MeshCentral) + (scripting via val-bay Computes)
Cross-cuts	val-grid (provisioning + CA) + val-policy (capability gates) + val-bay (scripting Computes) + val-cargo (MeshCentral remote-desktop) + val-switch (alerting) + val-ontology (Agent entity per doc 33 F219 + doc 35 F236 + doc 40 F266 entity convergence)
Reference	doc 35 + ADR-012 + milestone M9.3

Backup + Disaster Recovery

Backup (Kopia + Duplicati integrate-with)

Dimension	Detail
Vertical integration ID	L8.8
Interfaces used	I2 Asset (Data / Storage backend / Repository) + I7 Document (snapshot contents) + I8 Schedule (backup windows + retention windows) + I3 Site (per-client repository location)
Physical AI hooks	Storage backends (S3 / Azure Blob / GCS / B2 / WebDAV / SFTP / local NAS / NAS appliance / cloud-storage hardware) — physical infrastructure but managed via APIs not embodied agents
Company lens	Per-client: SBR financial records (long-retention) vs MSP client laptop backups (short-retention + DR) vs manufacturing process-data archival (compliance-driven) vs healthcare patient-record backup (HIPAA-compliant)
Capabilities	Backup (snapshot creation) + Restore (file-level + full) + Retention policy enforcement + Verification + Reporting + Cross-engine policy abstraction (Kopia primary + Duplicati alternative)
Mission categories	`mission.backup.schedule.v1` + `run.v1` + `verify.v1` + `report.v1` + `restore.v1` + `retention.v1`
Cross-cuts	val-cargo (Kopia/Duplicati API) + val-orchestrator (scheduling) + val-policy (capability binding) + val-desk OpsCenter Metrics (backup KPIs per doc 28 F170 + 3 added per doc 36 R239) + val-track (failure ticket auto-creation) + Problem-Solving (complex restore + DR scenarios per doc 36 F248)
Reference	doc 36 + ADR-019 backup-state directory

Security + Detection

SIEM (Wazuh)

Dimension	Detail
Vertical integration ID	L8.3
Interfaces used	I2 Asset (Endpoint / Network gear / Sensor) + I7 Document (logs / events / packets) + I8 Schedule (audit windows + correlation windows)
Physical AI hooks	Wazuh agents on endpoints (cross-platform) + network gear (syslog) + cloud workload monitors + container security — physical + virtual
Company lens	Per-MSP-client: compliance-driven (HIPAA / SOC 2 / GDPR / Australian Privacy Act 1988) vs incident-detection-driven vs threat-hunt-driven
Capabilities	Log aggregation + Correlation (cross-source) + Alert generation + Threat hunting + Compliance reporting + File integrity monitoring + Configuration assessment + Vulnerability detection + Cloud workload protection
Mission categories	`mission.siem.ingest.v1` + `correlate.v1` + `alert.v1` + `hunt.v1` + `compliance-report.v1`
Cross-cuts	val-cargo (Wazuh API) + val-ingest (log ingestion) + val-orchestrator (correlation Missions) + val-policy (alert routing) + val-track (incident ticket creation) + MDR (Defender for Business correlation per doc 37 F246) + Problem-Solving (complex incident analysis)
Reference	doc 25 F166

EDR / MDR (Microsoft Defender for Business + ValOS-as-MDR-provider)

Dimension	Detail
Vertical integration ID	L8.4
Interfaces used	I2 Asset (Endpoint) + I7 Document (detection / investigation / forensics) + I6 Operator (analyst + auto-response system-account) + I8 Schedule (24/7 monitoring + threat-hunt cycles)
Physical AI hooks	Microsoft Defender for Business agents on endpoints (cross-platform via Microsoft toolchain) — physical embodied agents
Company lens	Per-MSP-client: SMB tier (Defender for Business) vs Enterprise tier (Defender for Endpoint extension) vs compliance-driven verticals (HIPAA / financial / regulated)
Capabilities	Detection (behavioral analytics + threat intelligence) + Investigation (alert triage + context enrichment) + Threat hunting (proactive search) + Incident response (containment + remediation via RMM dispatch) + Reporting (executive + client + compliance)
Mission categories	`mission.mdr.ingest.v1` + `triage.v1` + `hunt.v1` + `respond.v1` + `report.v1` + `hunt-team.v1` (Problem-Solving for complex) — 6 categories per doc 37 F244
MDR → RMM dispatch patterns (6)	Isolate endpoint + Quarantine file + Patch vulnerability + Force password reset + Policy enforce + (password rotation per doc 39 F259)
Cross-cuts	val-cargo (Microsoft Graph API security endpoints) + val-orchestrator (MDR Missions) + val-policy (autonomy gates) + RMM (dispatch endpoint actions per doc 37 F245 + F259) + SIEM cross-correlation (per doc 37 F246) + Problem-Solving (complex incident analysis) + val-track (alert tickets)
Reference	doc 37

Identity + Credentials

Password Management / Vault (Vaultwarden + Bitwarden Server integrate-with)

Dimension	Detail
Vertical integration ID	L8.10
Interfaces used	I6 Operator (human + agent + system-account) + I7 Document (vault entry metadata) + I8 Schedule (rotation cadence) + I2 Asset (credential = software asset)
Physical AI hooks	n/a (purely software / virtual) — except where credentials grant access to physical assets (PLCs / robots / network gear / vehicle hardware) which then cross-cut to RMM + IoT
Company lens	Per-client: SBR finance-team password discipline vs MSP technician-shared credentials vs healthcare per-patient-credential vs manufacturing OT-credential isolation
Capabilities	Per-client vault provisioning + Password rotation policy + Audit (weak / reused / breached per Have I Been Pwned) + Rotation execution + Recovery (Emergency Access) + Reporting + 2FA management + Cross-cut with Azure AD SSO
Mission categories	`mission.password.provision.v1` + `rotation-policy.v1` + `audit.v1` + `rotate.v1` + `report.v1` + `recovery.v1` — 6 categories per doc 39 F258
Cross-cuts	val-cargo (Bitwarden API) + val-grid (Azure AD SSO sync) + MDR (credential-compromise rotation per doc 39 F259 — 6th MDR dispatch pattern) + val-policy (per-tenant capability + autonomy gates) + val-ledger (audit chain)
Two secrets surfaces	OpenBao (ValOS infrastructure per CLAUDE.md) + Bitwarden/Vaultwarden (client-facing per doc 39) — distinct concerns
Reference	doc 39

Identity / SSO / Conditional Access (Azure AD + val-grid)

Dimension	Detail
Vertical integration ID	L8.9 + L9.5
Interfaces used	I6 Operator (all subtypes; identity is the cross-cutting layer) + I3 Site (per-tenant scope)
Physical AI hooks	n/a (virtual) — but credential-bearing devices (smart cards / hardware tokens / biometric scanners / mobile MFA) connect Identity to I2 Asset
Company lens	Per-deployment + per-client: Microsoft-stack-aligned tenant (Microsoft 365 + Entra) vs non-Microsoft (Google Workspace / Okta / custom)
Capabilities	SSO + MFA + Conditional Access policies + Role + Group management + Per-tenant Azure AD app registration + Token exchange
Cross-cuts	val-grid (CA + node enrollment per PLATFORM.md row 12) + val-cargo (Graph API per ADR-009) + val-policy (capability binding extends with ABAC per doc 40 F269 + R276) + Microsoft-stack alignment (per doc 38 F251)
Reference	doc 25 F167 + doc 38 F251

Operations + Work-Tracking

PSA / Ticketing / Client Management (ValOS native; informed by Alga PSA)

Dimension	Detail
Vertical integration ID	L8.6 + L3.12 (val-track engine)
Interfaces used	I5 Engagement (MSP-ticket / project / agreement / sales-deal) + I6 Operator (technician + manager + client + system-account) + I7 Document (ticket descriptions + comments + agreements) + I8 Schedule (cycles + sprints + SLA windows) + I2 Asset (assets per client)
Physical AI hooks	n/a (digital operations layer; assets it tracks may have physical-AI dimensions but PSA itself is digital)
Company lens	Per-MSP-client: SBR debt-recovery cases vs New Era IT (AU) MSP tickets vs manufacturing-vertical work-orders vs healthcare patient-management
Capabilities	Ticket lifecycle + Time tracking + Billing/invoicing + Asset management + Contract/agreement management + SLA enforcement + Multi-portal (MSP + Client) + Workflow automation + RBAC/ABAC
Mission categories	`mission.psa.ticket.v1` + `time.v1` + `bill.v1` (Business Central handoff) + `asset.v1` + `agreement.v1` + `report.v1` — 6 categories per doc 40 F265
8-entity model (per Alga PSA borrow)	Ticket + Company + Contact + Asset + Agreement + Time Entry + (Mission/Initiative) + (User) — entity convergence per doc 40 F266
Cross-cuts	val-track (work-tracking core per doc 30) + Business Central (billing/invoicing per doc 38 + M5) + val-policy ABAC extension (per doc 40 F269 + R276) + Hocuspocus (collaboration on tickets) + val-desk OpsCenter (MSP portal) + Client portal extension (per doc 40 F270 + R277)
Reference	doc 40 + doc 30 + doc 38

Work-Tracking (val-track first-party engine)

Dimension	Detail
Vertical integration ID	L3.12 + L8.6 sub-component
Interfaces used	I5 Engagement (sub-types: story + epic + task + sub-task hierarchy) + I6 Operator + I8 Schedule (cycles + sprints + due-dates)
Physical AI hooks	n/a (virtual; work items represent operational orchestration not physical objects)
Company lens	Per-client: SBR collection-case tracking vs MSP ticket tracking vs manufacturing job tracking vs marketing-campaign tracking vs Problem-Solving Mission tracking
Capabilities	Linear-equivalent 11 semantic categories: work items + statuses + assignees + cycles + projects + roadmaps + custom fields + filters + comments + code integration + external bridging
Vocabulary lock	Work items < Initiatives (= Missions) < Roadmap (per doc 30 R185 + ADR-007 R171)
Cross-cuts	val-orchestrator (Missions create val-track items) + MDR / RMM / Backup / Password rotation auto-tickets + PSA superset + Hocuspocus (real-time collaboration) + val-desk OpsCenter val-track mode
Reference	doc 30 + milestone M7

Documentation + Knowledge

Documentation (val-ontology LLMWiki + Cores)

Dimension	Detail
Vertical integration ID	L8.11
Interfaces used	I7 Document (all subtypes — PDF / DOCX / transcribed-audio / scraped-web / markdown / structured) + I5 Engagement (per-client docs) + I6 Operator (author + reviewer)
Physical AI hooks	Document scanners + OCR pipelines + audio recording hardware + camera-based document capture — cross-cuts I2 Asset and I7 Document
Company lens	Per-client: SBR debtor case documents vs MSP runbooks + client documentation (IT Glue replacement) vs healthcare patient records (compliance-driven) vs manufacturing SOPs
Capabilities	Authoring (Tiptap + Hocuspocus collaborative) + Ingestion (val-ingest 3 modes) + Search (val-ontology hybrid retrieval per doc 1) + Versioning (coral growth) + Access control (val-policy capability binding) + Multi-channel rendering (val-block-renderer) + Per-client bundling (Cores)
Mission categories	val-ingest 3 extraction modes + LLMWiki accretion + Hydrator (per doc 32 F203) + Background-curation (Synthesis + Deconfliction + Validation + Tagging per doc 32 F202)
Cross-cuts	val-ingest (ADR-017) + val-ontology LLMWiki + Cores (knowledge-nodes per doc 32 F210) + val-editor (authoring per ADR-023) + val-block-renderer (rendering per ADR-010) + val-policy (capability)
Reference	doc 25 F167 + doc 32

Patching + Maintenance

Patch Management (val-grid + val-orchestrator)

Dimension	Detail
Vertical integration ID	L8.7
Interfaces used	I2 Asset (Endpoint + Server + Network gear) + I8 Schedule (patch windows) + I3 Site (per-client patch scope)
Physical AI hooks	Embodied agent on every patched endpoint — same Rust agent as RMM (cross-cuts L2.6 + L8.2)
Company lens	Per-MSP-client: SBR low-touch (managed-laptop only) vs New Era IT MSP fleet (full patch automation) vs manufacturing OT (patch-window-coordinated with production shutdowns) vs healthcare (compliance-coordinated)
Capabilities	OS patch scheduling + Application patches (via Chocolatey / apt / Homebrew) + Patch verification + Rollback + Compliance reporting + CVE matching
Mission categories	`mission.patch.apply.v1` + `verify.v1` + `rollback.v1` + `report.v1` + `cve-match.v1`
Cross-cuts	val-grid (endpoint inventory) + val-orchestrator (scheduling) + val-policy (autonomy gates for production-critical patches) + RMM cross-cut + Problem-Solving (complex patch failure analysis)
Reference	doc 25 F167 + ADR-012

Compliance + Quality

QMS — Quality Management System (base blueprint)

Dimension	Detail
Vertical integration ID	L7.2 (base blueprint)
Interfaces used	All 8 — I1 WorkSpace (Factory / Office) + I2 Asset (Robot / PLC / Camera / Manufacturing equipment / Sensor) + I3 Site (Customer-site / Field-installation) + I4 Conversation (complaint intake) + I5 Engagement (audit / NCR / CAPA cases) + I6 Operator (auditor + technician + manager) + I7 Document (procedures / records / audits) + I8 Schedule (audit cycles + review cadence)
Physical AI hooks	Substantial — Manufacturing equipment + PLCs + Robots + Cameras + Quality-control sensors + Inspection robots + Vibration monitors + Temperature sensors + Vision systems
Company lens	8 verticals — Manufacturing + Construction + Healthcare + Food-safety + Medical-devices + Pharma + Financial-services + IT-services (per doc 29 F175)
Capabilities (8 surface areas per doc 29 F174)	Document control (auto-version + approval) + Training tracker + NCR + CAPA register + ISO 9001 audit + Risk + FMEA + Supplier management (peer-scorecards) + Complaints + Change management
Compliance frameworks	ISO 9001 + IATF 16949 + ISO 13485 + ISO 45001 + HACCP + GxP + FDA 21 CFR Part 11 + Australian Privacy Act 1988 (per doc 29 R178 + doc 2 §10 F11)
Cross-cuts	val-ontology (entities + scenarios per ADR-015) + val-policy (ABAC for compliance) + Problem-Solving (complex root-cause per doc 34 F222) + Engagement Wizard (QMS onboarding per ADR-013) + adversarial validation (audit per doc 19) + Hocuspocus (collaborative document review) + Microsoft-stack (Business Central supplier master + Sites)
Mission categories	NCR investigation + CAPA execution + Audit cycle + Risk assessment + FMEA RPN calculation (Computes capability per doc 33 R210) + Supplier scoring + Change impact assessment + Document approval
Reference	doc 29 + ADR-013 + milestone M11.5-M11.7

Operations Intelligence

Problem-Solving (base blueprint — cross-vertical)

Dimension	Detail
Vertical integration ID	L7.1
Interfaces used	I5 Engagement (problem-case) + I6 Operator (problem-framing operator + critique-team agents + plan-team agents) + I7 Document (research + plans + reports) + I8 Schedule (annealment cycles + plan delivery deadlines) + optionally I1 WorkSpace + I2 Asset + I3 Site (depending on problem domain)
Physical AI hooks	Conditional — field-investigation problems may use physical agents (drones / cameras / on-site assessment); cross-vertical so depends on engagement type
Company lens	Universal — applies across all verticals (per doc 34 F222): military planning + engineering troubleshooting + investment decisions + business strategy + R&D + QMS NCR root cause + customer-issue resolution + emergency response + Backup/DR scenarios + MDR complex incident response
Capabilities (6 stages per doc 34 F223)	Problem framing + Idea generation (parallel agents) + Per-idea critique team (dynamic Worker roles per doc 34 F226 + ADR-007 R218) + Annealment loop (V1→V2→V3 per doc 34 F225) + Idea-to-plan promotion + Plan-team Mission + Execution handoff (val-forge AI panel)
Three-tier knowledge accretion	b_facts (per-Mission) + knowledge-nodes (per-engagement synthesized insights per doc 32 F210) + Engagement Core bundle (whole engagement)
Cross-cuts	val-orchestrator (Mission decomposition) + val-bay (LLM dispatch) + val-policy (autonomy gates) + Adversarial validation per doc 19 + Heartbeat watchdog per ADR-020 + Compounding knowledge per ADR-019
Mission categories	Frame + Ideate + Critique + Anneal + Plan + Execute
Reference	doc 34 + ADR-007 dynamic-Worker variant + milestone M11.1-M11.4

System of Record + Financial

Business Central as ValOS SoR

Dimension	Detail
Vertical integration ID	L8.14 + L9.1
Interfaces used	I5 Engagement (sales-deal + service-contract + project) + I6 Operator (sales + finance + customer) + I7 Document (invoices + agreements + statements) + I8 Schedule (invoicing cycles + payment terms) + I2 Asset (product / inventory item)
Physical AI hooks	n/a (financial/transactional SoR; physical inventory tracked but not embodied)
Company lens	Per-deployment + per-client: SBR collection-revenue tracking vs MSP recurring-service billing vs manufacturing inventory-and-invoicing vs healthcare per-patient billing vs SMB tier (Business Central Essentials) vs Premium tier (Premium) vs Enterprise extension
Capabilities	Financial GL + Sales orders + Invoices + Inventory + Vendor master + Customer master + Multi-currency + Multi-company + Project accounting
Integration patterns (3 per doc 38 F250)	Entity reference + b_fact emission with BC refs + Cache+sync
val-cargo skills (3)	`bc.read.v1` + `bc.write.v1` + `bc.query.v1`
Cross-cuts	val-cargo (Graph API + REST/OData per ADR-009) + val-ontology (entities reference bc_id) + val-ledger (b_facts with BC transaction refs) + val-policy (Builds capability for writes) + per-tenant OAuth via val-grid + cross-cuts every revenue-generating vertical integration (PSA + Backup billing + MDR per-incident billing + RMM per-endpoint pricing)
Reference	doc 38 + ADR-009 + milestone M5

Mission Control + Onboarding (val-up + val-forge multi-repo)

val-up — Mission Control Engine + Engagement Wizard Runtime (per ADR-024)

Dimension	Detail
Vertical integration ID	L3.19 (per fusion checklist)
Interfaces used	I5 Engagement (every client onboarding case + per-tenant Decision Cards) + I6 Operator (Valtience operator-team + per-client operator-team + client-side reviewer roles) + I7 Document (5 MC docs + Decision Card YAML files + Engagement Wizard intake forms) + I8 Schedule (per-engagement onboarding cadence + Engagement Wizard 7-phase timing)
Physical AI hooks	n/a directly (val-up is web-based SaaS); cross-cuts physical AI via Engagement Wizard Phase 2 substrate provisioning (val-grid endpoint rollout per ADR-012)
Company lens variants	Cross-vertical: every ValOS client engagement runs through val-up. Valtience operator-team tenant (Mission Control superset access) + per-client tenants (scoped onboarding access; e.g., SBR tenant + New Era IT tenant + future-client tenants)
Capabilities	Mission Control 5-doc interactive browser + per-tenant Decision Card ledger + ADE Factory pipeline-branch spawn dispatch + Engagement Wizard runtime (7 phases) + 5-level maturity progression + per-tenant institutional knowledge accretion + Microsoft Entra OAuth multi-tenant + ABAC isolation
Mission categories	`up.decision.draft.v1` + `up.milestone.advance.v1` + `up.intake.triage.v1` + `up.pipeline.spawn.v1` + `up.pause-point.verify.v1` + `up.wizard.phase.advance.v1`
Cross-cuts	All 4 prior MC docs (vertical-fusion-checklist + milestones-manifesto + fusion-layer-integration-matrix + mission-control-operating-protocol) + master-decision-card-spec + ADR-013 (Wizard runtime) + ADR-019 (per-tenant Cores) + ADR-023 (Tiptap+Hocuspocus first concrete consumer) + ADR-018 (customer-acquisition cross-cut) + ADR-025 (val-forge multi-repo ADE consumer)
Reference	ADR-024; public DNS `up.valtience.com`

val-forge Multi-Repo ADE (per ADR-025)

Dimension	Detail
Vertical integration ID	L3.20 (per fusion checklist; extension of L3.14 val-forge)
Interfaces used	I3 Site (per-client repo = per-deployment site analog) + I5 Engagement (per-client repo lifecycle bound to engagement) + I6 Operator (Valtience operator-team + client-side reviewer + automated pipeline approver) + I7 Document (Decision Cards drive pipeline branches; ADRs + specs drive pipeline branches) + I8 Schedule (release cadence + per-client upgrade windows)
Physical AI hooks	n/a directly (val-forge is software orchestration); cross-cuts physical AI via per-client repo's blueprint output (which may include endpoint provisioning / device management / OT integration per per-vertical scope)
Company lens variants	Per-tenant + per-deployment: dev-workspace (Valtience platform team) + canonical ValOS (published platform) + per-client repos (each engagement)
Capabilities	4-scope ADE routing + per-client repo lifecycle Missions + cross-repo dependency tracking (canonical → cascading client upgrades) + per-scope promoter approval + Decision Card → pipeline-branch dispatch from val-up
Mission categories	`mission.forge.repo.create.v1` + `archive.v1` + `upgrade.v1` (per-client lifecycle); standard pipeline-type Missions extended with `ade_scope` field
Cross-cuts	ADR-011 (val-forge baseline extended) + ADR-024 (val-up primary consumer) + ADR-013 (Engagement Wizard Phase 2 invokes repo creation) + ADR-019 (per-tenant Cores can include repo references) + ADR-009 (MCP server pattern between val-up and val-forge) + `CLAUDE.md` publish workflow + `project_blueprint_as_a_service.md` memory
Reference	ADR-025

Provisioning + Onboarding

Device Provisioning (val-grid + Rufus + USB sidecar)

Dimension	Detail
Vertical integration ID	L8.1 + L3.1 (val-grid)
Interfaces used	I2 Asset (new endpoint + USB sidecar + provisioning image) + I3 Site (target deployment location) + I6 Operator (technician deploying) + I8 Schedule (onboarding window)
Physical AI hooks	Substantial — physical USB stick for air-gapped provisioning + endpoint hardware + Rufus-burned bootable media + hardware tokens for code signing
Company lens	Per-MSP-client: SBR laptop provisioning vs New Era IT MSP fleet rollout vs manufacturing kiosk deployment vs healthcare medical-device onboarding vs air-gapped client environments (defense / financial / classified)
Capabilities	3 paths: Online network-reachable (mesh via MeshCentral) + USB sidecar (semi-air-gapped) + Air-gapped (full offline) + Certificate authority (val-grid CA) + Code-signing
Cross-cuts	val-grid (CA + enrollment) + RMM (agent install) + Identity (Azure AD + cert chain) + val-policy (provisioning capability)
Reference	doc 12 + ADR-012

Engagement Wizard (5-level maturity framework)

Dimension	Detail
Vertical integration ID	L7.4
Interfaces used	I5 Engagement (onboarding case) + I6 Operator (operator-team + client) + I7 Document (questionnaires + onboarding artifacts) + I8 Schedule (onboarding cadence + maturity progression)
Physical AI hooks	n/a directly (orchestration discipline); cross-cuts physical via vertical-specific onboarding (e.g., manufacturing QMS Wizard touches physical equipment)
Company lens	Per-vertical Wizard variants: SBR onboarding + MSP onboarding + QMS manufacturing onboarding + Healthcare placement Wizard + 8 known Wizard instances (per ADR-013)
Capabilities (5 maturity levels)	L0 Manual + L1 Substrate-assisted + L2 Substrate-orchestrated + L3 Substrate-autonomous + L4 Substrate-self-evolving
Wizard template (7 phases)	Scope-assessment + Substrate provisioning + Capability-baseline rollout + Integration setup + Operator + technician training + Soft-launch validation + Go-live + monitoring
Cross-cuts	val-grid (initial substrate) + Engagement Core (per-onboarding state) + val-orchestrator (Wizard primitive) + AGENTS.md autonomy gates (maturity-level autonomy progression) + Engagement Wizard (8 industry corroborations per ADR-013 R225)
Reference	ADR-013 + 8 Wizard instances

Marketing + Customer-Acquisition

Marketing Automation (base blueprint — cross-vertical)

Dimension	Detail
Vertical integration ID	L7.3
Interfaces used	I4 Conversation (multi-channel outbound + inbound) + I5 Engagement (lead → prospect → customer → advocate) + I6 Operator (lead + sales + customer) + I7 Document (content + nurture sequences + landing pages) + I8 Schedule (campaign cadence + drip sequences)
Physical AI hooks	Conditional — kiosks + signage + retail-floor cameras + IoT-enabled retail environments cross-cut marketing campaigns (especially for retail/hospitality verticals)
Company lens	Cross-vertical: B2B SaaS lead nurture vs retail email + SMS vs healthcare appointment reminders vs MSP referral programs vs SBR debt-recovery client engagement
Capabilities (8 areas per doc 18)	Lead generation + Lead nurture + Lead qualification + Customer onboarding + Customer retention + Customer advocacy + SEO + content + Video Genie
Cross-cuts	val-switch (multi-channel comms) + val-ingest (video content per doc 15 §14 + val-ingest video mode) + val-orchestrator (campaign Missions) + val-cargo (CRM integration via Business Central) + val-ledger (per-lead activity stream) + Engagement Cores (per-client campaign state) + Problem-Solving (campaign analysis)
Reference	doc 18 + ADR-018 + milestone M11.8-M11.9

Physical AI Dimension — Cross-Cut by Vertical Integration

Per IDENTITY.md §Physical AI & Fusion Hooks + PLATFORM.md §Interfaces (physical kind).

Endpoint as Physical AI subtype

Endpoint subtype	Vertical integrations consuming
Windows / macOS / Linux desktop	RMM + Backup + MDR + Password Management (SSO-aligned) + Patch Management + Device Provisioning + Documentation (operator authoring) + Voice/Comms (WebRTC client)
Server (Windows / Linux)	RMM + Backup + MDR + Patch Management + Provisioning + SIEM (host events)
Mobile (iOS / iPadOS / Android)	RMM (mobile UEM scope) + Identity (MFA) + Comms (mobile chat / SMS / WhatsApp)
ChromeOS	RMM (Chrome management) + Identity (Google or Azure SSO)
Kiosk + Signage	RMM + Patch + Marketing (retail signage campaigns) + Provisioning + Custom QMS for manufacturing-floor displays
Rugged device (Zebra / Honeywell / Panasonic Toughbook)	RMM + Patch + Provisioning + QMS (manufacturing floor-data capture)
Manufacturing portable (handheld scanner / data terminal)	RMM + QMS (real-time process data) + Backup (per-device data)
PLC / Robot / Drone / Camera / RF-sensor	QMS (process control + quality inspection) + SIEM (OT monitoring) + Problem-Solving (physical incident investigation) + Provisioning (OT device onboarding)
Vehicle hardware	Fleet ops + RMM (mobile asset) + Provisioning (vehicle onboarding)

Physical AI Capability Cross-Cut

Physical AI capability	Vertical integrations
Embodied agent dispatch (Rust cross-platform agent)	RMM + Patch + MDR + Backup (per-endpoint backup)
Sensor data ingestion	QMS + SIEM + Problem-Solving + Marketing (retail floor sensors)
OT integration (PLCs / Robots / Manufacturing equipment)	QMS + SIEM (OT scope) + Patch Management (OT-scheduled windows)
On-site provisioning (USB sidecar + air-gapped)	Device Provisioning + Identity (cert chain) + RMM agent install
Camera / Vision systems	QMS (quality inspection) + SIEM (physical security) + Marketing (retail analytics)
Field operations (vehicle-mounted + drone + remote workers)	Field_services blueprint + Fleet ops + Remote-employee comms

Company Lens Dimension — Cross-Cut by Vertical Integration

Per IDENTITY.md §The Org + §Market Reality + per-deployment + per-vertical framing.

Verticals scoped (current state + future-vertical capture-and-hold)

Vertical	Primary engagement type	Industry-specific framing
Debt-recovery-AU (SBR — v1 production)	Debt-recovery-case	AU jurisdiction + Privacy Act 1988 + court actions + trust accounting
MSP / IT services (New Era IT — future)	MSP-ticket + service-contract	Microsoft-stack-aligned + SMB/Medium Enterprise + multi-client tenant management
Manufacturing (future)	Manufacturing-job + work-order + QMS-NCR	OT/IT convergence + ISO 9001 + IATF 16949 + supplier chain
Construction (future)	Construction-project + Field-services + Sub-contractor	Job-site safety (ISO 45001) + project-phase QMS + sub-contractor scorecards
Healthcare (future)	Healthcare-placement + patient-record	HIPAA + Privacy Act + clinical training + per-patient compliance
Food-safety (future)	Food-safety-incident + ingredient + co-packer	HACCP + supplier compliance + traceability
Medical-devices (future)	Device-recall + 510(k) + design-control	ISO 13485 + FDA 21 CFR Part 11 + design-history-file
Pharma (future)	Batch-record + audit + GxP	GMP/GDP/GLP + FDA + batch-coordinated audits
Financial-services (future)	Compliance-program + control-deficiency	SOX + ISO 27001 + financial regulator alignment
Legal (future)	Legal-matter + client-matter	Privilege + matter-management + court-deadlines

Operator-team variants by company lens

Operator role	Vertical-specific framing
Operator (per IDENTITY.md primary user)	Per-deployment — founder + owner + GM driving daily
Technician / Analyst	MSP technician (RMM) + SBR collection-specialist + manufacturing-quality-engineer + healthcare-clinician
Manager	MSP account-manager + SBR debt-collection-team-lead + manufacturing-operations-manager
Customer / Client	SBR client (debt-issuer) + MSP client (managed-IT customer) + manufacturing-client + healthcare-patient/provider
External-user (per I6 Operator subtype)	Auditor + Government regulator + Partner + Sub-contractor

Capabilities Dimension — Cross-Cut by Vertical Integration

Per AGENTS.md autonomy gates + val-policy capability binding (Reads / Builds / Grows / Evolves / Computes per doc 33 R210).

Capability shapes by vertical integration

Capability shape	Vertical integrations
Reads (query-only; low-stakes)	Documentation (LLMWiki search) + SIEM (alert query) + RMM (endpoint inventory query) + Business Central (bc.read.v1)
Builds (create + non-destructive write)	PSA (ticket creation) + val-track (work-item creation) + Marketing (campaign authoring) + QMS (document drafting) + Documentation (markdown authoring) + Business Central (bc.write.v1)
Grows (additive expansion — coral growth pattern)	Knowledge-node accretion + skill registry growth + Engagement Core versioning + Ring 3 blueprint additions
Evolves (refactor + supersede + retire)	Blueprint promotion / retirement + skill supersession + ADR locks
Computes (per doc 33 R210; 5th capability)	RPN calculation (QMS FMEA) + months-of-runway (financial) + utilization rate (PSA) + dedup analysis (Backup) + Wilson-score confidence (Mission promotion) + entity resolution (SBR debtor reconciliation) + custom script execution (RMM scripts)
ABAC extension (per doc 40 F269 + R276)	Per-tenant access control (PSA + Backup + MDR + Password + all multi-tenant verticals)

OODA scale cross-cut (per SOUL.md mindset + PLATFORM.md Pulse Lifecycle)

OODA scale	Vertical integrations
Tick (sub-millisecond — fast firehose orient)	SIEM event ingestion + RMM heartbeat + Voice call-event tick
Watcher (anomaly detection — continuous JetStream watch)	SIEM correlation + MDR detection + RMM anomaly + Backup failure detection
Pulse (per-interaction — operator chat / button / trigger)	Operator-initiated Mission + Skill dispatch + Approval gates
Genie (multi-step Mission — long-horizon workflow)	Problem-Solving multi-agent annealment + QMS audit + MDR threat-hunt + Engagement Core lifecycle
Value-engine (cross-engagement value optimization)	Marketing campaign value chains + PSA value tracking + Per-engagement profitability + Cross-engagement learning loop

Reverse Map — Per-Interface, What Uses It

I1 WorkSpace (physical)

Concrete subtypes: Factory · Office · Vehicle · Greenfield · Field site · Remote work-from-home

Vertical integrations using I1:

QMS (factory + workshop)
Field_services blueprint
Marketing (retail signage + kiosks)
Provisioning (per-site rollout)
RMM (per-site endpoint inventory)

I2 Asset (physical)

Concrete subtypes: Robot · Camera · PLC · Drone · RF-sensor · Endpoint (cross-platform) · Server · Network gear · Kiosk · Signage · Rugged · Manufacturing portable · IoT · Vehicle hardware

Vertical integrations using I2:

RMM / UEM / MDM (every endpoint)
Backup (per-asset data)
MDR (endpoint asset)
Patch Management (every patchable asset)
SIEM (asset log source)
Provisioning (every new asset)
QMS (manufacturing assets)
VPS / DNS / Hosting (server + DNS + certificate as assets)
Marketing (retail kiosk + signage)

I3 Site (physical)

Concrete subtypes: HQ · Branch · Customer-site · Field-installation · Data center · Co-located rack · Edge location

Vertical integrations using I3:

RMM (per-site endpoint scope)
MDR (per-tenant per-site scope)
VPS / DNS / Hosting (Data center + Edge)
Provisioning (target site)
Backup (repository location)
QMS (per-facility scope)
Field_services (job-site)

I4 Conversation (virtual)

Concrete subtypes: email · Teams · SMS · voice · webchat · WhatsApp · Instagram · Facebook · Telegram · Signal · in-app chat

Vertical integrations using I4:

Voice / Comms (every channel)
Marketing (multi-channel outbound + inbound)
MDR alerting (email/SMS/webhook)
RMM alerting (email/SMS/webhook)
Backup failure alerts (email/SMS)
val-track collaboration (in-app comments)
PSA client communications (email + Teams)
QMS complaint intake (multi-channel)
Problem-Solving operator-team coordination

I5 Engagement (virtual)

Concrete subtypes: legal-matter · healthcare-placement · MSP-ticket · sales-deal · debt-recovery-case · construction-project · manufacturing-job · service-contract · investment-decision · DR-incident · marketing-campaign

Vertical integrations using I5:

PSA (MSP-ticket + service-contract)
val-track (every Engagement subtype maps to work-item)
Engagement Core (per-engagement substrate state per ADR-019)
Engagement Wizard (per-engagement onboarding)
Legacy Modernization Mission (per-engagement migration)
Problem-Solving (per-case)
Marketing (campaign-as-engagement)
QMS (NCR + audit + CAPA cases)
Business Central (sales-deal + service-contract + project)

I6 Operator (virtual)

Concrete subtypes: human · agent (val-agent / val-orchestrator) · role (technician / manager / executive) · system-account · service-account · external-user

Vertical integrations using I6:

ALL vertical integrations (Operator is the cross-cutting layer)
Password Management (per-Operator vault)
Identity / SSO (per-Operator authentication)
val-policy (per-Operator capability binding)
val-desk (per-Operator UI surface)
Engagement Wizard (per-Operator maturity progression)

I7 Document (virtual)

Concrete subtypes: PDF · DOCX · transcribed-audio · scraped-web · markdown · structured-data · spreadsheet · presentation · image-with-OCR · video-with-transcript

Vertical integrations using I7:

Documentation (LLMWiki + Cores per ADR-019)
val-ingest (every document subtype ingestion)
QMS (document control)
PSA (ticket descriptions + agreements)
val-block-renderer (rendering target)
val-editor (authoring source)
Marketing (content assets)
Voice/Comms (call recordings as documents)
SIEM (logs as documents)

I8 Schedule (virtual)

Concrete subtypes: appointment · shift · delivery · maintenance-window · backup-window · patch-window · audit-cycle · invoicing-cycle · sprint · cycle · recurring-task

Vertical integrations using I8:

Backup (backup windows + retention)
Patch Management (patch windows)
QMS (audit cycles + review cadence)
val-track (cycles + sprints)
PSA (SLA windows)
Marketing (campaign cadence)
MDR (24/7 monitoring + threat-hunt cycles)
Voice/Comms (call-back scheduling)
Business Central (invoicing cycles)
Engagement Wizard (onboarding cadence)

Fusion Layer Examples — Same Logic Across Many Subtypes

Concrete demonstrations of the fusion layer in action:

Example 1: "Schedule a maintenance window" — runs across many concrete subtypes via I8 Schedule

Backup engine schedules backup window for client laptop (RMM cross-cut)
Patch Management schedules OS patch window for manufacturing PLC (cross-cut to OT)
val-orchestrator schedules audit cycle for QMS NCR review
Marketing schedules drip-sequence delivery for sales-deal nurture
PSA schedules SLA breach review cycle
Voice/Comms schedules call-back appointment

Same logic (schedule + verify + execute + report); many subtypes (Backup window, Patch window, Audit cycle, Marketing cadence, SLA review, Call-back appointment); one Mission template dispatches across all.

Example 2: "Alert on anomaly" — runs across many concrete subtypes via I2 Asset + I4 Conversation

MDR alerts on Defender detection → email + SMS + webhook
SIEM alerts on Wazuh correlation → same channels
RMM alerts on monitoring threshold → same channels
Backup alerts on failure → same channels
QMS alerts on NCR severity → same channels

Same logic (detect → triage → notify → log); many subtypes (Defender alert + Wazuh correlation + RMM threshold + Backup failure + NCR detection); one alerting Mission per val-switch channel.

Example 3: "Onboard a new asset" — runs across many concrete subtypes via I2 Asset + I3 Site + I6 Operator

Provisioning onboards new laptop (val-grid + Rufus)
RMM onboards new server (cross-platform Rust agent)
QMS onboards new manufacturing PLC (OT discovery)
val-host onboards new VPS server
Identity onboards new operator (Azure AD)
Password Management onboards new vault for new client
PSA onboards new client engagement

Same logic (inventory → policy → provision → verify); many subtypes (laptop + server + PLC + VPS + operator-identity + vault + client-engagement); one Engagement Wizard template with per-subtype variants.

Example 4: "Compute a derived metric" — runs across many concrete subtypes via Computes capability (per doc 33 R210)

QMS computes Risk Priority Number (severity × probability × detectability)
PSA computes utilization rate (billable / total hours)
Backup computes deduplication ratio
val-track computes cycle burnup
Financial computes months-of-runway (per doc 28 F170)
Mission promotion computes Wilson-score confidence (per doc 27 F158)
Entity resolution computes canonical-entity matching score

Same logic (read source b_facts → apply formula → emit derived b_fact); many subtypes (RPN + utilization + dedup + burnup + runway + Wilson-score + matching score); one Computes capability gates dispatch.

Example 5: "Resolve duplicate entities" — runs across many concrete subtypes via val-ontology entity resolution (per doc 33 R212)

Resolve duplicate debtor records (SBR)
Resolve duplicate equipment records (manufacturing maintenance)
Resolve duplicate customer records (Business Central + RMM Client cross-cut)
Resolve duplicate Asset records (RMM endpoint convergence with PSA asset)
Resolve duplicate contact records (across Conversation subtypes)

Same logic (multi-source records → derived-property chain → canonical entity); many subtypes (Debtor + Equipment + Customer + Asset + Contact); one Mission category (mission.resolution.v1).

Integration Density Heatmap

Per vertical integration × interface density (which interfaces each integration touches):

Integration	I1 WorkSpace	I2 Asset	I3 Site	I4 Conversation	I5 Engagement	I6 Operator	I7 Document	I8 Schedule	Total Interfaces
QMS (base blueprint)	✓	✓	✓	✓	✓	✓	✓	✓	8 (highest density)
Problem-Solving (base)	△	△	△		✓	✓	✓	✓	4 (+ 3 conditional)
PSA / Ticketing		✓			✓	✓	✓	✓	5
RMM / UEM / MDM		✓	✓			✓		✓	4
MDR		✓				✓	✓	✓	4
Marketing Automation	△			✓	✓	✓	✓	✓	5 (+ 1 conditional)
SIEM		✓					✓	✓	3
Backup		✓	✓				✓	✓	4
Password Management		✓				✓	✓	✓	4
Voice / Comms				✓		✓		✓	3
VPS / DNS / Hosting		✓	✓					✓	3
Patch Management		✓	✓					✓	3
Documentation					✓	✓	✓		3
Business Central SoR		✓			✓	✓	✓	✓	5
Provisioning (val-grid)		✓	✓			✓		✓	4
Engagement Wizard					✓	✓	✓	✓	4

Legend: ✓ direct usage · △ conditional usage (depends on engagement type)

Highest density vertical integration: QMS (8 interfaces — all of them). Confirms QMS as the most-cross-cutting base blueprint at substrate scope.

Universal interfaces (used by 8+ vertical integrations): I2 Asset (12) + I6 Operator (all 16) + I8 Schedule (11). These are the fusion-layer anchors — most cross-cutting interfaces.

How to Use This Matrix

For planning vertical-integration scoping

Pick vertical integration to scope (e.g., RMM, PSA, Backup)
Identify interfaces it uses (look up row)
Identify physical AI hooks + company lens variants + capabilities
Cross-reference fusion-checklist Layer N for current state
Cross-reference milestones-manifesto Milestone M for forward-build sequencing

For prospect/customer conversations

Prospect asks "Does ValOS do X?"
Look up X in matrix
Identify: capabilities + interfaces + company lens variants
Articulate: ValOS does X via interfaces I and J, applicable across verticals A, B, C, with capabilities P, Q, R

For architectural decisions

New vertical integration proposed
Map to interfaces it would use
Check if interfaces have concrete subtypes already (composition with existing)
Identify cross-cuts with existing integrations
Sub-types add to existing concrete-subtype list (coral growth)

For Problem-Solving Missions

Problem-Solving Mission instantiates dynamic Worker roles per problem context
Worker roles drawn from interfaces involved (e.g., problem touching I2 Asset → endpoint specialist; problem touching I5 Engagement → engagement specialist)
Same Mission template + same Worker dispatch pattern + different concrete subtypes per problem

Cross-Pipeline References

This matrix references:

40 research docs (2026-05-11 pipeline; all 5 batches)
16 ADRs (2026-05-12)
vertical-fusion-checklist.md (current-state inventory — Layer-by-layer)
milestones-manifesto.md (forward-build sequencing — 13 milestones × ~110 sub-milestones)
PLATFORM.md (Ontology System §Interfaces + Pulse Lifecycle + Five Rings)
IDENTITY.md (per-deployment lens — The Org + Physical AI scope + Hardware/Edge + Systems of Record table)
SOUL.md (architectural law + Mindsets — including #6 OODA + #7 Checklist Manifesto)
AGENTS.md (Caveman Tiers + Autonomy Gates + Surface-Specific Tone)
CLAUDE.md (Cowork dev rules + ARCH-165 markdown-view-layer)
valos-reference.md (engine + capability + vocabulary register)
rules/architecture-layers.md + rules/fact-taxonomy.md + rules/ooda-pattern.md
policies/model-stack.md + policies/voice-substrate.md

Companion Documents Summary

Three docs work together as the ValOS Cowork-side build tracker:

Doc	Axis	Lens
vertical-fusion-checklist.md	Current state	Layered inventory (16 layers, status per item)
milestones-manifesto.md	Forward build	Sequenced milestones (13 milestones × ~110 sub-milestones × 13 pause points)
fusion-layer-integration-matrix.md (this doc)	Cross-cutting	Interfaces × Physical AI × Company Lens × Capabilities

Use together: pick vertical integration → look up current state (checklist) → trace forward-build milestone (manifesto) → understand cross-cutting connections (this matrix).

Fusion-Layer Integration Matrix — Cowork-side composition. Connects vertical-fusion-checklist (current state) + milestones-manifesto (forward-build) to the actual fusion layer (PLATFORM.md Interfaces). The fusion is in the cross-reference: same logic across many concrete subtypes via interfaces. Public, versioned, wrong until proven right. 2026-05-12.