Harnesses, Models and Portability
Outlined, not yet written
The argument is settled and the chapter is scheduled. Published chapters land roughly every two weeks.
- Treating the harness as replaceable infrastructure
- Keeping skills and workflows out of any single vendor's format
- What breaks when you swap the model underneath
- Open weights and the compliance argument for portability