ReferenceDemonstratedv1.10.0
Source Report Concept Map
Evidence levelDemonstrated
The package now preserves uploaded reports, public-safe summaries, public pages, and .uai memory records. This page maps those reports into reusable site concepts.
v1.8.0 schematic · source-report concepts
The reports now feed the public system map.
Raw reports remain in /docs. Public pages use bounded concepts: transition graphs, adapter reproduction, persistence reservoirs, evaluator drift, execution-time controls, and human-incentive boundaries.
Self-replication reportsmitosis · meiosis · deprecation · containment
Multi-LoRA reportsadapter reproduction · stack activation · reservoirs
4Fs / teleodynamic reportsfeed · fork · fight · flee · no-op
Mutualism reportshuman incentives · exit rights · capability transfer
Browser / tiny model reportsWASM · WebGPU · local adapters · cache reset
Public site expansionanatomy · composition · evolution · control · reference
| Report theme | Public concept pages |
|---|---|
| Self-replicating modules | Algorithmic Reproduction Taxonomy, Execution-Time Alignment Boundaries |
| Multi-LoRA apex threat | Apex Threat Pattern From the Source Reports, Merge-State Backdoors |
| 4Fs / code beading / model breeding | Open-Ended Evolution Without Autonomy, Edge Browser Ecology |
| Aggressive mutualism / mutualist persistence | Human Incentive Safety Boundary, Persona Parasitology Boundaries |
| Cognitive-virus defenses | Cognitive Warfare and Mutualism Synthesis |
Evidence rule
Reports are source dossiers. They inform site interpretation, but the site still labels each public claim according to the evidence ladder.