ArcForges AI

ArcForges' AI execution runtime on Cloudflare Workers and Workflows. The repository currently contains a private Hello Agent: a selected Workers AI model calls one validated greeting tool, then writes a final reply. The greeting tool uses the published ArcForges protobuf package.

The intended product architecture keeps the only model/tool loop in a Workflow. Cloud owns business authorization, D1 transactions, approvals and accounting under the current runtime authority. This bootstrap demonstrates the runtime, package boundary, build and deployment path; it does not implement the full product harness, streaming, R2 routes or commercial behavior.

Quick start

Install Node 24.21.0 LTS with npm 11.19.0, then:

npm ci --ignore-scripts
npm run hooks
npm run check
npm run build

These commands need no Cloudflare account. Default tests run pure offline units in Node. Workflow engine and bundle runtime tests are separate explicit local opt-in commands, never CI gates. The build produces artifacts/candidate/, including the deployable bundle, configuration, hashes, provenance, licenses and runtime SBOM.

The toolchain pins TypeScript 7.0.2, Wrangler 4.135.0 and @arcforges/proto 1.0.0-ci.44.1. See development for tool compatibility, local health testing and dependency updates.

Hello Agent

1. Validate { "name": "ArcForges" } before admitting a model call.
2. Ask @cf/openai/gpt-oss-20b for exactly one say_hello function call using the model's Chat Completions binding profile.
3. Validate the tool and its arguments, then encode/decode the published request and response protobuf messages to produce Hello, ArcForges!.
4. Supply that result to the model and require a bounded final text reply with no further tools.

Each model step disables automatic retries and allows at most 1,024 output tokens with a 90-second step timeout. Names are limited to 80 Unicode code points and 256 UTF-8 bytes, with no ASCII control characters. Whitespace and Unicode are preserved. Unsupported tools, changed arguments and incomplete/malformed model output fail the Workflow.

The Worker has no public route, workers.dev URL or preview URL. Remote runs are started and inspected through Cloudflare's authenticated Workflow API. The local GET /health handler reports the build identity; it does not call a model or prove inference.

Delivery

PRs validate source, targeted offline units, dependencies/security and the sealed Worker build. Main deploys that same candidate and creates a prerelease containing the candidate and provider deployment record. CI does not invoke a Workflow or model, test the compiled runtime, poll health or download public release bytes. Deployment completion is distinct from live runtime acceptance. See validation policy.

This is a deployable Worker, not an npm library. Versions are automatic: 0.1.0-ci.<run-number>.<run-attempt>. No manual version edit, npm account, NuGet key or PGP key is needed.

Before the first merge, complete Cloudflare setup and deployment. That guide covers account settings, the GitHub cloudflare environment, live verification and recovery. Validation evidence distinguishes completed local checks from pending external gates.

Repository guide

• Bootstrap plan
• Development and hooks
• Project licence declarations and checks
• Reuse records and actual artifact provenance
• Cloudflare setup, release and recovery
• Contributing, conduct and security
• AGPL-3.0-only license and third-party notices

Build candidates also carry the WP02.04 build identity, sealed from independent source/producer/lock inputs.