AIM Framework glossary
Body Manager
Canonical definition
The reader-facing name for Appetites (A) used in the Minimal Architecture Specification and throughout the treatise where the architectural role of the component (homeostatic-deficit signaller with no stored priors and no upstream channel) is under discussion rather than the Axiom-1 source-taxonomy role. The Body Manager is not a distinct component from A; it is the same Disaggregation Primitive specified under its reading-surface function rather than under its source-taxonomy label. It is introduced in Chapter 4 Section 4.4 in the course of specifying the minimal architecture, and is used in preference to "Appetites" wherever the architectural function (deficit signalling, satiation-on-repair, absence of priors, absence of upstream channel) is the point being made. Use "Appetites" or "A" where the Axiom-1 taxonomic role is the point being made, and "Body Manager" where the architectural function is the point. The two labels denote the same component.
Explanation
The Body Manager is just another name for A, used when we are talking about what the component does in the architecture rather than where it sits in the three-source taxonomy. A signals that the body needs something, scales the signal to how urgent the deficit is, and stops signalling once the deficit is repaired. The Body Manager name makes that job easy to remember: it is the part that manages the body. We call it "Appetites" when we are talking about the three sources of motivation and where A fits among them, and we call it the "Body Manager" when we are talking about how the system is wired and what each component is responsible for. Same component, two labels for two different kinds of discussion.
Epistemic status
Canonical.
Derivation
Related terms
- Appetites (A)
- Disaggregation Primitive
- Dashboard Gauge Principle
- Minimal Architecture Specification
- Decision Hub
- Thinker
- Observer
- Belief Register
- Signed Valuation Principle