Link map

Apply these retargets when the package is published. Anchors use the final package filenames.

inventory row body link as written package target
3 [software house](../notes/definitions/software-house.md) automated-software-houses-with-fixed-llms-appendix-a-definitions.md#software-house
4 [distributed-parametric state](../notes/definitions/representational-form.md) automated-software-houses-with-fixed-llms-appendix-a-definitions.md#distributed-parametric-state
5 [notes and code](../notes/definitions/representational-form.md) automated-software-houses-with-fixed-llms-appendix-a-definitions.md#notes-and-code
6 [definition](../notes/definitions/software-house.md#scope) automated-software-houses-with-fixed-llms-appendix-a-definitions.md#definition
7 [Holding a program theory means sustaining coherent search under delayed feedback](../notes/program-theory-sustains-search-under-delayed-feedback.md) automated-software-houses-with-fixed-llms-appendix-b-arguments.md#holding-a-program-theory-means-sustaining-coherent-search-under-delayed-feedback
8 [Naur's compiler case](../sources/programming-as-theory-building.ingest.md) automated-software-houses-with-fixed-llms-references.md#peter-naur--programming-as-theory-building
9 [one set of documents and one way of reading them, bounded to its time](../notes/naurs-compiler-case-tests-one-historically-bounded-documentation-and-consumption-system.md) automated-software-houses-with-fixed-llms-appendix-b-arguments.md#naurs-compiler-case-tested-one-historically-bounded-document-and-reading-system
10 [The distinction is between formal execution and explicitly formulated criteria](../notes/naur-equates-machine-execution-with-formulated-criteria.md) automated-software-houses-with-fixed-llms-appendix-b-arguments.md#formal-execution-is-not-the-same-as-explicitly-formulated-criteria
11 [Governing a behaviour-changing write therefore requires selection, validation, authorization, and coordination](../notes/continual-learning-requires-governing-behaviour-changing-writes.md) automated-software-houses-with-fixed-llms-appendix-b-arguments.md#behaviour-changing-writes-require-selection-validation-authorization-and-coordination
12 [transition closure of the seed](./reachability-as-closure-under-the-seed-gate.md) automated-software-houses-with-fixed-llms-appendix-a-definitions.md#transition-closure-of-the-seed
13 [Gödel machine](../notes/goedel-machines-are-a-proof-governed-case-of-self-modification.md) automated-software-houses-with-fixed-llms-appendix-a-definitions.md#gödel-machine
14 [Schmidhuber](../sources/goedel-machines-schmidhuber.ingest.md) automated-software-houses-with-fixed-llms-references.md#jürgen-schmidhuber--gödel-machines
inventory row body link as written
1 [the repository's GitHub Discussions page](https://github.com/zby/commonplace/discussions)
2 [companion article](./the-software-house-as-the-unit-of-training.md)
15 [third article](./bootstrapping-the-first-automated-software-house.md)
16 [companion map](./nearest-existing-constructions-to-a-reachability-witness.md)
17 [companion article](./the-software-house-as-the-unit-of-training.md#testable-consequences)
18 [open-domain theory builder may itself become a software house](../notes/an-open-domain-theory-builder-becomes-a-software-house-when-new-domains-require-production-machinery-changes.md)
19 [companion article](./the-software-house-as-the-unit-of-training.md)