work

I build things that hold up: web, app, ecom, enterprise, agent, orchestration.

Twenty-five years of shipping, distilled into one idea: the code an agent writes needs guardrails, memory, and an adversary. This page is the legible half - the range, the proof, and three case studies.

The range

The Creadev.org services vocabulary, in plain words.

Web and app development

Front to back, from a static lander to an app with real state.

Back end and infrastructure

APIs, data, and the seams that keep them predictable.

IT contracting

Embedded work on someone else's stack, shipped and documented.

SEO and performance

Real head tags, real sitemaps, real load budgets - not adjectives.

Tools and automation

Deterministic gates that fail loudly instead of generated green.

Migrations and rescues

Inherited trees made honest again, with the drift named at cause.

AI and agent engineering

Memory, contracts, and adversarial QA for agent-written code.

Proof

Every number ships with a source and a date, or it does not ship. VERIFIED was re-derived from the trees; DIRECTION is a stale figure kept only as a signal about what to measure.

ClaimSourceStatus
83 public crashtest packs across 10 family reposcounted from the pack manifests, 2026-11-17VERIFIED
25 family members in the governed rosterthe govstruct manifestVERIFIED
Nine npm-live toolsnpm view, 2026-11-17VERIFIED
Deterministic exit codes: 0 clean, 1 refusal, 2 usagethe family's own docsVERIFIED
The full discovery set ships from the baked outputa real freestruct buildVERIFIED
290 adversarial attack scenariosa strategy chat (stale; the verified ledger reads 269 rows)DIRECTION

Case studies

Proof of thinking, not just proof of shipping. Problem, Contract, Verification.

Zero-drift fleet governance

Problem
The crosslink mesh was hand-typed across many repos and drifted. Three copies of project data disagreed.
Contract
One manifest of members, one render surface per deployment shape, one doctor that verifies every adopter serves the same truth.
Verification
The doctor gates each adopter's pin; the rendered surfaces are statically emitted, so a bot reads a plain anchor; the registry is checksummed.

Adversarial agent hardening

Problem
Agent-written code ships faster than a human reviews, and the classic failure is a handler that echoes hostile input or leaks a stack frame.
Contract
The harness attacks the real handlers in-process, and every scenario returns exactly one verdict: refused, exploited, or bounded (which must name an owner and a bound, or it is a finding).
Verification
The pixels are pinned by a read-only gate over a committed visual ledger; the baked output is audited; the ledger runs deterministic pass-for-pass.

Git-backed agent memory

Problem
An agent that forgets every session cannot be trusted with real work, and memory that lives only in a vendor's database cannot be audited or moved.
Contract
The memory is markdown files in your own repository, read when a session starts and written before it ends, so git history becomes the memory lineage. The interface is MCP.
Verification
The brain is inspectable with cat; the memory survives leaving the tool; the boot stone carries a verified checksum sidecar.