lotdpbc.com
Flagship public site, architecture dossier, investor routes, protocols, benchmarks
pages
A gift for Matthew Prince and a foundation for LOTD PBC
Cloudflare-first architecture for a public-benefit internet company.
This page is the public exhibit for LOTD Edge One: a move from isolated Workers to a single edge-native platform where public narrative, operations, data, and observability live under one design language.
7platform services in the initial scaffold
4D1 domains in the target model
4standard queue classes
Why this exists
A public architecture exhibit for the next generation of LOTD PBC on Cloudflare.
PagesWorkersD1R2QueuesDurable ObjectsAccessAnalytics
Flagship surfaces
The public control layer
These routes are the public face of the platform. They turn the company site into an architecture narrative, a contract surface, and a portfolio guide.
api.lotdpbc.com
Public API gateway with standard JSON envelope
worker
learn.lotdpbc.com
Learner-first runtime for adaptive lessons, proofs, trust, and offline-sovereign progress
worker
status.lotdpbc.com
Portfolio status, uptime, incidents, and diagnostics split
worker
assets.lotdpbc.com
Public asset host for protocol artifacts, exports, and share media
r2
search.lotdpbc.com
Cross-property search backed by a shared D1 catalog and ready for Vectorize ranking
worker
Core services
Shared services instead of one-off deployables
The new operating model moves shared concerns like envelopes, rate limits, status, and topology into common services so every new product does not reinvent them.
lotdpbc-pages
pages surface
- /
- /cloudflare-first
- /learner-first
- /future-state
- /kelly-for-all
- /learn
- /benchmarks
- /.well-known/lotd-edge-architecture.json
- /.well-known/lotd-future-state.json
- /.well-known/kelly-for-all.json
api-gateway
worker surface
- /v1/health
- /v1/topology
- /v1/future-state
- /v1/kelly
- /v1/learner/overview
- /v1/learner/profile
- /v1/learner/graph
- /v1/learner/runtime
- /v1/protocol/compiler
- /v1/trust/fabric
- /v1/translate
- /v1/proofs
- /v1/outreach
- /v1/copilot
- /v1/impact
- /v1/network
- /v1/status
- /v1/benchmarks
- /v1/search/query
lotd-learner-runtime
worker surface
- /
- /kelly
- /health
- /manifest.json
- /v1/overview
- /v1/profile
- /v1/graph
- /v1/runtime
- /v1/protocol-compiler
- /v1/trust
- /v1/translate
- /v1/proofs
- /v1/outreach
- /v1/copilot
- /v1/impact
- /v1/network
- /v1/kelly
observability
worker surface
- /status.json
- /incidents.json
- /benchmarks.json
- /internal/status
lotd-assets
worker surface
- /
- /health
- /:key
lotd-search
worker surface
- /
- /health
- /v1/query
lotd-ops-console
worker surface
- /
- /health
Reference stack
The stack is frozen on purpose
Pages, Workers, D1, R2, Queues, Durable Objects, Access, WAF, API Shield, Analytics Engine, and Vectorize are the default path. The goal is less vendor drift and a simpler ops model.
lotd_controllotd_learninglotd_outreachlotd_observability
lotd-public-assetslotd-private-artifactslotd-exports
SessionCoordinatorIdempotencyCoordinatorRateLimitCoordinator
Operating rules
Four rules, one control plane
Edge-first. Origin-minimal. Secure-by-default. Measurable-by-default. Those rules now exist as code, route surfaces, and deploy scaffolding inside the platform repo.