@bytesbrains/cruise-worker 0.0.0-stage → 0.12.1

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -1,3 +1,38 @@
-# Temporary Holding Version
+# @bytesbrains/cruise-worker
 
-This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
+The [Cruise](https://gitlab.com/bytesbrains-oss/cruise) Worker, built and ready to deploy to
+your own Cloudflare account: one OpenAI-compatible endpoint in front of every model provider,
+with per-project keys, budgets that stop, and a cost ledger for every request.
+
+This is the deployable artifact, not a library. It holds:
+
+| | |
+|---|---|
+| `worker/` | The bundle `wrangler deploy` produces, for `no_bundle` deploys |
+| `migrations/` | Every migration as SQL, in order |
+| `wrangler.template.jsonc` | A complete config for this version: bindings, compatibility date, vars |
+| `index.mjs` | The same paths and settings, for scripts that write their own config |
+
+## Deploy
+
+```sh
+npm install @bytesbrains/cruise-worker@<version>
+cp node_modules/@bytesbrains/cruise-worker/wrangler.template.jsonc wrangler.jsonc   # fill in every <…>
+npx wrangler d1 migrations apply <database> --remote   # always before the Worker
+npx wrangler deploy
+```
+
+**Pin an exact version.** A release can carry migrations, and its Worker reads their columns, so
+the order is always: apply that version's migrations, then deploy that version's Worker.
+
+For a deploy that creates everything for you, see the `cruise` CLI
+(`npx @bytesbrains/cruise cloudflare deploy`). To run Cruise without Cloudflare, see the
+Docker image. Both run this same bundle.
+
+## In a script
+
+```js
+import { mainModule, workerDir, migrationsDir, compatibilityDate, bindings } from "@bytesbrains/cruise-worker";
+```
+
+Apache-2.0.

package/index.d.ts

@@ -0,0 +1,14 @@
+export declare const packageDir: string;
+export declare const workerDir: string;
+export declare const mainModule: string;
+export declare const migrationsDir: string;
+export declare const compatibilityDate: string;
+export declare const compatibilityFlags: readonly string[];
+export declare const bindings: {
+  readonly d1: readonly string[];
+  readonly kv: readonly string[];
+  readonly r2: readonly string[];
+  readonly workflows: readonly { binding: string; className: string }[];
+  readonly analyticsEngine: readonly string[];
+  readonly versionMetadata: "CF_VERSION_METADATA";
+};

package/index.mjs

@@ -0,0 +1,41 @@
+// packages/worker/src/index.ts
+import { existsSync } from "node:fs";
+import path from "node:path";
+
+// selfhost/worker-config.ts
+var COMPATIBILITY_DATE = "2026-08-13";
+var COMPATIBILITY_FLAGS = ["nodejs_compat"];
+var STORAGE = {
+  d1: { DB: "cruise" },
+  kv: { CACHE: "cruise-cache" },
+  r2: { BATCH_FILES: "cruise-batch-files" },
+  workflows: { BATCH_WORKFLOW: { name: "cruise-batch", className: "BatchWorkflow" } },
+  analytics: { METRICS: { dataset: "cruise_requests" } }
+};
+
+// packages/worker/src/index.ts
+var here = import.meta.dirname;
+var root = existsSync(path.join(here, "package.json")) ? here : path.join(here, "..");
+var packageDir = root;
+var workerDir = path.join(root, "worker");
+var mainModule = path.join(root, "worker", "index.js");
+var migrationsDir = path.join(root, "migrations");
+var compatibilityDate = COMPATIBILITY_DATE;
+var compatibilityFlags = COMPATIBILITY_FLAGS;
+var bindings = {
+  d1: Object.keys(STORAGE.d1),
+  kv: Object.keys(STORAGE.kv),
+  r2: Object.keys(STORAGE.r2),
+  workflows: Object.entries(STORAGE.workflows).map(([binding, w]) => ({ binding, className: w.className })),
+  analyticsEngine: Object.keys(STORAGE.analytics),
+  versionMetadata: "CF_VERSION_METADATA"
+};
+export {
+  bindings,
+  compatibilityDate,
+  compatibilityFlags,
+  mainModule,
+  migrationsDir,
+  packageDir,
+  workerDir
+};

package/migrations/0001_virtual_keys.sql

@@ -0,0 +1,102 @@
+-- Virtual per-project API keys (#4). Spec: docs/v0.md §3 component 2, §4.
+--
+-- D1 rather than KV, deliberately: revocation needs read-after-write consistency,
+-- and a revoked key that keeps working for a propagation window is a security
+-- control that does not work.
+
+-- Tenants exist from the first migration even while there is exactly one value,
+-- per v0.md §2 — a product that happens to have one tenant is not allowed to defer this.
+CREATE TABLE tenants (
+  id         TEXT PRIMARY KEY,
+  name       TEXT NOT NULL,
+  created_at TEXT NOT NULL DEFAULT (datetime('now'))
+);
+
+CREATE TABLE projects (
+  id        TEXT PRIMARY KEY,
+  tenant_id TEXT NOT NULL REFERENCES tenants(id),
+  slug      TEXT NOT NULL,
+  name      TEXT NOT NULL,
+
+  -- Which gateway this project's traffic goes to. A property of who is calling,
+  -- never a per-request flag anyone can get wrong (v0.md §4). Retention-off is the
+  -- default, and logging is what a project opts into.
+  gateway TEXT NOT NULL DEFAULT 'gw-sensitive'
+    CHECK (gateway IN ('gw-sensitive', 'gw-internal')),
+
+  -- Behaviour at the budget ceiling (v0.md §1). User-facing projects degrade and keep
+  -- serving; internal pipelines refuse loudly because nobody is waiting.
+  -- v0 ships only the refusal path — full degradation needs auto mode — so this
+  -- records intent that phase 1b will honour.
+  budget_behaviour TEXT NOT NULL DEFAULT 'refuse'
+    CHECK (budget_behaviour IN ('degrade', 'refuse')),
+
+  created_at TEXT NOT NULL DEFAULT (datetime('now')),
+  UNIQUE (tenant_id, slug)
+);
+
+CREATE TABLE virtual_keys (
+  id         TEXT PRIMARY KEY,
+  tenant_id  TEXT NOT NULL REFERENCES tenants(id),
+  project_id TEXT NOT NULL REFERENCES projects(id),
+  name       TEXT,
+
+  -- Non-secret. Identifies a key in logs and error messages without the log
+  -- becoming a place credentials live.
+  prefix TEXT NOT NULL UNIQUE,
+
+  -- SHA-256 of the whole key. A fast hash is the correct choice here precisely
+  -- because these are not passwords: the secret is 192 bits of CSPRNG output, so
+  -- there is no low-entropy guessing attack for a KDF to slow down.
+  key_hash TEXT NOT NULL,
+
+  created_at     TEXT NOT NULL DEFAULT (datetime('now')),
+  created_by     TEXT,
+  last_used_at   TEXT,
+  revoked_at     TEXT,
+  revoked_by     TEXT,
+  revoked_reason TEXT,
+
+  -- Enforced per project in phase 1 (#7).
+  rate_limit_per_min INTEGER,
+  budget_usd_month   REAL,
+
+  -- Carried from the first migration, enforced later. Decided 2026-08-13: adding
+  -- this to a live ledger at the moment an open-signup product needs it is the
+  -- expensive version of the same change.
+  account_rate_limit_per_min INTEGER
+);
+
+CREATE INDEX idx_virtual_keys_project ON virtual_keys (project_id);
+CREATE INDEX idx_virtual_keys_tenant ON virtual_keys (tenant_id);
+
+-- Allowed models. No rows means unrestricted; a row set means exactly that set.
+-- Capabilities are recorded per model rather than per upstream (v0.md §3), so a key
+-- that needs tools must never be routed to a model that silently lacks them.
+CREATE TABLE key_allowed_models (
+  key_id TEXT NOT NULL REFERENCES virtual_keys(id) ON DELETE CASCADE,
+  model  TEXT NOT NULL,
+  PRIMARY KEY (key_id, model)
+);
+
+-- Traffic classes this key may declare (#6). A key cannot label its own traffic
+-- as something it was not scoped for, or the segmented report in v0.md §7 is fiction.
+CREATE TABLE key_allowed_classes (
+  key_id TEXT NOT NULL REFERENCES virtual_keys(id) ON DELETE CASCADE,
+  class  TEXT NOT NULL,
+  PRIMARY KEY (key_id, class)
+);
+
+-- Audit. #13 requires that opting a project into logging records who did it and
+-- why; key issue and revocation belong in the same place for the same reason.
+CREATE TABLE audit_events (
+  id      TEXT PRIMARY KEY,
+  at      TEXT NOT NULL DEFAULT (datetime('now')),
+  actor   TEXT NOT NULL,
+  action  TEXT NOT NULL,
+  subject TEXT NOT NULL,
+  reason  TEXT,
+  detail  TEXT
+);
+
+CREATE INDEX idx_audit_subject ON audit_events (subject);

package/migrations/0002_seed_projects.sql

@@ -0,0 +1,16 @@
+-- Originally the first deployment's tenant and its projects, seeded here so the
+-- schema could be exercised from day one with one tenant modelled as one of many
+-- (v0.md §2).
+--
+-- The open-source release seeds nothing: a deployment starts with no tenants and
+-- creates its own with `npm run tenant:provision`, which writes the project and its
+-- budget in one batch. The file stays so migration numbering matches every
+-- database that has already applied it. Tests load equivalent rows from
+-- test/fixtures/seed.ts instead.
+--
+-- Gateway and budget behaviour per v0.md §1 and §4 still describe what a project
+-- should be given: retention-off (`gw-sensitive`) is the default and logging is the
+-- exception a project opts into; user-facing projects degrade at the ceiling while
+-- internal pipelines refuse loudly.
+
+SELECT 1;

package/migrations/0003_budgets.sql

@@ -0,0 +1,43 @@
+-- Budgets and spend accounting (#7). Spec: docs/v0.md §1, §3 component 6, §4.
+--
+-- This is the feature the agentic pipelines are switched off waiting for, so the
+-- bar is a correctness property rather than a dashboard setting.
+--
+-- Two halves, deliberately. The gateway's cost node is the authoritative stop
+-- because it sees real upstream cost; these tables are what makes the soft threshold
+-- *readable by the Worker*, which #7 requires and a dashboard-only budget cannot
+-- provide. They also carry the per-project degrade-or-refuse decision.
+
+CREATE TABLE project_budgets (
+  project_id TEXT PRIMARY KEY REFERENCES projects(id),
+
+  period TEXT NOT NULL DEFAULT 'day' CHECK (period IN ('day', 'month')),
+
+  -- Warn here; keep serving. Null means no soft threshold.
+  soft_usd REAL,
+  -- Stop here. Null means uncapped, which is the state that made the pipelines
+  -- unsafe to switch on in the first place.
+  hard_usd REAL,
+
+  updated_at TEXT NOT NULL DEFAULT (datetime('now')),
+  updated_by TEXT
+);
+
+-- Running spend per project per period. Written from response usage rather than
+-- from what the client submitted: v0.md §7 found devstral reporting 1,230 prompt tokens
+-- for a ~10-token message, so the ledger must attribute what the upstream bills.
+CREATE TABLE project_spend (
+  project_id    TEXT NOT NULL REFERENCES projects(id),
+  period        TEXT NOT NULL CHECK (period IN ('day', 'month')),
+  period_start  TEXT NOT NULL,
+  spend_usd     REAL NOT NULL DEFAULT 0,
+  request_count INTEGER NOT NULL DEFAULT 0,
+  updated_at    TEXT NOT NULL DEFAULT (datetime('now')),
+  PRIMARY KEY (project_id, period, period_start)
+);
+
+-- Starting limits were seeded here for the first deployment's projects. The
+-- open-source release seeds none (see 0002): `tenant:provision` writes a budget in
+-- the same batch as the project, because a project with no budget row is uncapped
+-- and serving. Keep a new project's first cap deliberately low: a cap that is wrong
+-- stops a job, while an absent cap is the unbounded liability v0.md §1 describes.

package/migrations/0004_tenant_isolation_and_integer_money.sql

@@ -0,0 +1,49 @@
+-- Two corrections from review of PR #23.
+--
+-- 1. Tenant isolation was not enforced by the schema.
+--
+-- `virtual_keys` carried its own `tenant_id` alongside `project_id`, with a
+-- foreign key on each and nothing tying them together. A row could name tenant A
+-- and a project belonging to tenant B, and every later authorization decision
+-- trusts that column. v0.md §2 calls tenant isolation a day-one constraint rather than
+-- phase-4 work, and a constraint the database does not enforce is a convention.
+--
+-- Fixed by deleting the redundancy rather than constraining it. A key belongs to
+-- a project, and a project belongs to a tenant; there is now exactly one path to
+-- that fact, so the two cannot disagree. A composite foreign key would also have
+-- worked, but it keeps a denormalisation whose only purpose was to save a join
+-- that `resolveVirtualKey` already performs.
+DROP INDEX idx_virtual_keys_tenant;
+ALTER TABLE virtual_keys DROP COLUMN tenant_id;
+
+-- 2. Money was stored as REAL.
+--
+-- The hard cap is the correctness property of #7 — it is the single feature the
+-- agentic pipelines are switched off waiting for — and binary floating point
+-- cannot represent most decimal money exactly. Accumulating thousands of small
+-- per-request costs into a REAL lets the total drift from the sum of what the
+-- providers actually billed, in either direction, which is both a cap that can be
+-- crossed and a ledger that cannot be reconciled against an invoice (#5).
+--
+-- Everything monetary is now an integer count of **micros**: 1 USD = 1,000,000.
+-- Cents would be too coarse, since a single cheap request can cost a small
+-- fraction of one. Conversion happens at the boundaries and nowhere else.
+--
+-- Done now because there is no production data. Doing it later means migrating a
+-- live ledger, which is the same argument this repo has already made twice.
+
+ALTER TABLE project_budgets ADD COLUMN soft_micros INTEGER;
+ALTER TABLE project_budgets ADD COLUMN hard_micros INTEGER;
+UPDATE project_budgets
+   SET soft_micros = CAST(ROUND(soft_usd * 1000000) AS INTEGER),
+       hard_micros = CAST(ROUND(hard_usd * 1000000) AS INTEGER);
+ALTER TABLE project_budgets DROP COLUMN soft_usd;
+ALTER TABLE project_budgets DROP COLUMN hard_usd;
+
+ALTER TABLE project_spend ADD COLUMN spend_micros INTEGER NOT NULL DEFAULT 0;
+UPDATE project_spend SET spend_micros = CAST(ROUND(spend_usd * 1000000) AS INTEGER);
+ALTER TABLE project_spend DROP COLUMN spend_usd;
+
+ALTER TABLE virtual_keys ADD COLUMN budget_micros_month INTEGER;
+UPDATE virtual_keys SET budget_micros_month = CAST(ROUND(budget_usd_month * 1000000) AS INTEGER);
+ALTER TABLE virtual_keys DROP COLUMN budget_usd_month;

package/migrations/0005_model_prices.sql

@@ -0,0 +1,42 @@
+-- Prices, so the Worker can turn a response's token usage into spend (#1, #7).
+--
+-- The Worker has to compute cost itself rather than read it from gateway logs,
+-- because `gw-sensitive` has logging off (v0.md §4) — which is the default and covers
+-- every project carrying end-user content. A budget that only works on the
+-- logging gateway would not restrain the traffic it exists to restrain.
+--
+-- This is a stopgap sized to #7's needs, not the cost ledger. #5 owns
+-- reconciliation against Custom Costs and provider invoices, and v0.md §8 warns that a
+-- stale table produces attribution that looks authoritative and is wrong — so
+-- `source` and `as_of` are recorded from the start, and unknown models are
+-- counted rather than guessed at.
+--
+-- Micros per million tokens, integer. See migration 0004 for why nothing
+-- monetary is a float.
+
+CREATE TABLE model_prices (
+  model             TEXT PRIMARY KEY,
+  input_micros_per_mtok  INTEGER NOT NULL,
+  output_micros_per_mtok INTEGER NOT NULL,
+  source            TEXT NOT NULL,
+  as_of             TEXT NOT NULL,
+  updated_at        TEXT NOT NULL DEFAULT (datetime('now'))
+);
+
+-- Requests whose model has no price. Counted rather than silently costed at
+-- zero, because a budget that under-counts is the failure mode that matters:
+-- it lets spend past a cap while reporting the cap as unbreached.
+CREATE TABLE unpriced_usage (
+  model          TEXT NOT NULL,
+  period_start   TEXT NOT NULL,
+  request_count  INTEGER NOT NULL DEFAULT 0,
+  input_tokens   INTEGER NOT NULL DEFAULT 0,
+  output_tokens  INTEGER NOT NULL DEFAULT 0,
+  PRIMARY KEY (model, period_start)
+);
+
+-- Workers AI, the only upstream reachable today without a BYOK provider key, and
+-- what step 0 was measured against. Everything else lands here as projects
+-- migrate and #5 takes over.
+INSERT INTO model_prices (model, input_micros_per_mtok, output_micros_per_mtok, source, as_of) VALUES
+  ('workers-ai/@cf/meta/llama-3.3-70b-instruct-fp8-fast', 290000, 2250000, 'cloudflare-published', '2026-08-13');

package/migrations/0006_budget_reservation.sql

@@ -0,0 +1,38 @@
+-- Atomic budget reservation (#7), from review of PR #24.
+--
+-- The previous shape read spend, decided, called the upstream, and recorded cost
+-- afterwards. Two problems followed from the gap between the read and the write.
+--
+-- Concurrent requests could all pass the check before any of them recorded, so
+-- the cap could be exceeded by `concurrency × cost-per-request`. That was
+-- measured and documented rather than fixed, on the argument that an agentic
+-- loop is sequential and therefore already tightly bounded — which is true, and
+-- was the wrong place to stop, because product traffic is the concurrent case
+-- and v0.md §1 is explicit that spend now rises with marketing rather than engineering.
+--
+-- And because spend was only recorded after the response, a failure in that path
+-- meant spend was never counted at all — so the cap drifted upward silently and
+-- every later request was served against a stale total.
+--
+-- Reserving first fixes both. A request takes its reservation atomically before
+-- the upstream call and reconciles to actual cost afterwards; if reconciliation
+-- never happens, the reservation stands and the system fails closed rather than
+-- open.
+
+ALTER TABLE project_budgets
+  ADD COLUMN reserve_micros INTEGER NOT NULL DEFAULT 50000;  -- $0.05
+
+-- Reservations that were never reconciled, so the gap between what was held and
+-- what was actually billed is visible rather than inferred. A reservation that
+-- is never released is a small permanent overcharge against the cap; one that is
+-- released twice is a hole in it. Both need to be countable.
+CREATE TABLE reservation_failures (
+  id           TEXT PRIMARY KEY,
+  at           TEXT NOT NULL DEFAULT (datetime('now')),
+  project_id   TEXT NOT NULL,
+  reserved     INTEGER NOT NULL,
+  stage        TEXT NOT NULL,
+  detail       TEXT
+);
+
+CREATE INDEX idx_reservation_failures_project ON reservation_failures (project_id, at);