Skip to content

Connect the approved pricing KV namespace #5

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
JimCollinson merged 1 commit into from
Sep 16, 2026
+11 −21
Merged

Connect the approved pricing KV namespace #5

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 7 additions & 21 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -79,27 +79,13 @@ Allow/CORS methods `GET, OPTIONS`. No pricing cache, TTL or expiry header is add
Only the pricing path accesses pricing KV; supply and health retain their original
responses, methods, caches, wallet accounting, RPC order and fallback behavior.

**Not configured for publication:** `wrangler.jsonc` and the deployment workflow
are unchanged. No KV namespace binding/ID, route or secret is added by this work;
without the separately approved binding/data setup pricing returns 503. The two
[API Proposed ADRs](docs/adr/README.md) remain Proposed; local implementation is
not acceptance or release approval.

Minimal **documentation-only** binding example for a separately approved future
`wrangler.jsonc` change (the ID below is a placeholder, not a real namespace):

```json
{
"kv_namespaces": [
{ "binding": "PRICING_KV", "id": "<APPROVED_PRICING_KV_NAMESPACE_ID>" }
]
}
```

This example configures nothing. Resource creation, the real binding, deployment,
producer activation and publication of `pricing:v1` each remain behind the
separate activation approval gate; no secret or deployment configuration changes
are included here.
**Namespace configured:** `wrangler.jsonc` binds `PRICING_KV` to the existing
approved namespace. Deployment, publisher activation and data availability remain
separate steps; availability is not verified until the first approved live run.
Publication remains disabled during setup, and missing or invalid `pricing:v1`
still returns 503. The deployment workflow, routes and secrets are unchanged.
The two [API Proposed ADRs](docs/adr/README.md) remain Proposed; this configuration
change is not ADR acceptance or proof of live publication.

### Circulating supply definition

Expand Down
4 changes: 4 additions & 0 deletions wrangler.jsonc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,10 @@
"enabled": true
},

"kv_namespaces": [
{ "binding": "PRICING_KV", "id": "c4c210fcdf1342678f9fed3710c42486" }
],

// Production domain — enabled by a reviewed commit, never from the
// dashboard. Claims api.autonomi.com away from the former Vercel CNAME.
"routes": [
Expand Down
Loading