Status: pre-launch. This page describes target design; this document does not establish a deployed service.

DEV-04 -- Add An Agent

Adding an agent means moving from doctrine to row to runtime to pipeline without breaking source ownership.

File-touch Trace

Step	Layer	Files
1	Doctrine	private caste specification (not reproduced here)
2	Row application	private row-application files (not reproduced here)
3	Runtime rows	`.codex/agents/rows/0X_LX_<caste>.toml`
4	Deployed runtime	`.codex/agents/SPECTRE-<caste>.toml`; `.codex/agents/children/` for child variants
5	Hosted bridge	`.codex/agents/managed_runner.py`; `.codex/agents/relay_axiom.py`
6	Pipeline use	private pipeline chain module, if the chain invokes it directly

Name the caste first. Is this L1 intake, L2 exploration, L3 audit, L4 execution, L5 architecture, L6 compression, or L7 constitution?
Change doctrine only when the row itself is wrong across all organisms.
Change row application for Skyzai-local behavior.
Regenerate or project runtime surfaces from row sources.
Do not teach a generated TOML a fact the row source does not know.
If the agent can stage an irreversible act, it stages an unsigned ProposalEnvelope; it does not sign. A Natural Person retains authority over their own typed private act; a Legal Person acts through lawful external authority and required executors. A public-DAV consequence remains unsigned until the signer(s) required by applicable law, the entity's governing instrument, or a valid competent mandate bind the exact consequence in a complete valid bound PRISM decision receipt; PRISM records and verifies only, and deterministic execution is limited to that exact consequence.

Source path is named.
Runtime path is named.
The typed authority boundary is named if the agent can affect money, identity, memory lineage, external communications, or deployment. The agent still stages an unsigned proposal only.
A test or audit surface is listed before merge.