Boundary
ModelBreeder.com is the positive engineering site. It teaches how to build useful model ecologies: small specialists, adapter descendants, local runtimes, fitness proofs, release packets, provenance, and human-strengthening workflows.
Cognivirus.com is the right destination for the negative case: system pathology, misuse framing, warning-heavy scenarios, coercive dependency, and doing it wrong.
Editorial routing rule
FUNCTION route_topic(topic)
IF topic.focus IN ["benefit", "architecture", "implementation", "learning", "local sovereignty", "fitness proof"]
RETURN "ModelBreeder.com"
END IF
IF topic.focus IN ["warning", "misuse", "pathology", "negative case", "cautionary scenario"]
RETURN "Cognivirus.com"
END IF
RETURN "ModelBreeder.com with a short scope note"
END FUNCTIONPositive default
When a page needs a boundary, use a scope note. Do not lead with pessimism. Explain the constructive pattern and provide a short link to the risk-focused counterpart only when it helps readers place the topic.
Source reports used for this guide
These reports are preserved verbatim in the site archive. The guide above is an editorial synthesis and may narrow, qualify, or reorganize claims from the source material.