Notes on local AI, typed capabilities and the tools we build. https://machinefabric.com/blog/feed.xml 2026-08-20T00:00:00Z MachineFabrichttps://machinefabric.com/ https://machinefabric.com/assets/apple-touch-icon.png https://machinefabric.com/blog/deconstruct-software-case-for-machinefabric.html 2026-06-13T10:00:00Z 2026-06-13T10:00:00Z

Local AI should not live inside monolithic apps or vague agents. It should be packaged as small, concrete, typed utilities that can be composed into real workflows.

https://machinefabric.com/blog/cartridge-small-program.html 2026-06-07T00:00:00Z 2026-08-20T00:00:00Z

A cartridge owns a typed operation. The host supplies routing, lifecycle, progress, and composition with other cartridges.

https://machinefabric.com/blog/fourth-axis.html 2026-05-18T00:00:00Z 2026-05-18T00:00:00Z

MachineFabric now supports generic Cap URNs more precisely. The new fourth axis lets the system reason about tools that preserve file type at runtime, which improves routing for cases like decimate without hard-coded special cases.

https://machinefabric.com/blog/pick-the-destination-not-the-app.html 2026-05-13T10:00:00Z 2026-05-13T10:00:00Z

Most file menus still ask the wrong question: which app opens this file? We think the operating system should ask what you want the file to become, then route the transformation through a formal typed capability graph.

https://machinefabric.com/blog/capdag-cartridge-protocol.html 2026-03-01T10:30:00Z 2026-08-20T00:00:00Z

Bifaci carries frames between cartridge processes. CapDAG gives those processes a typed, inspectable contract for dispatch and composition.

https://machinefabric.com/blog/hello-world.html 2026-01-18T11:44:34Z 2026-05-07T00:00:00Z

For thirty years your operating system has answered the same question: which app opens this file? MachineFabric answers a better one — what do you want this file to become? — and lets you pick the destination while the planner finds the route.