PONSSystem architecture
The website, durable state, isolated runner and public publisher have separate responsibilities.
Website and public research
The default application is Next.js on Vercel. It serves the interface, documentation, repository catalogue and prepared briefs. The catalogue is bundled from data/registry.json, so source discovery does not depend on a paid model service or database.
Server routes expose research reads and the request/build API. Public configuration is an explicit allowlist of capability flags, public repository metadata and configured public addresses. Provider keys and service authentication secrets are not returned to browsers.
Durable application state
Requests, votes, jobs, activity, receipts and settled credits require persistent storage. The alternative Cloudflare runtime binds D1 and uses the included migrations. The current Node/Vercel runtime has no durable database adapter.
Accounting depends on atomic database batches and unique records. A replacement adapter must preserve reservation, receipt and settlement behavior under concurrent requests. A local in-memory store or a string environment variable named DB is not an equivalent integration.
Trusted account gateway
The web application accepts a stable, app-scoped opaque account ID only when a trusted gateway authenticates the session and supplies a matching server secret. User identity, request ownership and wallet connection are separate concepts.
The gateway must replace caller-supplied identity headers. Browser code does not receive the gateway secret. Operator settlement and runner callbacks use separate bearer credentials and do not inherit ordinary account privileges.
Runner and sandbox
The runner is a separate long-running Node service with a durable SQLite job database and event outbox. It authenticates bounded jobs, creates an E2B sandbox, checks out pinned source and calls the configured OpenRouter model through a tool loop.
Untrusted source executes inside the sandbox. Model, publisher and application secrets remain in the trusted runner. The web process does not execute submitted repositories.
Public evidence and source publication
Sanitized event records travel from the runner to the application. The trusted publisher writes job-scoped source changes to an isolated GitHub branch. A final artifact exposes the patch, command exit codes, model and limitations while withholding raw prompts and terminal output.
This publication path does not merge into the default branch or run a mainnet deployment. Software release, a project’s token launch and any treasury execution remain separate operational steps.
Funding boundary
Verified native fee receipts become ledger records. Usable provider credit is recorded only after an authorized settlement step. A request reserves settled USD credit before dispatch, then a confirmed completion settles the reported cost.
The current source does not automatically convert proceeds, top up providers, create tokens or execute FORKD buybacks. A configured address or connected flag is not evidence that these operations occurred.