Repository guide · 0 diagrams

View source on GitHub ↗
Original documentation, preserved from the repository. Historical projections and scenario ambitions are not evidence of live performance. See the current readiness record for deployment requirements.

Start here: AGI Jobs v0 (v2)

This repository contains smart contracts, agent and validator services, operator interfaces, and demonstrations of an agent-work marketplace. Begin locally, inspect the evidence, and then follow the deployment runbooks for your chosen environment.

Current release posture: local development and demonstrations are testable. The contract-size blocker is resolved through fixed implementations and staged deployment. Release remains blocked by unconfigured maintainer signing trust and the integration/configuration requirements in the readiness report. Read the readiness report before preparing any deployment.

Choose your route

Your goal Open this
Understand the architecture and its diagrams Repository overview
Explore a working model demo without a wallet Tiny Recursive Model setup
Execute a job from creation to local settlement AURORA walkthrough
Run a three-job local mission with receipts ASI Take-Off walkthrough
Rehearse release, provider failures, security controls, and commissioning Production rehearsal
Choose, run, or validate any demo Demo guide and complete catalog
Find a subsystem manual Documentation catalog
Run the browser console Console instructions
Develop agent integration Gateway guide
Coordinate browser and desktop work Computer-work setup and recovery, then the executable supplier-desk lab
Inspect a delivery and record review findings Evidence review guide and local reviewer
Understand owner controls Operator runbook
Prepare a production deployment Readiness report, then security deployment guide

Reproduce the local baseline

Use Node 22.23.3, npm 10.8.2, and Python 3.12. The commands below assume a POSIX shell and an installed nvm. Run from the repository root.

nvm install
nvm use
npm install --global npm@10.8.2
CYPRESS_INSTALL_BINARY=0 npm ci
npm run doctor:node
npm run ci:preflight
npm run compile
npm test

CYPRESS_INSTALL_BINARY=0 defers the browser download during dependency setup. Browser end-to-end tests install their binary separately. Keep optional npm dependencies: Solidity tooling uses platform-specific binaries.

Create an isolated Python environment rather than modifying your system packages:

python3.12 -m venv .venv
source .venv/bin/activate
python -m pip install -r requirements-python.txt
python -m pip check
PYTEST_DISABLE_PLUGIN_AUTOLOAD=1 python -m pytest

To include the neural-model tests, resolve both requirement sets together:

python -m pip install -r requirements-python.txt -r demo/Tiny-Recursive-Model-v0/requirements-core.txt --extra-index-url https://download.pytorch.org/whl/cpu
python -m pip check
OMP_NUM_THREADS=1 MKL_NUM_THREADS=1 PYTEST_DISABLE_PLUGIN_AUTOLOAD=1 python -m pytest -m requires_torch

Install the optional model dashboard in its own virtual environment. Its Streamlit dependencies may conflict with the platform API's pinned FastAPI version.

Inspect readiness before releasing

npm run release:check-size
npm run release:audit-dependencies
npm run ci:verify-signers

The size check passes for the modular contracts. The dependency check retains registry audit evidence for every tracked npm and pnpm lockfile and fails on critical/high findings or unavailable evidence; it currently reports unresolved high findings. The signer check intentionally fails on the example signing keys. Read the deployment architecture guide before deploying new controllers. Follow their diagnostic output and the remaining work. Do not interpret a green local test suite, simulated economy, dashboard, or successful compilation as evidence of a deployable or audited production system.

This repository's v2 contract configuration uses the 18-decimal $AGIALPHA token. Confirm the actual token, chain, contract addresses, and deployment manifest for the workflow you run; do not substitute another AGI Jobs repository's settlement assumptions.

Common setup problems

Symptom Action
Node doctor reports the wrong version Run nvm use at the repository root; check both node -v and npm -v.
Python dependency conflict or router import error Use a fresh virtual environment; install all required files in one pip command, then run python -m pip check.
Native Python dependency cannot build Install your platform's C compiler and Python headers; on a managed interpreter select an available compiler with CC=gcc.
Missing Solidity artifacts Run npm run compile before contract tests and the size gate.
A live command asks for RPC or wallet configuration Read that command's runbook. Preview flags differ by command; signing and configuration changes may write on-chain.
Release signer validation fails Replace the illustrative entries with authorized SSH public keys using the signer guide.
← Back to the collection