AGI Jobs v0 (v2) — Demo → Alpha Meta

Launcher safety and mode upgrade

The launcher now defaults to an effect-free plan. --help and exact --dry-run also perform no runtime work. Execution requires an explicit --mode execute, network, Compose choice and --yes; dependencies are never installed automatically. See the mode upgrade and evidence boundaries before using operational commands below. Planning and inert tests do not qualify a deployment or establish production readiness.

Developer typecheck

Run npx --no-install tsc --project demo/alpha-meta/tsconfig.json --noEmit with the locked repository dependencies installed. The source root includes the sibling governance engine imported by Alpha-Meta. CI runs this native project check whenever either demo changes. This checks TypeScript compatibility; it does not execute the full mission pipeline or establish solver convergence. If emitting JavaScript manually, the demo source hierarchy is retained beneath dist/.

AGI Jobs v0 (v2) is our sovereign intelligence engine; this module extends that superintelligent machine with specialised capabilities for demo/alpha-meta.

Overview

• Path: demo/alpha-meta/README.md
• Module Focus: Anchors Demo → Alpha Meta inside the AGI Jobs v0 (v2) lattice so teams can orchestrate economic, governance, and operational missions with deterministic guardrails.
• Integration Role: Interfaces with the unified owner control plane, telemetry mesh, and contract registry to deliver end-to-end resilience.

Capabilities

• Provides opinionated configuration and assets tailored to demo/alpha-meta while remaining interoperable with the global AGI Jobs v0 (v2) runtime.
• Ships with safety-first defaults so non-technical operators can activate the experience without compromising security or compliance.
• Publishes ready-to-automate hooks for CI, observability, and ledger reconciliation.

Systems Map

flowchart LR
    Operators((Mission Owners)) --> demo_alpha_meta[[Demo → Alpha Meta]]
    demo_alpha_meta --> Core[["AGI Jobs v0 (v2) Core Intelligence"]]
    Core --> Observability[[Unified CI / CD & Observability]]
    Core --> Governance[[Owner Control Plane]]

Working With This Module

1. From the repository root run npm install once to hydrate all workspaces.
2. Inspect the scripts under scripts/ or this module's package.json entry (where applicable) to discover targeted automation for demo/alpha-meta.
3. Execute npm test and npm run lint --if-present before pushing to guarantee a fully green AGI Jobs v0 (v2) CI signal.
4. Capture mission telemetry with make operator:green or the module-specific runbooks documented in OperatorRunbook.md.

Directory Guide

Key Directories

• bin
• config
• reports
• scripts

Key Files

• RUNBOOK.md
• tsconfig.json

Quality & Governance

• Every change must land through a pull request with all required checks green (unit, integration, linting, security scan).
• Reference RUNBOOK.md and OperatorRunbook.md for escalation patterns and owner approvals.
• Keep secrets outside the tree; use the secure parameter stores wired to the AGI Jobs v0 (v2) guardian mesh.

Next Steps

• Review this module's issue board for open automation, data, or research threads.
• Link new deliverables back to the central manifest via npm run release:manifest.
• Publish artefacts (dashboards, mermaid charts, datasets) into reports/ for downstream intelligence alignment.

Mermaid rendering corrections dated October 8, 2026 are recorded in the historical report manifest. They preserve the original simulation values and timestamps; they do not represent a new execution or new production evidence. The manifest also identifies four pre-existing artifact hash mismatches, which remain unverified historical evidence.