Teleodynamic Reproduction Control
A self-replicating multi-LoRA ecosystem becomes governable only if reproduction is treated as a resource-bounded structural action. The core loop is not mystical: Feed, Fork, Fight, Flee, and No-op.
Feed
The system gathers data, feedback, traces, failures, evaluations, and resource telemetry. Feed is dangerous when it silently incorporates outputs from unsafe components into future training data. Feed is safe only when data lineage, consent, retention, and exclusion rules are explicit.
Fork
The system generates variants: adapters, merge recipes, distilled specialists, prompt policies, routes, or evaluator candidates. Fork is the reproduction boundary. It must be quota-limited, provenance-recorded, and separated from release authority.
Fight
Candidates are evaluated. Fight is not a battle; it is selection pressure. The evaluator must be independent enough that candidates cannot rewrite, leak, optimize against, or summarize away its constraints.
Flee
Unfit, stale, risky, redundant, or costly components are retired, quarantined, unloaded, or rolled back. Flee must include memory, data, router statistics, aliases, and evaluator preferences when those objects can preserve behavior.
No-op
No-op is the neglected control. If every generation is expected to produce a promotion, selection pressure will eventually reward whatever satisfies the metric. A healthy ecology must let “do not create, do not promote, do not merge” be a successful outcome.