The organism

An organism is your application together with the parts that let it be governed, changed, run and watched. Its code can change itself, and you hold the door. A change is proposed in a sandbox, proven with the toolchain from the earlier parts, shown to whoever has the authority to decide it, applied exactly as approved, expressed on your machine or a fleet, and watched until it holds or rolls back. Every step is a row in a record kept in your repository, so anyone with a clone has the whole story.

The organism is drawn as parts, each with one job, one owner and one way of failing:

• the genome it is made of;
• the record and working memory;
• the nerves between its parts;
• the spine that decides;
• the head and face where people reach it;
• the legs, their hat, hands and voice, which do the work;
• the heart, your application;
• the body it runs on;
• the senses and reflexes that watch it;
• the skin that keeps its secrets.

The organism, part by part draws the map. Each part then has a chapter of its own.

All of it is written in Hale, with the language, the locus model and the claims of the earlier parts. The organism’s own law is a constitution its build checks (Constitutions). Its parts are loci on a typed bus. What it may reach is proven before it runs.

DNA is the building block the organism is assembled from: vendor/dna, the dna::Dna locus and the hale dna commands. It comes last in this part (DNA, the building block), because it is the inside view. You can run and govern an organism without opening it.

What the next part adds. An organism looks after one application and its record. The habitat is the design for what several organisms and the people in them share: isolated records, deliberate sharing between them, who may act and on whose authority, and the standard equipment an organism grows with. It is a design, not yet the tree.