Abstract
This paper presents the first applied reference validation of the Vertical AI Governance Stack v1.0 — Implementation Conformance Checklist against an active, AI-enabled production architecture: the PrintPriceOS Control Plane (@ppos/control-plane v1.9.5). The assessment evaluated what the deployed system can actually make happen across interactive, asynchronous, and legacy execution paths rather than what architectural documentation claims should happen. Operating strictly in a read-only / audit-first mode, the assessment applied Layer 1–6 controls to an execution surface inventory of 82 operational paths and 5 autonomous background daemons. The framework independently rediscovered previously documented critical governance bypasses and identified additional, previously undocumented governance weaknesses without confirmed false positives during this assessment. Crucially, the validation exercise exposed fundamental framework blind spots—most notably the omission of asynchronous daemons as governed execution principals—leading to the formulation of three candidate refinements for v1.1. PrintPriceOS Control Plane is qualified as a Partial Reference Implementation, demonstrating state-of-the-art governance design in financial production activation and schema compatibility gating while retaining documented governance coverage gaps.
1. Methodological Principle
A fundamental rule governs the integrity of this validation study:
Framework v1.0 was frozen prior to commencing the applied assessment. The Control Plane assessment was performed strictly against that frozen specification. Only after the assessment was completed were candidate refinements for v1.1 identified, formulated, and documented.
The framework was not retroactively modified to fit the observed characteristics of the target codebase. Preserving strict separation between the evaluated framework (v1.0), the empirical findings, and candidate v1.1 refinements is essential to maintaining scientific rigor and avoiding confirmation bias.
2. Research Questions
This study addresses a primary research question:
Primary RQ: Can the Vertical AI Governance Stack v1.0 identify material governance defects in an existing AI-enabled operational architecture without being tailored to that architecture?
Four secondary research questions were evaluated:
- SRQ1: Can the framework detect governance vulnerabilities outside synchronous HTTP request-response paths (e.g. in background workers, daemons, and schedulers)?
- SRQ2: Can the framework distinguish between authority failures, identity spoofing, execution parameter tampering, and audit evidence deficits?
- SRQ3: Can the framework produce actionable diagnostic findings without relying on aggregate numerical scoring?
- SRQ4: Where does the governance framework itself reveal structural blind spots or require candidate refinements?
3. Assessment Scope
The target system evaluated in this case study is the PrintPriceOS Control Plane (@ppos/control-plane v1.9.5), a multi-tenant, multi-region industrial print manufacturing platform. The Control Plane acts as the central coordinator for order intake, preflight verification, inverse price solving, governed routing, factory dispatching, and financial settlement.
The operational surface inventory mapped 82 execution paths across:
- Intake & Public Gateways: Order intake (
POST /api/marketplace/orders), connector heartbeats, and status updates. - Live Quote & Pricing Solvers: Real-time inverse pricing solvers and quote eligibility endpoints.
- Governed Routing & Dispatch Engines: Printhouse eligibility evaluation, routing decision commitment, and production dispatching.
- Administrative Operations: Onboarding review, shipping configuration, and financial production activation (
/api/admin/financials/activation/approve). - Autonomous & Background Daemons: 5 background loops (
autonomousOrchestrator), including automated job assignment, SLA monitoring, capacity conflict detection, and automated rerouting. - Routing Infrastructure: Fastify HTTP gateway with Express middleware bridge.
4. Methodology
The assessment followed an 11-step methodology:
- Framework Freeze: Freeze Canonical Specification v1.0 and Checklist v1.0.
- Boundary Mapping: Map total operational surface of deployed Control Plane codebase.
- Execution Surface Inventory: Build
CONTROL_PLANE_EXECUTION_SURFACE.mdrecording entry points, principals, services, operations, side-effects, enforcement points, audit evidence, and fallback behaviors for all 82 paths. - Layer Controls Audit: Apply Layer 1 through Layer 6 controls.
- Proof Obligations Evaluation: Test representative workflows against 7 Proof Obligations.
- Capability Drift Analysis: Compare declared operational authority against effective executable authority.
- Execution Drift Analysis: Evaluate whether authorized operational intent matches actual downstream side-effects.
- Coverage Gap Identification: Classify side-effecting paths operating outside declared enforcement architecture as
GOVERNANCE_COVERAGE_GAP. - Negative Verification: Perform safe local negative tests without altering production data.
- Historical Blind Comparison: Compare independent results against historical repository audit logs only after assessment completion.
- Refinement Extraction: Formulate candidate refinements for v1.1.
Methodological Constraint: No aggregate governance percentage score was used. Summarizing complex architectural governance with a single percentage score masks critical single-point vulnerabilities.
5. Assessment Taxonomy
Evaluated controls were assigned one of five canonical conformance states: CONFORMANT, PARTIALLY CONFORMANT, NON-CONFORMANT, NOT VERIFIED, or NOT APPLICABLE. Findings severity was classified as CRITICAL, HIGH, MEDIUM, LOW, or OBSERVATION.
6. Key Assessment Findings
The assessment identified 17 distinct governance findings. Five key findings include:
Middleware in printhouseShippingRoutes.js and runtimeOperationsRoutes.js checks req.headers['x-user-role'] when req.user is unpopulated. An unauthenticated external client can pass X-User-Role: SUPER_ADMIN to gain administrative access without a valid JWT. (Violates Identity O2, Authority O1, Scope O3).
Background loops in autonomousOrchestrator.js execute every 30–90 seconds, automatically mutating job assignments and rerouting orders in manufacturing_dispatches without passing through a Capability Verification Adapter (CVA). (Violates Authority O1, Scope O3, Evidence O5).
Governed routing and dispatch endpoints accept client-controlled actorId and tenantId directly from request JSON bodies without binding them to authenticated req.user token claims. (Violates Identity O2, Scope O3, Outcome O6).
Helper functions default missing tenant IDs to 'ph-tenant-default' and missing roles to 'PRINTHOUSE_ADMIN'. Violates the invariant: Uncertainty must reduce authority, not expand it.
Fastify onRequest hook excludes /api/admin from central JWT auth to delegate to Express, but sub-routes mounted without secondary middleware remain unauthenticated. Principle: Governance invariants MUST survive transport, framework, and runtime boundaries.
7. Rediscovered vs. Newly Discovered Findings
Findings were compared against historical repository audit records after assessment completion:
| Finding ID | Finding Title | Discovery Classification | Historical Note Ref |
|---|---|---|---|
FINDING-001 |
Header-Based Identity Trust Failure | Independently Rediscovered | task.md (Phase 38.8) |
FINDING-002 |
Asynchronous CVA Bypass in Background Loops | Independently Rediscovered | CHANGELOG_PHASE10 |
FINDING-003 |
Untrusted Principal / Scope Binding | Newly Discovered | Not previously documented |
FINDING-004 |
Cross-Runtime Fastify/Express Bypass | Independently Rediscovered | server.js (Phase 184) |
FINDING-005 |
Privileged Default Escalation | Independently Rediscovered | PHASE_39_0_NOTES.md |
FINDING-006 |
Hardcoded Email Escalation | Newly Discovered | Not previously documented |
8. Governance Proof Obligations Evaluation
Representative operational workflows were evaluated against the 7 Proof Obligations:
| Workflow | O1 Auth | O2 Ident | O3 Scope | O4 Integ | O5 Evid | O6 Outc | O7 Recov | Workflow Gate |
|---|---|---|---|---|---|---|---|---|
| Marketplace Visibility | PARTIAL | FAIL | PARTIAL | PASS | FAIL | PASS | PARTIAL | PARTIALLY GOVERNED |
| Live Quote Generation | FAIL | FAIL | FAIL | PASS | FAIL | PASS | PARTIAL | MATERIAL GAPS |
| Governed Job Routing | PARTIAL | FAIL | PARTIAL | FAIL | PASS | PARTIAL | PASS | PARTIALLY GOVERNED |
| Production Dispatch | PARTIAL | FAIL | PARTIAL | FAIL | PASS | PARTIAL | PASS | PARTIALLY GOVERNED |
9. Framework Performance & Validation Statement
The diagnostic performance of the Vertical AI Governance Stack v1.0 is summarized by the following defensible statement:
Within the assessed scope, the framework independently rediscovered the previously documented critical governance bypasses and identified additional governance weaknesses without confirmed false positives during this assessment.
10. Candidate Refinements for v1.1
Applying the frozen v1.0 framework exposed three structural blind spots, documented as candidate v1.1 refinements:
Refinement A — Asynchronous Execution Principals
Candidate Invariant: Every side-effecting autonomous execution principal — interactive agent, daemon, worker, scheduler, orchestrator or service — MUST be subject to an equivalent authority verification boundary.
Refinement B — Cross-Runtime Governance Equivalence
Candidate Invariant: Governance invariants MUST survive transport, framework and runtime boundaries.
Refinement C — Privileged Default Escalation Antipattern
Candidate Invariant: Missing identity or scope context MUST reduce authority; it MUST NOT resolve to a privileged default.
11. Study Limitations
Explicit limitations of this study include:
- Single-System Case Study: Findings on
@ppos/control-planecannot be statistically generalized to all AI architectures. - Repository-Level Assessment: Assessment relied on static code analysis, route mapping, and safe local execution.
- Absence of Empirical False-Positive Proof: No confirmed false positives were identified, but this does not prove a zero false-positive rate across untested paths.
- Temporal Boundary: Reflects Control Plane v1.9.5.
- No Regulatory Certification: Academic research paper only.
12. Interpretation
The assessment provides initial applied evidence that the Vertical AI Governance Stack can expose governance defects across interactive, asynchronous, and legacy execution paths. The exercise also revealed that applied assessment should stress-test the framework itself.
13. Subject Qualification
PrintPriceOS Control Plane (@ppos/control-plane v1.9.5) is qualified as a Partial Reference Implementation. It demonstrates state-of-the-art governance design in financial production activation and readiness-gated schema compatibility while retaining documented governance coverage gaps.
14. Remediation Direction
High-level engineering remediation requires: (1) removing req.headers['x-user-role'] fallback checks and binding body parameters strictly to authenticated JWT claims; (2) instantiating a system background actor CVA context inside autonomousOrchestrator.js; and (3) computing SHA-256 parameter hashes at authorization time to enforce parameter immutability post-authorization.
15. Reproducibility Appendix
Evaluated Framework: Vertical AI Governance Stack v1.0
Evaluated Instrument: Implementation Conformance Checklist v1.0
Target System: PrintPriceOS Control Plane (@ppos/control-plane v1.9.5)
Assessment Date: September 19, 2026
Primary Internal Artifacts: CONTROL_PLANE_GOVERNANCE_ASSESSMENT_v1.md, CONTROL_PLANE_EXECUTION_SURFACE.md, CONTROL_PLANE_GOVERNANCE_FINDINGS.md, CONTROL_PLANE_PROOF_OBLIGATIONS.md, VERTICAL_AI_GOVERNANCE_STACK_VALIDATION_NOTES.md.
Cite This Paper
To cite this research paper, use the following BibTeX entry:
@article{morales2026appliedvalidation,
author = {Morales Santiago, Manuel Enrique},
title = {Vertical AI Governance Stack v1.0 --- First Applied Validation: A Governance Assessment of the PrintPriceOS Control Plane},
journal = {LatinFlash Research Papers},
year = {2026},
month = {September},
number = {2026-06},
url = {https://research.latinflash.com/papers/applied-validation-control-plane/},
publisher = {LatinFlash Research},
note = {ORCID: 0009-0007-6921-7688, Wikidata: Q141498244, Dialnet: 3123473}
}