v0.2.0 — weeks-depth platform edge
v0.2.0 — weeks-depth platform edge
Release date: 2026-08-14
Scope
The free-path gateway was already public, git-connected, and honest about empty upstreams
(v0.1.0). This release makes the edge look like a platform engineer built it: request journal,
complete OpenAPI with typed failure examples, a limiter protocol with optional Redis, OTel as a
seam, and upstream URLs that stay unconfigured unless env says otherwise.
What shipped
| Week | Surface |
|---|---|
| 1 | In-process journal (GET /v1/platform/journal), complete OpenAPI, typed 401/429/413/415 tests, README curl block on the correct status path |
| 2 | RateLimiter + InMemoryLimiter + optional RedisLimiter, ADR-0002, decision counters on /metrics |
| 3 | Tracer / NullTracer / optional OTel console exporter, optional *_URL validation, status UI treats unconfigured as first-class, CASESTUDY + ADR-0003 |
Hosted claim (unchanged honesty)
- Live: https://pax-ai-gateway.vercel.app (Vercel, per function instance)
- Correct status path:
/v1/platform/status(not/v1/status) - Fixture key:
dev-local(published, not a credential) - Public env leaves four upstream URLs,
GATEWAY_REDIS_URL, andGATEWAY_OTELempty - Fly remains PLANNED
- No claim of deployment-wide 429 on the public host
Verify
curl -s https://pax-ai-gateway.vercel.app/health
curl -s -H "X-API-Key: dev-local" https://pax-ai-gateway.vercel.app/v1/platform/status
curl -s -H "X-API-Key: dev-local" "https://pax-ai-gateway.vercel.app/v1/platform/journal?limit=5"
curl -s https://pax-ai-gateway.vercel.app/metrics
curl -s https://pax-ai-gateway.vercel.app/openapi.json