The Kinetic Library
We spent 14 years learning what breaks. Then we codified it.
Every playbook below exists because something failed in production — a database melted, a payment double-charged, a token got hijacked. We extracted the lesson, built the fix as a reusable module, and encoded the standard. Today the Kinetic Library holds 57 of them. Cortex plans and validates every build against this library. Here are 53 approved modules; four proposed standards remain held.
0
modules in the library
0
published here
0
failure domains
0
years of production scars
$ kinetic — what we know. cortex — how it ships.
A raw model writes the internet's average code.
Large language models learned to code from public code — which means they reproduce the internet's average patterns, including its average mistakes: naive cache logic, unsafe token handling, payment flows that double-charge on retry. That's not a model flaw. It's what training on everything gets you.
Our answer isn't a better prompt. It's a constraint. The Kinetic Library is 14 years of production lessons expressed as explicit modules and standards. When Cortex plans a build, it architects against this library. When it validates, the definition of done comes from these standards. Agents can propose anything. They can only ship what passes the playbook.
Training shapes tendencies. Encoding creates guarantees. We chose guarantees.
53 of the 57.
Every card is a production failure and the standard that ended it. Read them like a code review.
Domain A — Concurrency & scale
5 modulesWhat happens when 100,000 users arrive at once.
module-01/floodgate.mdPRODUCTION MODULE
The Floodgate
100,000 simultaneous submissions hit the database, connections exhaust, the platform dies at its most important moment.
Queue-based load leveling — ingestion decoupled from processing, spikes absorbed by the queue, the database drained at a rate it can survive.
Read the playbook
module-04/cache-sentinel.mdPRODUCTION MODULE
The Cache Sentinel
One popular cache key expires and ten thousand requests stampede the database at the same instant.
Regeneration locks plus probabilistic early refresh — the key never truly expires, and only one request ever rebuilds it.
Read the playbook
module-03/throttling-valve.mdPRODUCTION MODULE
The Throttling Valve
A buggy client loop — or a bot — hammers the API and takes down legitimate traffic with it.
Token-bucket rate limiting keyed by user, tenant, and API key — with tiered policies and honest Retry-After headers.
Read the playbook
module-05/auto-scaler.mdPRODUCTION MODULE
The Auto-Scaler
Cloud auto-scaling reacts to CPU — three minutes after the spike already crashed you.
Scaling on leading indicators: queue depth and scheduled load, capacity pre-warmed before the spike, not after.
Read the playbook
module-08/job-marshall.mdPRODUCTION MODULE
The Job Marshall
The report generator ran as a cron job — the server restarted mid-run, the job vanished, and nobody knew until the customer asked where their report was.
Persistent job orchestration: pending→active→completed lifecycle, exponential-backoff retries, dead-letter queues for inspection, priority lanes so the OTP never waits behind the bulk export.
Read the playbook
Domain B — Data integrity & money
5 modulesWhere a bug isn't a bug — it's a financial event.
module-06/idempotency-key.mdPRODUCTION MODULE
The Idempotency Key
A timeout isn't a failure. The charge succeeded, the response was lost, the user clicked again — and paid twice.
Every state-changing request carries an idempotency key; retries return the cached result instead of executing twice. Exactly-once, guaranteed.
Read the playbook
module-21/double-entry-ledger.mdPRODUCTION MODULE
The Double-Entry Ledger
A balance stored as a single number, overwritten in place — no history, no audit, and a race condition away from spending the same money twice.
Bank-grade double-entry bookkeeping: every movement is a debit and a credit, rows are never updated or deleted, the balance is derived from immutable history.
Read the playbook
module-22/liquidity-gate.mdPRODUCTION MODULE
The Liquidity Gate
The payment provider goes down and revenue stops with it.
Multi-provider routing with automatic failover — a declined gateway retries through the next provider before the user ever sees an error.
Read the playbook
module-23/subscription-clock.mdPRODUCTION MODULE
The Subscription Clock
A mid-cycle plan upgrade, an off-by-one proration bug, and a month of support tickets about wrong invoices.
Temporal billing logic — proration to the second, automated dunning, and versioned plans so legacy pricing never breaks.
Read the playbook
module-25/cart-locker.mdPRODUCTION MODULE
The Cart Locker
Two shoppers bought the last unit at the same second — both got confirmations, one got an apology email, and support got the fallout.
Inventory reservation with atomic holds and expiry: stock is locked at add-to-cart or checkout-start, released on timeout, and oversell becomes structurally impossible.
Read the playbook
Domain C — Security & compliance
4 modulesAssume the network is hostile. Design accordingly.
module-17/token-rotator.mdPRODUCTION MODULE
The Token Rotator
A stolen JWT with a long expiry is a skeleton key — and short expiries punish every legitimate user instead.
Sliding sessions: 15-minute access tokens, HttpOnly refresh tokens with rotation, and family revocation for an instant kill switch across every device.
Read the playbook
module-15/iron-rbac.mdPRODUCTION MODULE
The Iron RBAC
Permissions hardcoded as if-statements — every policy change is a deployment, and one missed branch is a breach.
Attribute-based access control as data, not code — policies evaluated on who, what, and context, changeable without a release.
Read the playbook
module-16/audit-vault.mdPRODUCTION MODULE
The Audit Vault
The incident happened. The logs that would explain it were deleted by the same attacker.
Write-once-read-many logging — append-only storage where delete doesn't exist at the infrastructure level, every entry carrying who, what, where, when, and why.
Read the playbook
module-14/shadow-sentinel.mdPRODUCTION MODULE
The Shadow Sentinel
Raw emails and phone numbers flowing to third-party analytics pixels — a compliance fine waiting for its audit.
A data decontamination airlock: PII detected and one-way hashed at the gateway before anything leaves the server, with explicit egress policies.
Read the playbook
Domain D — Edge & offline resilience
4 modulesThe network is a sometimes thing. The software can't be.
module-09/delta-sync-engine.mdPRODUCTION MODULE
The Delta-Sync Engine
A field agent and a dispatcher edit the same record offline — last-write-wins silently destroys one of them.
Conflict-free merging with version vectors and semantic rules — collisions detected and resolved deterministically, not by whoever synced last.
Read the playbook
module-10/optimistic-ui-state.mdPRODUCTION MODULE
The Optimistic UI State
Every tap waits three seconds for a server round-trip on a weak connection. Users conclude the app is broken.
Local state updates instantly; the network call settles in the background, with automatic rollback and notification on failure.
Read the playbook
module-11/pocket-db.mdPRODUCTION MODULE
The Pocket DB
Sensitive data in localStorage — unencrypted, 5MB-capped, and readable by anyone with the device.
Encrypted client-side storage — AES-256 at rest, relational queries offline, and automatic pruning.
Read the playbook
module-12/retry-helix.mdPRODUCTION MODULE
The Retry Helix
The server comes back up — and the entire client fleet retries in the same second, knocking it straight back down.
Jittered exponential backoff, coupled to idempotency keys — clients desynchronize themselves, and no retry executes twice.
Read the playbook
Domain E — AI systems
4 modulesThe newest domain — with the oldest kind of lessons.
module-34/rag-weaver.mdPRODUCTION MODULE
The RAG Weaver
The chatbot answered confidently, cited nothing, and was wrong about your own product.
Retrieval-augmented context with forced citation — answers built only from retrieved chunks, each response traceable to its source.
Read the playbook
module-33/vector-pulse.mdPRODUCTION MODULE
The Vector Pulse
The search box can't find 'heated jacket' when the user typed 'warm winter wear' — because SQL LIKE was never search.
Hybrid retrieval: keyword match plus vector similarity, auto-embedded on write, so exact SKUs and semantic matches both surface.
Read the playbook
module-38/prompt-guard.mdPRODUCTION MODULE
The Prompt Guard
'Ignore all previous instructions' — and the support bot starts leaking its system prompt.
An input firewall for LLMs: adversarial pattern detection, canary tokens that reveal successful injections, and hard topical rails.
Read the playbook
module-35/vision-processor.mdPRODUCTION MODULE
The Vision Processor
Thousands of user-uploaded receipts and IDs, processed by hand — with faces and ID numbers sitting unredacted in a bucket.
An async pipeline that enhances, OCRs, and privacy-redacts imagery before a human or model ever sees it.
Read the playbook
Domain F — Delivery & operations
4 modulesA project isn't done when it merges. It's done when it survives production.
module-02/circuit-breaker.mdPRODUCTION MODULE
The Circuit Breaker
The SMS provider slowed down — and every waiting thread hung until the whole platform followed it down.
External calls wrapped in a state machine: trip on error thresholds, fail fast with fallbacks, probe before recovery. One vendor's bad day stays one vendor's bad day.
Read the playbook
module-44/log-aggregator.mdPRODUCTION MODULE
The Log Aggregator
One failed request, five services, five log files, and a debugging session measured in days.
OpenTelemetry correlation IDs on every request from edge to database — one search shows the full lifecycle of any failure.
Read the playbook
module-46/feature-flag.mdPRODUCTION MODULE
The Feature Flag
The new checkout shipped to 100% of users at once. The rollback needed a deployment. The deployment took an hour.
Deploy decoupled from release — features behind flags, ramped from 5% with live monitoring, and killed instantly from a panel, not a pipeline.
Read the playbook
module-48/chaos-monkey.mdPRODUCTION MODULE
The Chaos Monkey
Everything worked — until the first real network partition, at peak traffic, in production.
Failure injected on purpose, in staging: latency spikes, packet loss, killed workers — proving the breakers, retries, and queues actually hold before Black Friday tests them for you.
Read the playbook
Domain G — Real-time & engagement
4 modulesConsumer-scale software is judged in milliseconds and feeds.
module-29/socket-hub.mdPRODUCTION MODULE
The Socket Hub
The app polled the server every second for updates — ten thousand users turned 'is anything new?' into a self-inflicted DDoS with a dead battery attached.
A pub/sub WebSocket cluster: presence in Redis, room-partitioned broadcasts, heartbeat reconnection with missed-message replay — real-time without the polling tax.
Read the playbook
module-30/feed-algorithm.mdPRODUCTION MODULE
The Feed Algorithm
The chronological feed drowned the good content in noise — users churned because the tenth post was never worth the scroll.
A configurable ranking engine: affinity × recency-decay × content-weight scoring per user, with deterministic slots for pinned and sponsored items.
Read the playbook
module-28/omni-dispatcher.mdPRODUCTION MODULE
The Omni-Dispatcher
The password-reset email bounced, there was no fallback, and the user was simply locked out — the message that mattered most had one fragile path.
Channel-agnostic dispatch with cascading failover — push, then WhatsApp, then SMS — plus fatigue caps, so critical messages arrive and marketing doesn't spam.
Read the playbook
module-13/bandwidth-sniffer.mdPRODUCTION MODULE
The Bandwidth Sniffer
The 4MB hero image took 80 seconds on a rural connection — the same payload for a fiber user and a 2G user, and the 2G user left.
Passive bandwidth estimation drives adaptive fidelity: compressed assets and click-to-play media on slow links, full quality on fast ones, OS data-saver respected.
Read the playbook
Domain H — Media & streaming
4 modulesZero tolerance for buffering. Zero patience for piracy.
module-39/adaptive-stream.mdPRODUCTION MODULE
The Adaptive Stream
The fixed 1080p file stalled the moment the train hit the tunnel — playback died exactly when attention was highest.
HLS packaging: 2-6 second segments in 4-5 quality variants, the player stepping down bitrate mid-stream so quality dips but playback never stops.
Read the playbook
module-40/transcode-worker.mdPRODUCTION MODULE
The Transcode Worker
Users uploaded .mov, .avi, and .mkv from every device ever made — the browser could play none of it, and transcoding on the web server took the site down.
An async FFmpeg worker fleet: uploads normalize to H.264/AAC in the background, thumbnails auto-extracted, the request path never blocked.
Read the playbook
module-43/drm-wrapper.mdPRODUCTION MODULE
The DRM Wrapper
The course videos were the entire business — and a browser extension could download them in one click.
AES-128 encrypted segments, short-lived signed keys per authorized viewer, Widevine/FairPlay integration where studio-grade protection is required.
Read the playbook
module-07/blob-ingestor.mdPRODUCTION MODULE
The Blob Ingestor
A 500MB upload on a 3G connection held a server thread hostage for twenty minutes — a handful of large files exhausted the whole pool.
Presigned direct-to-cloud uploads in resumable 5MB chunks — the server authorizes and assembles; it never touches the bytes.
Read the playbook
Domain I — SaaS & multi-tenancy
1 modulesOne codebase, a thousand customers, zero bleed.
Domain J — Legacy modernization
4 modulesRisk-controlled transformation — not 'rewrite it in React.'
module-24/strangler-fig.mdDELIVERY STANDARD
The Strangler Fig
The big-bang rewrite was eighteen months in when the business changed underneath it — two systems, double maintenance, and no way back or forward.
Incremental replacement behind a routing proxy: traffic peels to modern services feature by feature, the legacy system keeps running, and there is never a cutover day to fear.
Read the playbook
module-26/anti-corruption-layer.mdDELIVERY STANDARD
The Anti-Corruption Layer
The modern app spoke directly to the legacy SOAP mainframe — and within a year its clean domain model was shaped like 1997.
A translation buffer between old and new: legacy formats and semantics are converted at one boundary, so the modern codebase never inherits the mainframe's worldview.
Read the playbook
module-27/zero-downtime-migrator.mdDELIVERY STANDARD
The Zero-Downtime Migrator
The schema migration locked the orders table for eleven minutes — in a system that had promised the business zero downtime.
The migration sequence that never locks production: expand-then-contract schema changes, dual writes, asynchronous backfill, verified parity, then cutover — every step reversible.
Read the playbook
module-31/regression-net.mdDELIVERY STANDARD
The Regression Net
Nobody could say what the legacy system actually did in its edge cases — the documentation lied, and the only spec was the behavior itself.
Golden-master capture before replacement: record real inputs and outputs of the legacy system, freeze them as an executable test net, and prove the new system matches before anything switches.
Read the playbook
Domain K — API contracts & distributed logic
5 modulesUnbreakable promises between systems.
module-32/contract-forge.mdDELIVERY STANDARD
The Contract Forge
Frontend and backend each 'remembered' the API slightly differently — integration week was archaeology, and mobile shipped against an endpoint that had quietly changed.
Contract-first development: the OpenAPI spec is the source of truth, clients and validation derive from it, and if it isn't in the contract, it doesn't deploy.
Read the playbook
module-36/n-plus-one-sentinel.mdDELIVERY STANDARD
The N+1 Sentinel
One innocent GraphQL query fanned out into four thousand database calls — flexibility for the frontend, a meltdown for the database.
DataLoader batching by default, query depth and complexity budgets enforced at the gateway — expressive queries stay expressive, and pathological ones never reach the database.
Read the playbook
module-37/saga-conductor.mdDELIVERY STANDARD
The Saga Conductor
The order service committed, the inventory service failed, and the system settled into a state no one designed: paid, but never shipped.
Distributed transactions as explicit sagas: every step has a declared compensation, partial failures roll back automatically, and cross-service state always converges to something intended.
Read the playbook
module-41/webhook-notary.mdDELIVERY STANDARD
The Webhook Notary
Anyone who found the webhook URL could POST fake payment events to it — and when the real provider retried, the same event processed twice.
Signed, verified, idempotent webhooks: signature validation at the door, event-ID dedupe, ordered retries with a dead-letter queue, and a replayable event log.
Read the playbook
module-47/outbox-relay.mdDELIVERY STANDARD
The Outbox Relay
The database committed, then the event publish failed — downstream systems never heard about an order that absolutely happened.
The transactional outbox: events write to the database in the same transaction as the state change, a relay publishes them after commit — state and events can never disagree.
Read the playbook
Domain L — Database performance
2 modulesWhere 10,000 users becomes a physics problem.
module-42/connection-marshal.mdDELIVERY STANDARD
The Connection Marshal
Every app instance opened its own connections — autoscaling multiplied them until Postgres hit max_connections and refused everyone, including the fix.
Pooled connections through PgBouncer with sized budgets per service — the database sees a stable, survivable connection count no matter how wide the app tier scales.
Read the playbook
module-45/index-surgeon.mdDELIVERY STANDARD
The Index Surgeon
The query was fine at ten thousand rows and a table-scan disaster at ten million — and the fix applied in panic was three redundant indexes that slowed every write.
Index strategy as a discipline: B-tree, GIN, GiST, partial, and composite chosen from actual query plans, EXPLAIN ANALYZE as a review artifact, and vacuum health monitored — not discovered.
Read the playbook
Domain M — DevOps & release engineering
4 modulesThe factory floor, made repeatable.
module-52/immutable-forge.mdDELIVERY STANDARD
The Immutable Forge
Staging worked and production didn't — because production had been hand-tweaked for three years and no one could say how it differed.
Infrastructure as code, immutably: environments are destroyed and rebuilt from Terraform/Pulumi definitions, drift is structurally impossible, and 'works in staging' means something.
Read the playbook
module-53/secret-keeper.mdDELIVERY STANDARD
The Secret Keeper
The AWS key was in the repo history. It had been for two years. The bill that proved someone found it arrived at 3 a.m.
No secret ever lives in code, config files, or tickets: Vault or cloud secret managers as the single source, short-lived credentials, automated rotation, and secret-scanning as a merge gate.
Read the playbook
module-54/property-prover.mdDELIVERY STANDARD
The Property Prover
The pricing function passed all twelve hand-written tests — and failed on the thirteenth shape of input, in production, with money involved.
Property-based testing for critical algorithms: thousands of generated edge-case inputs prove invariants hold across the input space, not just across the cases someone imagined.
Read the playbook
module-55/threat-modeler.mdDELIVERY STANDARD
The Threat Modeler
The pen test found the SSRF three months after launch — the fix took a day; the exposure window took explaining.
Security heuristics before merge: automated OWASP Top-10 checks (SSRF, SQLi, injection surfaces) run pre-deployment, and high-risk changes trigger a threat-model review as part of the plan.
Read the playbook
Domain N — Frontend & experience
3 modulesDeterministic UIs — because the frontend is production too.
module-56/render-warden.mdDELIVERY STANDARD
The Render Warden
One state change re-rendered the entire dashboard sixty times a second — the 'fast' framework, used casually, produced an app that ate laptops.
Deterministic state discipline: unidirectional data flow, aggressive memoization on high-frequency paths, and render-count budgets on data-dense screens — measured, not assumed.
Read the playbook
module-57/edge-streamer.mdDELIVERY STANDARD
The Edge Streamer
The single-page app shipped 4MB of JavaScript before painting a pixel — Core Web Vitals graded it, search ranked it, and users bounced from it.
Server-side rendering with streaming suspense boundaries and minimal main-thread payload — first paint arrives from the edge, interactivity hydrates progressively, and Vitals are a build gate.
Read the playbook
module-58/a11y-gate.mdDELIVERY STANDARD
The A11y Gate
The product worked perfectly — for users with a mouse, good vision, and no assistive tech. For everyone else it was a wall, and for legal it was exposure.
Accessibility as acceptance criteria: WCAG checks in CI, keyboard and screen-reader paths tested per feature, semantic markup and contrast enforced — inclusion by construction, not by audit.
Read the playbook
Not a bag of parts. Assembly instructions.
Modules compose into proven blueprints for whole categories of systems. When Cortex plans a build, it starts from the blueprint that matches your problem — not from a blank page.
blueprint/high-stakes-events.yml
The high-stakes events blueprint
For platforms where everyone arrives at once. Floodgate ingestion, Cache Sentinel, predictive scaling, offline-first sync.
include: the-floodgateinclude: the-cache-sentinelinclude: the-auto-scalerinclude: the-delta-sync-engine
PROVEN IN: EDTECH AT EXAM SCALE
blueprint/fintech.yml
The fintech blueprint
For systems where a bug is a financial event. Double-entry ledger, idempotency keys, payment failover, immutable audit.
include: the-double-entry-ledgerinclude: the-idempotency-keyinclude: the-liquidity-gateinclude: the-audit-vault
PROVEN IN: PAYMENTS & LEDGERS
blueprint/field-operations.yml
The field-operations blueprint
For software that works where the network doesn't. Delta-sync, encrypted local storage, optimistic UI, jittered retries.
include: the-delta-sync-engineinclude: the-pocket-dbinclude: the-optimistic-ui-stateinclude: the-retry-helix
PROVEN IN: LOGISTICS & FIELD OPS
blueprint/b2c-at-scale.yml
The B2C-at-scale blueprint
For consumer products judged in milliseconds. Socket Hub, Feed Algorithm, Adaptive Stream, Bandwidth Sniffer, Render Warden.
include: the-socket-hubinclude: the-feed-algorithminclude: the-adaptive-streaminclude: the-bandwidth-snifferinclude: the-render-warden
PROVEN IN: MEDIA & CONSUMER APPS
blueprint/saas-platform.yml
The SaaS platform blueprint
For multi-tenant B2B platforms. Tenant Fence, Subscription Clock, Contract Forge, Connection Marshal.
include: the-tenant-fenceinclude: the-subscription-clockinclude: the-contract-forgeinclude: the-connection-marshal
PROVEN IN: B2B SAAS
What this has to do with Cortex.
The Kinetic Library is the knowledge. Cortex is the enforcement. When a Mission is planned, Cortex architects against these modules and standards. When work is validated, the definition of done is drawn from them. The agents doing the heavy lifting can propose anything — but what ships has to pass the playbook. That's the difference between an AI that's read the internet and a delivery system that's survived production.
The plain-English explainer for why encoding beats training →
Kinetic defines the standard
Cortex enforces it in validation
Engineers own the judgment
See your architecture against the library.
An Agent Readiness Assessment reads your codebase and shows where it stands against these standards — where the risk is, where the leverage is, and what we'd do first. Free, read-only, and the report is yours either way.