Repository navigation
Working Alpha Acceptance
The working-alpha acceptance harness proves the running MCOS product end to
end and is the preferred way to certify a working alpha. All scripts are
non-mutating by default; add -Certification to make working-alpha readiness and
required HTTP.sys bindings hard-required checks — any required-probe failure
exits nonzero.
Full operator runbook (in the repository): docs/operator/working-alpha-acceptance.md.
Run on the MCOS host:
pwsh -NoProfile -ExecutionPolicy Bypass -File `
scripts\Test-MasterControlOrchestrationServerWorkingAlpha.ps1 `
-Certification `
-BaseUrl http://127.0.0.1:7300 `
-BootstrapperPath "C:\Program Files\Master Control Orchestration Server\MasterControlBootstrapper.exe" `
-InstallDirectory "C:\Program Files\Master Control Orchestration Server" `
-OutDirectory artifacts\working-alpha-localIt probes every required admin route (including /api/clients, /api/pools,
/api/diagnostics/runtime-stats), the gateway initialize / ping /
tools/list over JSON-RPC, discovery routability (conditioned on network
posture), the workingAlpha readiness block on /api/health/summary, and — when
a bootstrapper is supplied — the per-surface bindings verdicts from
MasterControlBootstrapper.exe validate --json. It writes JSON + Markdown
reports plus per-probe request/response evidence and invokes the diagnostics
collector on both pass and fail.
Run on the MCOS host (local operator, over loopback):
pwsh -NoProfile -ExecutionPolicy Bypass -File `
scripts\Register-MasterControlLanClient.ps1 `
-ClientId codex-alpha-01 -ClientType codex `
-OutputPath artifacts\clients\codex-alpha-01.jsonThe client is registered read-only (no mutation privileges unless explicit
-Privilege switches are passed), and the exported bundle carries the gateway,
discovery, heartbeat, and onboarding URLs plus the X-MCOS-Client-Id identity.
Run from the LAN peer with the exported bundle:
pwsh -NoProfile -ExecutionPolicy Bypass -File `
.\Test-MasterControlLanClientAcceptance.ps1 `
-Certification `
-DiscoveryUrl http://<mcos-host>:7300/.well-known/mcos.json `
-ClientBundlePath .\codex-alpha-01.json `
-OutDirectory .\mcos-lan-acceptanceIt rejects loopback/wildcard advertised URLs, posts telemetry and authenticated
X-MCOS-Client-Id heartbeats, completes MCP initialize / ping / tools/list,
and confirms the client appears with a fresh liveness timestamp in
/api/telemetry/clients.
After any failure (or a successful run), collect an evidence bundle:
pwsh -NoProfile -ExecutionPolicy Bypass -File `
scripts\Get-MasterControlOrchestrationServerDeploymentDiagnostics.ps1 `
-BaseUrl http://127.0.0.1:7300 `
-BootstrapperPath "C:\Program Files\Master Control Orchestration Server\MasterControlBootstrapper.exe" `
-InstallDirectory "C:\Program Files\Master Control Orchestration Server" `
-BundleThe bundle includes service status, event logs, netsh URL ACL / SSL cert /
firewall state, port listeners, admin + gateway probe outputs, the workingAlpha
readiness block, and the structured bootstrapper bindings.
GET /api/health/summary carries a workingAlpha object: a fail-closed
readiness report. Every availability signal defaults to its blocking value, so
readiness cannot pass without live evidence. It reports ready,
blockingIssues[] (stable id / category / state), and a per-signal
signals[] provenance list. A required pool counts ready only after an instance
completes a real MCP initialize handshake, not merely process spawn. In
-Certification mode a non-ready report fails the run. See
API Reference for the full field list.
- Release Gate — alpha release policy and the product gate
- LAN Clients — client identity, bundles, heartbeat
- LAN Discovery — discovery documents and routable advertisement
- Maintenance — install, repair, uninstall
Source for this wiki is maintained under docs/wiki/ in the Master-Control-Orchestration-Server repository.
Setup
Connect Clients
Operate
- Daily Operations
- Dashboard
- Telemetry and Activity
- Gateway
- Worker Pools
- Sub-Agents
- Governance
- CLU Governance
- Privileges
Maintain
Troubleshoot
Reference