Generating code is getting cheaper. Deciding what should exist, defining its boundaries, and checking whether it works still take judgement. The work here starts with those questions. Agents help with implementation; architecture, review, and release decisions remain human responsibilities.
Fast is now table stakes. Fast and correct is the edge.
Trust, interoperability, and unit economics shape the architecture. A model can propose an action; explicit contracts, durable state, and policy determine whether the system can carry it out and recover when it fails.
The libraries isolate recurring problems: booking rules, notification templates, API descriptions, credential generation, tool authority, payment and shipping state, and interface interchange. Each has a defined boundary with the application that uses it. Tests and formal checks establish specific properties within that boundary; a consuming product still needs its own validation.
- Elixir and OTP: application libraries, agent security, and Web of Things infrastructure. Each package documents its runtime and supervision needs.
- Ruby and Solidus: payment and shipping extensions for existing shops.
- Rust: NUIF research into interface interchange and measurable conversion loss.
- Ventures: Refpath, Rivure, Diggymon, WoTEx, Orvane, Reloved, and Äger, all in development and described as direction rather than released solutions.
Write the intent and constraints before implementation. Keep decisions replayable where possible, with time and external effects passed through explicit boundaries. Record uncertain outcomes so recovery has a starting point. Review generated code against the same requirements as any other code.
Documentation, contracts, and tests belong beside the implementation. Claims should name what was checked and where the evidence stops.
Bootstrapped by default, built for durable ownership.