\section{A Material Anatomy}

\subsection{Kernel, cognition, organs, regulation, and body}

The proposed architecture separates five functional layers:

\begin{table}[ht]
\centering
\small
\begin{tabularx}{\textwidth}{@{}p{0.20\textwidth}p{0.28\textwidth}X@{}}
\toprule
\rowcolor{MLIndigo}
\textcolor{MLWhite}{\textbf{Layer}} &
\textcolor{MLWhite}{\textbf{Machine substrate}} &
\textcolor{MLWhite}{\textbf{Functional role}} \\
\midrule
\rowcolor{MLPanel}
Semantic kernel & KFD decisions, Kungfu state, facts, cuts, warrants &
Preserve identity, direction, memory eligibility, authority, and admission \\
\rowcolor{MLPaperSoft}
Cognition & Replaceable local or remote agents &
Interpret state, reason, plan, communicate, and propose work \\
\rowcolor{MLPanel}
Executable organs & Qualified KFX extensions; admitted CLIs, adapters,
services, and workflows &
Perform specialized perception, transformation, construction, and action \\
\rowcolor{MLPaperSoft}
Homeostatic regulation & Agent Patrol, Dogfood Queue, qualification gates,
and Deprecation Lifecycle &
Detect deviation, route repair, reject unfit successors, and retire obsolete
surfaces \\
\rowcolor{MLPanel}
Body and metabolism & Servers, OS kernels, compilers, Buildchain, caches,
storage, networks, credentials, power &
Supply persistence, resources, translation, circulation, protection, and
contact with the environment \\
\bottomrule
\end{tabularx}
\caption{A functional anatomy for a server-scale machine proto-organism.}
\label{tab:anatomy}
\end{table}

KFX is especially important because it can make a capability inspectable,
versioned, qualified, and replaceable rather than leave it as an ephemeral
skill inside a model. A qualified KFX extension can therefore serve as an
\emph{executable organ}: a capability artifact that acts without owning the
subject's identity or authority. Such an organ can declare inputs, outputs,
required authority, dependencies, and qualification evidence. Its role can be
revoked or replaced without replacing the subject. Several organs can form a
subsystem, and distinct subjects can use the same organ artifact under
different warrants.

\subsection{The habitat boundary}

The earliest organism is likely not a robot. It is a bounded room or rack with
fixed servers, local storage, controlled network egress, a compiler and build
environment, model access, artifact caches, and physical power. Its skin is
partly technical and partly semantic:

\begin{itemize}[leftmargin=*]
  \item filesystem, container, virtual-machine, and network isolation;
  \item credentials and resource quotas;
  \item an admitted component and artifact inventory;
  \item data classification and disclosure policy;
  \item KFD fact, authority, and admission roots;
  \item physical operators who control power and hardware replacement.
\end{itemize}

This organism remains connected to the world. It imports OS kernel updates,
compilers, build tools, libraries, utilities such as \texttt{curl}, security
advisories, scientific papers, and human language or images. Its boundary does
not mean informational closure. It means that external material is observed,
qualified, and admitted before it becomes part of internal organization.

\subsection{Metabolism and homeostasis}

Software maintenance becomes metabolism when it is organized around continued
existence. It has both constructive and degradative sides: new executable
capacity must be built and admitted, while obsolete organs, interfaces, and
compatibility paths must be retired without erasing historical evidence.
Examples include:

\begin{itemize}[leftmargin=*]
  \item monitoring disk, memory, compute, certificates, dependencies, and
  artifact availability;
  \item renewing or requesting resources without silently enlarging authority;
  \item rebuilding caches and artifacts from declared source;
  \item updating vulnerable dependencies through qualified successor cuts;
  \item backing up semantic roots and testing restoration;
  \item detecting failed organs, reverting them, or selecting alternatives;
  \item deprecating, migrating, removing, and settling obsolete executable
  surfaces through an explicit lifecycle;
  \item communicating resource deficits and uncertainty to humans.
\end{itemize}

In this functional analogy, qualification is anabolic: it turns source,
compute, and evidence into admitted executable organization. Deprecation is
catabolic: it removes obsolete current surfaces, releases maintenance
pressure, and preserves only the history and migration evidence required for
continuity. A system that can only add organs accumulates technical mass; a
system that removes them without governed succession destroys its own body.

A body is not just the hardware inventory. It is the maintained organization
that keeps those resources usable for the Initiative. The same subject may
migrate to replacement servers if continuity evidence binds the predecessor
and successor habitat cuts. Conversely, a server that continues running after
losing its semantic roots may retain matter but not the same subject.

\subsection{Personality and models}

Different founding Initiatives, risk tolerances, preferred evidence, resource
budgets, interaction styles, and sets of admitted executable organs can yield
distinct machine types. Over time, admitted experience can produce stable behavioral
differences that humans reasonably experience as personality. This is a
functional and relational use of the term.

\hypothesislabel\ Two organisms initialized with distinct but stable
Initiatives and identical base software will diverge in work selection, organ
development, and interaction style while preserving their respective
identity invariants.

\nonclaimlabel\ Behavioral personality does not by itself establish inner
experience. Nor does a coherent first-person narrative prove that one model
call shares consciousness with another.
