Command OS — Cloudflare Architecture Review

Architecture

┌──────────────────────────────────────────────────────────────┐ │ PRINCIPAL │ │ Human: Siri / Access-gated board / forwarded mission email │ └───────────────────────┬──────────────────────────────────────┘ ▼ ┌──────────────────────────────────────────────────────────────┐ │ ORAL — SOLE OPERATOR (api.alfred.report) │ │ Cloudflare Worker + Durable Object + D1 │ │ │ │ Session authority → Mission compiler → Evidence ledger │ │ ↓ ↓ ↓ │ │ Independent gate Budget enforcement Agent Memory │ │ ↓ ↓ ↓ │ │ Voice report (TTS via AI Gateway) │ └──────────────┬───────────────────────────────┬───────────────┘ ▼ ▼ ┌──────────────────────────┐ ┌────────────────────────────┐ │ FIELD WORKERS │ │ TRUST │ │ Ephemeral, scoped, │ │ D1 event/state record │ │ replaceable │ │ CF Artifacts (source) │ └──────────────────────────┘ └────────────────────────────┘ ┌──────────────────────────────────────────────────────────────┐ │ BOARD — THIN EDGE (alfred.report) │ │ Static pages + Access-gated inspection │ │ Service binding to ORAL; no local state │ └──────────────────────────────────────────────────────────────┘

Cloudflare Services Used

Workers + Durable Objects

agent-alfred — ORAL operator (missions, sessions, voice, gate)
alfred-report — Board (thin edge, static assets, service binding)

D1

Missions table (tenant_id, version, state, budget, acceptance, evidence)
Voice sessions (SHA-256 hashed tokens, tenant isolation)
Mission events (append-only audit log)

AI Gateway

Profile: alfred
Custom provider: MiMo TTS via custom-mimo
Routing: All LLM calls through gateway

Agent Memory

Namespace: hermes
Profile: alfred
Usage: Fact → skill → forget promotion on mission completion

Artifacts

Namespace: alfred-command
Repos: agent-alfred, alfred-report
Status: Ready, main branch

Cloudflare Access

Authentication: Google IdP + OTP
Protected: Board command routes, ORAL auth bootstrap
Public: Homepage, about, contact, privacy, developers

Service Bindings

Board → ORAL: Direct binding (no public HTTP)
Tenant context: X-Tenant-Id header propagation

Questions

1. Artifacts CI/CD

We have Artifacts repos set up. What's the correct flow for:

Push source to Artifacts → trigger CI Workflow → deploy Worker
Store build artifacts for rollback
Auto-deploy on push

2. AI Gateway Optimization

Routing MiMo TTS through custom provider. Are we:

Using correct endpoint format?
Getting full logging/analytics?
Missing caching, rate limiting features?

3. Agent Memory Best Practices

Using CF Agent Memory for mission promotion. Are we:

Using correct binding pattern?
Getting full semantic search?
Missing memory features?

4. Durable Objects Patterns

Using DOs for mission state. Are we:

Using SQLite storage correctly?
Getting proper concurrency control?
Missing alarms, websockets, or other DO features?

5. D1 Optimization

Missions, sessions, events tables. Are we:

Using proper indexing?
Getting full D1 features (backups, branching)?
Missing D1 capabilities?

6. Service Binding Patterns

Board → ORAL via service binding. Are we:

Propagating tenant context correctly?
Getting proper error handling?
Missing binding features?

7. Auth & Access

Cloudflare Access + JWT verification. Are we:

Using correct JWT verification pattern?
Getting full Access features (service tokens)?
Missing auth capabilities?

8. Secrets Management

Using wrangler secret put. Is there a better way?

CF Secrets Store?
Secret rotation?
Best practices?

9. Monitoring & Observability

What CF features for:

Worker logs and analytics?
Error tracking?
Performance monitoring?
Cost tracking?

10. Unused Services

Should we be using any of these?

CF Queues — async mission processing
CF Pub/Sub — real-time updates
CF Workers AI — local inference
CF Browser Rendering — web scraping
CF Vectorize — semantic search
CF KV — caching
CF R2 — file storage

Command OS — Cloudflare Architecture