Scale & orchestration
Omni Orchestrator Explore the Singularity orchestration scenario and its documented assumptions.
Code & guide What to expect This directory includes code and documentation. Its guide defines dependencies, execution modes and what the results demonstrate.
Guides & runbooks 3
Registered commands 0 Environment setup ↗ Guided tour Inspect the sources Try it locally Architecture Complete library A CLOSER LOOK
Where does a governance rehearsal cross into an authorized action? For governance operators: inspect council identities, emergency controls and the script’s dry-run versus execute paths.
01 02 03 Audit execution branches Inspect every branch under dry-run and execute, including identity updates and owner-control calls. A flag name alone is insufficient evidence that every nested action is read-only.
demo/omni-orchestrator-singularity/bin/orchestrate.sh ↗ Inspect this source ↓ REAL REPOSITORY MATERIAL
Inspect. Understand. Reproduce. Reading the exact source at revision 5b4cebb3.
demo/omni-orchestrator-singularity/config/council.example.json
Select a walkthrough step to explore its source.
Show more fields ↓ Full source text {
"members": [
{
"address": "0x0000000000000000000000000000000000000010",
"weight": 1,
"label": "Aurora Prime"
},
{
"address": "0x0000000000000000000000000000000000000020",
"weight": 1,
"label": "Meridian Arcology"
},
{
"address": "0x0000000000000000000000000000000000000030",
"weight": 1,
"label": "Neutral Oversight"
}
],
"timelock": {
"executionDelaySeconds": 900,
"gracePeriodSeconds": 3600
}
}
SHA-256 540cb5adbb4c5a08f1125275e8d370310cc320aa2f45e06a00a4e7e94375696d
The first source is shown in full. All walkthrough source links and the complete document library remain available without JavaScript.
{"revision":"5b4cebb309a83a7a6749d8911d8bf96a1921e042","sources":[{"file":"demo/omni-orchestrator-singularity/config/council.example.json","content":"{\n \"members\": [\n {\n \"address\": \"0x0000000000000000000000000000000000000010\",\n \"weight\": 1,\n \"label\": \"Aurora Prime\"\n },\n {\n \"address\": \"0x0000000000000000000000000000000000000020\",\n \"weight\": 1,\n \"label\": \"Meridian Arcology\"\n },\n {\n \"address\": \"0x0000000000000000000000000000000000000030\",\n \"weight\": 1,\n \"label\": \"Neutral Oversight\"\n }\n ],\n \"timelock\": {\n \"executionDelaySeconds\": 900,\n \"gracePeriodSeconds\": 3600\n }\n}\n","format":"json","sha256":"540cb5adbb4c5a08f1125275e8d370310cc320aa2f45e06a00a4e7e94375696d","bytes":493,"download":"/AGIJobsv0/examples/540cb5adbb4c5a08-council.example.json","source":"https://github.com/MontrealAI/AGIJobsv0/blob/5b4cebb309a83a7a6749d8911d8bf96a1921e042/demo/omni-orchestrator-singularity/config/council.example.json"},{"file":"demo/omni-orchestrator-singularity/config/emergency-drill.json","content":"{\n \"title\": \"Emergency Drill - Pause, Adjust Thermostat, Resume\",\n \"steps\": [\n {\n \"type\": \"pause\"\n },\n {\n \"type\": \"governanceCall\",\n \"target\": \"RewardEngineMB\",\n \"method\": \"setRoleShares\",\n \"args\": [\n {\n \"role\": \"agent\",\n \"shareBps\": 5200\n },\n {\n \"role\": \"validator\",\n \"shareBps\": 4800\n }\n ]\n },\n {\n \"type\": \"governanceCall\",\n \"target\": \"Thermostat\",\n \"method\": \"setTemperature\",\n \"args\": [\"1.10e18\"]\n },\n {\n \"type\": \"unpause\"\n }\n ]\n}\n","format":"json","sha256":"8a2cb4bbbd251ec39c1526d45da319711d009b4d67bd99c247af4c71c5ea7e48","bytes":581,"download":"/AGIJobsv0/examples/8a2cb4bbbd251ec3-emergency-drill.json","source":"https://github.com/MontrealAI/AGIJobsv0/blob/5b4cebb309a83a7a6749d8911d8bf96a1921e042/demo/omni-orchestrator-singularity/config/emergency-drill.json"},{"file":"demo/omni-orchestrator-singularity/bin/orchestrate.sh","content":"#!/usr/bin/env bash\nset -euo pipefail\n\nfunction usage() {\n cat <<USAGE\nUsage: $0 --network <network> [--mode dry-run|execute]\n\nDry-run stops before broadcasting transactions. Execute mode performs full deployment and orchestration.\nUSAGE\n}\n\nNETWORK=\"\"\nMODE=\"execute\"\n\nwhile [[ $# -gt 0 ]]; do\n case \"$1\" in\n --network)\n NETWORK=\"$2\"\n shift 2\n ;;\n --mode)\n MODE=\"$2\"\n shift 2\n ;;\n --help|-h)\n usage\n exit 0\n ;;\n *)\n echo \"Unknown argument: $1\" >&2\n usage\n exit 1\n ;;\n esac\ndone\n\nif [[ -z \"$NETWORK\" ]]; then\n echo \"--network is required\" >&2\n usage\n exit 1\nfi\n\nDRY_RUN=false\nif [[ \"$MODE\" == \"dry-run\" ]]; then\n DRY_RUN=true\nfi\n\nROOT_DIR=\"$(git rev-parse --show-toplevel)\"\nREPORT_DIR=\"$ROOT_DIR/reports/omni-orchestrator-singularity/latest\"\nmkdir -p \"$REPORT_DIR\"\n\nlog() {\n echo \"[omni-orchestrator] $*\"\n}\n\nlog \"network=$NETWORK mode=$MODE\"\n\nif $DRY_RUN; then\n log \"Running one-click deployment script in dry-run mode\"\n npx ts-node scripts/v2/oneclick-stack.ts --network \"$NETWORK\" --dry-run | tee \"$REPORT_DIR/deployment.log\"\nelse\n log \"Executing one-click deployment\"\n npx ts-node scripts/v2/oneclick-stack.ts --network \"$NETWORK\" | tee \"$REPORT_DIR/deployment.log\"\nfi\n\nlog \"Verifying owner control wiring\"\nif $DRY_RUN; then\n npx hardhat run --no-compile scripts/v2/verifyOwnerControl.ts --network \"$NETWORK\" -- --json \\\n | tee \"$REPORT_DIR/owner-control.json\"\nelse\n npx hardhat run --no-compile scripts/v2/updateSystemPause.ts --network \"$NETWORK\" -- --execute \\\n | tee \"$REPORT_DIR/system-pause.log\"\n npx hardhat run --no-compile scripts/v2/verifyOwnerControl.ts --network \"$NETWORK\" -- --json \\\n | tee \"$REPORT_DIR/owner-control.json\"\nfi\n\nlog \"Seeding identity registry\"\nif $DRY_RUN; then\n log \"Skipping identity registry writes in dry-run mode\"\nelse\n npm run identity:update -- --network \"$NETWORK\" --config demo/omni-orchestrator-singularity/config/identities.example.json | tee \"$REPORT_DIR/identities.log\"\nfi\n\nlog \"Capturing orchestrator plan pipeline instructions\"\ncat demo/omni-orchestrator-singularity/docs/mandate-script.md > \"$REPORT_DIR/mandate-script.md\"\n\nlog \"Recording governance drill templates\"\ncp demo/omni-orchestrator-singularity/config/emergency-drill.json \"$REPORT_DIR/emergency-drill.json\"\n\nlog \"Done. Follow README.md for interactive steps.\"\n","format":"text","sha256":"560da84b1350efe4c6bb64269dacf43409acb2b8ec1da6b9914826f57b4235d4","bytes":2371,"download":"/AGIJobsv0/examples/560da84b1350efe4-orchestrate.sh","source":"https://github.com/MontrealAI/AGIJobsv0/blob/5b4cebb309a83a7a6749d8911d8bf96a1921e042/demo/omni-orchestrator-singularity/bin/orchestrate.sh"}]} FROM READING TO A REPRODUCIBLE RUN
Try the selected path. Configured operator environment Start with the linked setup and component runbooks. This experience crosses several services or network-aware scripts; the first command below is labeled with its actual scope. Prepare local addresses, services and output paths before invoking the broader launcher.
Complete environment setup ↗ SELECTED EXECUTION PATH Copy
bash demo/omni-orchestrator-singularity/bin/orchestrate.sh --helpWhat you should observe The script prints its network and mode usage. Before a rehearsal, prepare the documented local network and inspect nested actions; no live operation is performed by this help command.
The source inspector above reads bundled repository material. Local commands run separately on your computer. Recorded examples may contain historical timestamps, placeholders and simulated metrics.
MAKE IT YOUR OWN
One useful experiment. Locate the commands that can alter ownership, identity or pause state. Explain the authority and transaction evidence required for each.
THE SYSTEM, MADE VISIBLE
Architecture & relationships Architecture diagram · source preserved below
View original Mermaid source flowchart LR
Operators((Mission Owners)) --> demo_omni_orchestrator_singularity[[Demo → Omni Orchestrator Singularity]]
demo_omni_orchestrator_singularity --> Core[[AGI Jobs v0 (v2) Core Intelligence]]
Core --> Observability[[Unified CI / CD & Observability]]
Core --> Governance[[Owner Control Plane]]WHEN SOMETHING DOESN’T MATCH
Troubleshooting A command or service fails Start at the first error, confirm the working directory and pinned toolchain, then follow the linked component guide. Optional packages and provider services have separate prerequisites.
A report looks successful but lacks evidence Check its source revision, configuration, timestamps and underlying events. Historical fixtures and generated plans do not prove a fresh execution.
TRACE THE CHECKS
Verification & next steps This directory has no standalone test source files. Follow the shared implementation and its behavioral tests before making correctness claims.
For live commissioning, consult the production readiness record .
EVERY VARIANT, PRESERVED
Complete document library REPRODUCE & INSPECT
Registered commands Run commands from the repository root after following this demo's guide. Network and owner actions require their documented setup.
No root-level launch command is associated with this source path. Follow the guide or source directory for its own entry point.
Full command catalog and troubleshooting ↗