Skip to content

Project notice

1.27.2 — Alpha + AGI Jobs: one shared token, complementary capabilities

Explore Alpha + AGI Jobs to see how project funding, defined work, review and payment can support a coordinated workflow. The guide explains each system's role, gives an illustrative software-project example, and links to both recorded Ethereum deployments. For a separately installed agent, follow the operator start guide and the backup, upgrade and recovery instructions.

What visitors can explore

  • A prominent homepage introduction to both repositories and their shared Ethereum mainnet token: $AGIALPHA, 0xA61a3B3a130a9c20768EEBF97E21515A6046a1fA.
  • A readable guide to five Alpha contracts and 24 AGIJobsv0 instances, with full selectable addresses, plain-language roles, Etherscan links and source-pinned deployment evidence.
  • The practical connection between project commitments, funding, worker accountability, result review and settlement, with the additional integration and commissioning work explained beside the examples.
  • Existing first-plan, SUCCESSOR, demonstration, research and flowchart journeys retained alongside the new guide.

Deployment and integration scope

The shared token is an existing dependency of both suites. This publication does not deploy contracts or alter their balances, permissions, admission settings or pause state. The recorded Alpha MARK contract routes to its own immutable AscensionJobMarket; automatic routing to AGIJobsv0's separate JobRegistry is not established. Identity compatibility in source requires its own configuration and validation.

Alpha's October 11 deployed-source archive predates later settlement hardening. AGIJobsv0's October 12 deployment retains its rc.4 source identity. The guide identifies the dated public records and links to their operating boundaries; a source-verification record is not a fresh live-state observation.

Acceptance and upgrade

The exact integrated commit must pass the existing complete release acceptance, including public Pages verification, before publication. The release manifest and validation archive identify actual results. The previous development-toolchain maintenance record and remaining dependency work stay explicit. No journal migration is introduced; retain the existing backup and recovery process.