Cards
- Mutable physical assembly hits a wall: you need not just a declarative config but also environment…
- Rollback in the physical world means disassembly. The cost of reverting a physical deployment is…
- Immutable physical assembly works only for a small class of tasks today. But its existence may…
- Software deploys in seconds, hardware in days or weeks. This time difference is not a bug but a…
- Procurement must become an API. Ordering components programmatically is a prerequisite for closing…
- Simpler approach: build from scratch every time, dismantle the old version. Components from…
- How does the system measure the current state of the physical environment? Sensors, cameras, human…
- How to formally define acceptable tolerance between desired and actual physical state? Software has…
- How to orchestrate multiple builders with different capabilities, speeds, and vendors? The…
- Physical builders are non-deterministic — parts may not arrive, walls may be uneven, connectors may…
- A declarative config alone does not determine the build plan. The plan also depends on the current…
- A physical builder rebuilds reality to match the user's description, probably with some acceptable…
- Open question: NixOS flakes provide reproducibility and composition for describing agents, but the…
- A Continuous Assembly platform connects pluggable builders, each with its own capabilities. The set…
- In an agent's description, the boundary between software and hardware is an implementation detail,…
- The environment changes on its own, not only through CA. Therefore CA must be able to measure and…
- Continuous Assembly requires two layers: a declarative description of desired state and a…
- In research, what you failed to arrive at matters more than what you did — dead ends map the…
- Continuous Assembly is CI/CD for the physical world: a commit to a repo describing equipment…
- An AI agent is always physical — at minimum it runs on hardware. Yet CI/CD only automates…