Why does this demo also have an underscore-style package name?
For Python users and contributors: understand an import-compatible facade that preserves access to the canonical demo without duplicating its engine.
01
Read the compatibility layer
Inspect how this package locates or re-exports the canonical implementation. The alias is supporting infrastructure, not a separate performance demonstration.
Confirm the resolved implementation path when debugging imports. Run from the repository root or use the documented launcher so relative package paths resolve consistently.
"""Compatibility wrapper exposing the AlphaEvolve demo as a Python package."""
from __future__ import annotations
from importlib import import_module
from pathlib import Path
import sys
_pkg_dir = Path(__file__).resolve().parent.parent / "AlphaEvolve-v0"
if str(_pkg_dir) not in sys.path:
sys.path.append(str(_pkg_dir))
alphaevolve_demo = import_module("alphaevolve_demo")
__all__ = ["alphaevolve_demo"]
{"revision":"5b4cebb309a83a7a6749d8911d8bf96a1921e042","sources":[{"file":"demo/AlphaEvolve_v0/__init__.py","content":"\"\"\"Compatibility wrapper exposing the AlphaEvolve demo as a Python package.\"\"\"\nfrom __future__ import annotations\n\nfrom importlib import import_module\nfrom pathlib import Path\nimport sys\n\n_pkg_dir = Path(__file__).resolve().parent.parent / \"AlphaEvolve-v0\"\nif str(_pkg_dir) not in sys.path:\n sys.path.append(str(_pkg_dir))\n\nalphaevolve_demo = import_module(\"alphaevolve_demo\")\n\n__all__ = [\"alphaevolve_demo\"]\n\n","format":"text","sha256":"2aff7031ceeabb7c881d81c87f2647c7942a4336641fa213b472c86fce71df2d","bytes":413,"download":"/AGIJobsv0/examples/2aff7031ceeabb7c-__init__.py","source":"https://github.com/MontrealAI/AGIJobsv0/blob/5b4cebb309a83a7a6749d8911d8bf96a1921e042/demo/AlphaEvolve_v0/__init__.py"},{"file":"demo/AlphaEvolve-v0/README.md","content":"# AGI Jobs v0 (v2) — Demo → AlphaEvolve v0\n\n> AGI Jobs v0 (v2) is our sovereign intelligence engine; this module extends that superintelligent machine with specialised capabilities for `demo/AlphaEvolve-v0`.\n\n## Overview\n- **Path:** `demo/AlphaEvolve-v0/README.md`\n- **Module Focus:** Anchors Demo → AlphaEvolve v0 inside the AGI Jobs v0 (v2) lattice so teams can orchestrate economic, governance, and operational missions with deterministic guardrails.\n- **Integration Role:** Interfaces with the unified owner control plane, telemetry mesh, and contract registry to deliver end-to-end resilience.\n\n## Capabilities\n- Provides opinionated configuration and assets tailored to `demo/AlphaEvolve-v0` while remaining interoperable with the global AGI Jobs v0 (v2) runtime.\n- Ships with safety-first defaults so non-technical operators can activate the experience without compromising security or compliance.\n- Publishes ready-to-automate hooks for CI, observability, and ledger reconciliation.\n\n## Systems Map\n```mermaid\nflowchart LR\n Operators((Mission Owners)) --> demo_AlphaEvolve_v0[[Demo → AlphaEvolve v0]]\n demo_AlphaEvolve_v0 --> Core[[AGI Jobs v0 (v2) Core Intelligence]]\n Core --> Observability[[Unified CI / CD & Observability]]\n Core --> Governance[[Owner Control Plane]]\n```\n\n## Working With This Module\n1. From the repository root run `npm install` once to hydrate all workspaces.\n2. Inspect the scripts under `scripts/` or this module's `package.json` entry (where applicable) to discover targeted automation for `demo/AlphaEvolve-v0`.\n3. Execute `npm test` and `npm run lint --if-present` before pushing to guarantee a fully green AGI Jobs v0 (v2) CI signal.\n4. Capture mission telemetry with `make operator:green` or the module-specific runbooks documented in [`OperatorRunbook.md`](../../OperatorRunbook.md).\n\n## Directory Guide\n### Key Directories\n- `alphaevolve`\n- `alphaevolve_demo`\n- `config`\n- `tests`\n- `web`\n### Key Files\n- `__init__.py`\n- `alphaevolve_manifest.json`\n- `alphaevolve_runner.py`\n- `alphaevolve_summary.json`\n\n## Quality & Governance\n- Every change must land through a pull request with all required checks green (unit, integration, linting, security scan).\n- Reference [`RUNBOOK.md`](../../RUNBOOK.md) and [`OperatorRunbook.md`](../../OperatorRunbook.md) for escalation patterns and owner approvals.\n- Keep secrets outside the tree; use the secure parameter stores wired to the AGI Jobs v0 (v2) guardian mesh.\n\n## Next Steps\n- Review this module's issue board for open automation, data, or research threads.\n- Link new deliverables back to the central manifest via `npm run release:manifest`.\n- Publish artefacts (dashboards, mermaid charts, datasets) into `reports/` for downstream intelligence alignment.\n","format":"text","sha256":"39b7f22144bd6893e293c53f546bb3f9ee40baf921ca2c0fe74cae2b66981f66","bytes":2763,"download":"/AGIJobsv0/examples/39b7f22144bd6893-README.md","source":"https://github.com/MontrealAI/AGIJobsv0/blob/5b4cebb309a83a7a6749d8911d8bf96a1921e042/demo/AlphaEvolve-v0/README.md"}]}
FROM READING TO A REPRODUCIBLE RUN
Continue to the implementation.
Supporting material
This entry supports another demo or the collection as a whole. Use the canonical experience for execution; preserve the compatibility layer or presentation asset when making changes.
Open the canonical experience below. This package exists for import compatibility; its success should be evaluated by delegation and behavioral parity, not a separate synthetic score.
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.
Compare the imported module path and exported API with the canonical source. If behavior differs, inspect the shim and the environment before changing the underlying engine.
THE SYSTEM, MADE VISIBLE
Architecture & relationships
This supporting entry has no standalone architecture diagram. Follow its related experience below to inspect the canonical system.
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
1 tracked test source files are available in this directory. Inspect the tests and their environment before choosing a suite; file counts do not establish test results.