Project notice

Find your Alpha. Build your SUCCESSOR Ω.

Start with discovery · Open your project

Alpha helps you examine supplied evidence and run a bounded task. Jobs prepares separately priced work. Fleet accepts an explicit local execution request and returns the actual result and internal checking record. The guided workspace retains these files in one project history, including rejected results and earlier cycles.

Your first complete local cycle

1. In Find your Alpha, describe the mission, current approach, strongest alternative, supplied evidence and constraints. Compute and download the proposal. An unknown advantage stays unknown.
2. Open Your mission, import that discovery brief and separately select the permitted group,amount integer CSV. A discovery goal is never translated automatically into executable work. Save the project, run the bounded task and inspect its files. Record your local accepted or rejected review.
3. In One project, from discovery to returned work, choose the commissioning route and download the project for Manager, open its linked receiver and confirm the explicit row mapping. The $AGIALPHA route uses the actual Jobs compiler directly in this guided workspace.
4. Enter the USDC price in Manager, or the $AGIALPHA token allowance in the guided workspace. AGIJobManager uses USDC; AGI Jobs v0 JobRegistry uses $AGIALPHA. Each creates its own unfunded proposal with its own rules. Import the Manager return into Alpha; the inline Jobs transfer is retained automatically, and its bounded task can be run locally before Fleet.
5. Prepare a Fleet request from that exact retained transfer. On the local Fleet host, its authenticated operator must import the request, prepare the Agent's task, explicitly authorize and run it, then prepare, authorize and run the separate Node's internal check. Export the project return and inspect it in Alpha.
6. Save the complete journey. To continue, explicitly select the input and start a fresh Alpha cycle. Changed input gets a new mission/cycle; earlier exact inputs, failed attempts, rejected reviews and returns stay in the history. Save the complete journey again after further work.

The native project download remains compatible with its native receivers. The complete journey download is an additive alpha-guided-project/v1 history containing those exact files; it is not an executable authority or settlement envelope. Reopen it using Reopen complete journey, then explicitly create a fresh cycle.

Local Alpha execution checks the actual native planner before saving executable input or starting a run. Use a mission name of at most 48 characters and composed Unicode (NFC) for its name and license. A longer or unsupported imported native input remains readable as unchanged history. Choose Edit input for a fresh mission/cycle, explicitly edit the input, and save a valid new mission or cycle. The Jobs receiver separately records its explicit executor-name/license mapping while retaining the original native bytes.

Keep the two routes clear

Route	Asset	What this local journey retains
AGIJobManager	USDC	Exact Alpha project, deterministic Manager run and independently entered unfunded USDC draft
AGI Jobs v0 JobRegistry	$AGIALPHA	Exact project and bounded work compiled with the native Jobs compiler; local work remains uncommissioned
Fleet	Retains the selected route	Exact request, execution result and separate internal checking receipts; no payment or currency conversion

Switching the selected route never converts an amount or gives one protocol the other's admission or settlement rights. Re-importing a transfer cannot remove earlier checkpoints or silently reprice its work. To change the task or planning terms, start a fresh Alpha cycle and make a new explicit proposal.

Evidence and recovery

Every imported native project, Manager transfer, Jobs transfer and Fleet return is checked by the bundled native receiver. The original UTF-8 bytes, project identity, digests, route and append-only history remain linked. Unknown fields, rehashed invented results, wrong projects, changed routes, rewritten checkpoints and stale-cycle returns are rejected. Digests establish consistency; they do not authenticate the author, prove an actual external controller ran the software, or certify independent qualification.

Browser storage is a local convenience. Keep the downloaded complete journey before leaving or clearing storage. Imports never overwrite a different saved journey with the same project ID. A failed or conflicting save protects the in-memory recovery copy and reports the failure. Use Download protected recovery copy and confirm I kept this recovery file only after keeping the exact file. Download attempts do not clear the protection. Other linked histories cannot replace that copy, and leaving the page triggers a warning until an actual local save succeeds or you explicitly acknowledge keeping the recovery file. After a temporary storage failure, Retry local save validates the actually stored history and uses an atomic comparison before saving the protected extension. It never overwrites a conflicting branch. The complete journey is bounded to 16 MB and 16 retained stages; capacity errors preserve existing history rather than deleting evidence.

This local journey does not fund a job, submit a transaction, commission a live provider or establish production admission. Fleet's internal check is explicitly separate from eligible independent review. Native Linux isolation, physical-host commissioning, live independent participation and settlement require their own evidence. See release readiness and each receiver's operator guide.