Where it ends, and where it plugs in

This is the whole loop, and it is deliberately one machine, one GitHub account, one Linear workspace, one harness. Three things it does not ship each have a known file name that either exists or does not: a runtime that runs a beat somewhere else, an identity per role instead of one account, and wherever you want the status block sent. If the file is absent the factory does the local thing and keeps going. One page: contracts/extending.md.

contracts/ is the layer beneath this one, starting with what-is-a-factory.md, the normative definition every other document here should be explainable in terms of. Everything in that directory changes what the machine does when you edit it; nothing else does.