Skip to content

Project notice

1.12.2 — Reliable installed demos and a complete walkthrough

The canonical alpha_factory_v1/demos catalog now works reliably from a release wheel outside the repository. The demo walkthrough connects every browser experience and all preserved experiments to the full Insight → Nova-Seeds → MARK → Sovereign → Jobs → validator lifecycle. Use the release installation walkthrough to install matching, checksum-verified assets.

Installed examples and launch safety

  • The wheel includes all six original CSV samples and unchanged copies of the 11 Sector-Shock-10 fixtures used by Insight. Acceptance compares every bundled file with the original bytes and executes all 14 finite catalog commands with Python network calls blocked.
  • check NAME [--json] reports declared module and bundled-file prerequisites without importing optional backends, downloading, creating run state or revealing credentials. run performs this check before starting a child. Missing weights, live services and provider access still need their documented integration checks.
  • Launch paths resolve against the installed package. Output directories cannot shadow its Python package, and empty or relative inherited Python paths cannot become implicit child working paths. A file used as an output directory produces an actionable error while retaining its contents.
  • Finite catalog commands disable OpenAI/Anthropic keys and tracing in the child. Tree search uses its bundled configuration and random rewriter; Marketplace uses its bundled job; Macro and Era use their packaged CSV paths. Parent credentials and advanced standalone options are unchanged.
  • Offline children also disable remote Neo4j/PostgreSQL storage, preventing optional memory imports from probing a default or inherited database. An empty Neo4j URI selects local storage without constructing a driver. Explicitly configured service launches keep their existing connection path.
  • Plain self-edit file helpers remain usable when the optional Agents SDK raises an import error for unavailable transport extras. This fallback does not claim provider execution.

All 26 entries have refreshed launch sections and prerequisite commands. The new walkthrough covers browser choices, source and wheel installation, output recovery, execution modes and the full vision map. It is included in release documents and the complete operator-guide archive.

The runtime matrix tests launcher boundaries on Python 3.11–3.13 and runs installed Governance, Macro Sentinel and Era commands with minimal operator dependencies. Full regression additionally exercises all 14 finite wheel commands. A required Python 3.11/3.12 matrix repeats them with the complete backend dependencies, inherited database settings and no test-only integration shortcuts. Native CPU, browser/model, contracts, signed evidence, containers, dependency audits, strict documentation and publication acceptance remain required. Exact outcomes are recorded in the matching release validation archive.

Every original demo, flowchart, media asset and manuscript remains. Existing agent state and lineage need no migration. Use a new environment and retain prior state as described in operations.

The release scope remains bounded: a maintained private operator runtime, labeled browser experiences, preserved research integrations and an undeployed local-EVM contract reference. The release does not establish general AGI, predictive superiority or a commissioned mainnet economy.