Three-node MCP installation lab
Server 1 remains the governance and MCP host, Server 2 hosts infrastructure and shared services, and Server 3 stays empty until the MCP installs the application layer and then a test engine with its database and Local Control Panel.
Server 1 should host governance, MCP, platform, and runtime services.
Server 2 should host infrastructure, shared AI, shared API, and theme services.
Server 3 should be admitted and waiting for the application-layer install.
Use the MCP action below to register the platform service, confirm runtime readiness, join runtime, and link Server 3.
The final step installs the test engine runtime together with the database and local control panel.
No governed infrastructure jobs have been queued into the live MCP review yet.
Install Sequence
The MCP test follows the exact three-node order required for the local Version 3 review.
- 01Seed governance and MCP on Server 1Waiting for the governance seed to create Server 1.Target node: phaco-local-vm-01
- 02Seed the infrastructure host on Server 2Waiting for Server 2 bootstrap artifacts.Target node: phaco-local-vm-02
- 03Admit Server 3 as the waiting application nodeWaiting for Server 3 bootstrap artifacts.Target node: phaco-local-vm-03
- 04Install the application layer from the MCPThis action provisions the application-layer shell and advances Server 3 from Missing toward install ready.Platform service: vm-lab-application-layer
- 05Install the test engine, database, and LCPThis action approves the release, queues the governed package, binds shared-service leases from Server 2, and installs the test engine stack on Server 3.Related services: vm-lab-postgres / vm-lab-local-control-panel
Server 3 Install Actions
Use governed MCP actions to move Server 3 from waiting application-node state into application-layer and engine-stack readiness.
Server 3 Cross-plane State
This summarizes how governance, runtime, and integration currently describe the waiting or installed application node.
Latest Install Result
Each action returns a concise MCP-side summary so the operator can review what changed.
- 01Seed governance and MCP on Server 1Waiting for the governance seed to create Server 1.Target node: phaco-local-vm-01
- 02Seed the infrastructure host on Server 2Waiting for Server 2 bootstrap artifacts.Target node: phaco-local-vm-02
- 03Admit Server 3 as the waiting application nodeWaiting for Server 3 bootstrap artifacts.Target node: phaco-local-vm-03
- 04Install the application layer from the MCPThis action provisions the application-layer shell and advances Server 3 from Missing toward install ready.Platform service: vm-lab-application-layer
- 05Install the test engine, database, and LCPThis action approves the release, queues the governed package, binds shared-service leases from Server 2, and installs the test engine stack on Server 3.Related services: vm-lab-postgres / vm-lab-local-control-panel
Governed Install Queue
Placement, package authorization, and install execution are now tracked separately from runtime deployment effects.
- 01No governed install queue yetApprove an install-ready package and run the engine-stack action to persist placement and execution state.Queued, running, failed, and completed posture will appear here.
- 02DiscoveryNo local discovery event yetRun the engine-stack action to simulate GitHub release discovery through governance intake.
Governed Infrastructure
The MCP now reflects the governance infrastructure baseline, latest request, queued job, and managed node inventory.
- 01Latest install queueNo governed install queue yetInstall-ready packages will appear here after governance approval and queueing.
- 02Infrastructure baselineNo infrastructure baseline loadedThe governance infrastructure baseline will appear here when the live adapter responds.
- 03Latest requestNo governed infrastructure request yetA queued request will appear here before provisioning starts.
- 04Latest jobNo governed infrastructure job yetQueued jobs will appear here once governance promotes a request.
- 05Managed node inventory0 governed infrastructure nodesManaged nodes will appear here after provisioning completes.
- 06Capacity schedulerNo install-ready application node has remaining capacity for this engine class.Server 3 cannot accept another governed engine package without new-node fallback.
Infrastructure Execution Trail
Provisioning jobs record governed execution history here before the runtime and application layers take over.
- 01No governed infrastructure activity yetInfrastructure requests, job execution records, and managed nodes will appear here once provisioning starts.This panel is driven by the governance infrastructure service.
Infrastructure Shared-Service Host
Server 2 is the centralized host for shared AI, API, and theme services that application nodes lease instead of duplicating.
- 01AI Agent Service -> server2.phacokinetic.com3 packages hosted on phaco-local-vm-02Centralized worker capacity remains leaseable to application nodes.
- 02API Services Pool -> server2.phacokinetic.com3 packages hosted on phaco-local-vm-02Governed API integrations are exposed centrally instead of duplicating them per node.
- 03Theme Registry -> server2.phacokinetic.com3 packages hosted on phaco-local-vm-02Shared presentation packages remain available from the infrastructure node.
Server 3 Runtime History
Deterministic orchestration hook entries show what the MCP has applied to the application node.
- 01No Server 3 orchestration history yetRun the application or engine install action to seed deterministic hook history.The MCP will record application-layer, database, and LCP steps here.
Engine Stack Surface
The target services and deployment records that should exist after the second install step completes.