How to Build Around an Open Theorem Without Claiming It
Ambitious mathematical software can formalize the missing object, prove surrounding machinery, and record evidence while keeping the unresolved crux mechanically open.
Long-form thinking from the layer beneath the interface: secure AI infrastructure, microVMs, Rust, distributed systems, product, and the human work of building difficult things.
Ambitious mathematical software can formalize the missing object, prove surrounding machinery, and record evidence while keeping the unresolved crux mechanically open.
Showing 18 essays
Ambitious mathematical software can formalize the missing object, prove surrounding machinery, and record evidence while keeping the unresolved crux mechanically open.
Once objects have stable identities, a registry has to preserve namespace state, relationships, atomic changes, reconciliation, and reachability—not just blobs.
A portable suspension needs addressed state, addressed dependencies, explicit host contracts, and fresh authority when execution moves.
A useful research repository keeps negative results, pre-declares what would change the plan, and treats instruments that cannot fail as bugs.
Running a real AI compile-and-inference pipeline in the browser changes storage, memory, concurrency, and verification from backend concerns into product architecture.
When every valid execution path produces the same bytes, memory, scheduling, SIMD, and fallback decisions stop leaking into the caller's contract.
Content addressing gives delegated AI results durable identity and tamper evidence, but correctness still requires recomputation, attestation, or a stronger proof.
A hash identifies bytes. A useful object address has to survive harmless changes in representation without pretending every kind of equivalence is the same.
A destructive command exposed two hard problems: defining complete deletion in an evolving system and preserving cryptographic identity as one connected set.
A Rust ownership mistake in MVM's ext4 builder multiplied peak memory, and the fix required changing the shape of the pipeline.
Logs describe events. Provenance records who authorized them, why they happened, and which later decisions depended on them.
MicroVM latency only means something when the stopwatch includes preparation, verification, activation, first useful work, and cleanup.
A restored microVM can inherit computation, but it needs a fresh identity, fresh channels, and a newly admitted security contract.
Security promises need a threat model, an enforcement mechanism, and a witness that breaks when the mechanism does.
MVM removes the routable guest NIC and puts network authority behind a host-controlled vsock boundary.
Prompt rules are not a security boundary. Agent runtimes need enforceable capabilities, isolated execution, mediated I/O, and a deliberately small blast radius.
The advances in AI are incredible, but the most important systems will disappear into ordinary life.
Memories of my father and the derivative meaning of snacks.
Try another phrase or return to all topics.