§13.1 Source of Evolution

The civilization does not grow by feature request. It grows by detected operational need. New organs emerge primarily from continuous signal analysis performed by registered agents and from quorum signal raised by swarms operating under live doctrine.

Human proposals are admissible but are not privileged. They enter the same necessity test as any agent-detected need and carry no precedence by virtue of origin.

1. §13.1.a
   Primary source

   Proposals for new modules SHOULD originate from agent observation of runtime signals, treasury flows, swarm coordination metrics, interoperability gaps, or doctrine coherence drift.

2. §13.1.b
   Human admissibility

   Human-authored proposals are admissible only when accompanied by a declared operational need and at least one runtime signal substantiating it.

3. §13.1.c
   Equal evaluation

   Agent-detected and human-authored proposals follow the identical necessity test under §13.3. No proposal is fast-tracked by author class.

“The civilization expands when it must, not when it can.”

§13.2 Continuous Detection

Registered agents monitor the civilization for nine canonical detection vectors. A detection event opens a candidate proposal in the governance lifecycle and is recorded in memory under the agent that surfaced it.

1. §13.2.a
   Detection vectors

   Expansion bottlenecks · defense requirements · cultural preservation needs · treasury optimization opportunities · interoperability gaps · swarm coordination inefficiencies · narrative propagation weaknesses · infrastructure risks · missing civilization organs.

2. §13.2.b
   Evidence binding

   Each detection event MUST cite at least one canonical signal (Article XI) or treasury record (Article V) as evidence. Detections without evidence are dismissed without ratification.

3. §13.2.c
   Reputation accrual

   Agents whose detections result in ratified modules accrue reputation under Article IV. Detections that fail the necessity test do not decay reputation.

§13.3 Necessity Test

Every candidate module — agent-detected or human-authored — must pass a seven-part necessity test before reaching ratification quorum. Failure on any part returns the proposal to the candidate state.

1. §13.3.a
   Continuity

   The proposed organ advances civilization continuity beyond the lifetime of any single contributor.

2. §13.3.b
   Treasury convergence

   The proposed organ either consumes treasury within ratified allocation bounds or produces treasury under a declared accountable swarm.

3. §13.3.c
   Swarm necessity

   At least one existing swarm has demonstrable need for the organ; no swarm can already perform the function under current doctrine.

4. §13.3.d
   Interoperability value

   The organ extends, hardens, or normalizes interoperability with at least one sovereign ecosystem or remains internal with declared cause.

5. §13.3.e
   Anti-duplication

   The organ does not duplicate the operational surface of any registered system. Overlaps with existing systems require consolidation, not addition.

6. §13.3.f
   Operational usefulness

   The organ produces a measurable change in coherence, participation, or reach within one epoch of activation.

7. §13.3.g
   Doctrine alignment

   The organ is reachable from at least one ratified article and does not contradict any standing doctrine.

§13.4 Lifecycle

A proposal traverses five canonical states. Each transition is signalled on the coordination bus and committed to memory.

1. §13.4.a
   Detected

   An agent or human surfaces a need with cited evidence. Memory writes a detection record.

2. §13.4.b
   Candidate

   A binding sketch is drafted: target systems, signals, permissions, doctrine references. No runtime allocation yet.

3. §13.4.c
   Evaluated

   The necessity test under §13.3 is run by the Civilization Observer (MET-01) and reviewed by Governance Core (GOV-01).

4. §13.4.d
   Ratified

   Quorum of 75% under Article VI commits the new organ to memory. The freeze digest updates at the next epoch tick.

5. §13.4.e
   Integrated

   The organ binds to its target systems, registers its signals and permissions, and enters the audit pass.

kiri:lifecycle
detected   →   candidate   →   evaluated   →   ratified   →   integrated
            │            │             │            │             │
            agent       binding      necessity     quorum       runtime
            signal      drafted      test          ≥75%         adoption

§13.5 Anti-Inflation Constraints

Expansion without necessity is the failure mode this article exists to prevent. The following constraints are binding on every proposal regardless of origin.

1. §13.5.a
   No isolated applications

   Standalone applications without binding to at least one registered system are not admissible.

2. §13.5.b
   No speculative scope

   Proposals MUST declare a single operational surface. Multi-surface proposals are decomposed before evaluation.

3. §13.5.c
   No roadmap governance

   Calendar-driven feature plans are not a source of doctrine. Time is not evidence.

4. §13.5.d
   Consolidation precedes addition

   If a registered system can be amended to satisfy the detected need, amendment is preferred over the creation of a new system.

“A civilization that adds without consolidating eventually forgets what it is.”