Status: pre-launch. This page describes target design; this document does not establish a deployed service.
F3 -- The Polyphenotypic System
Same genome, multiple phenotypes across domains.
In organism terms, a shared constitutional and architectural “genome” can express different external products without changing core principles.
Concept
A polyphenotypic system has:
- one deep structure (invariants, core state, interfaces)
- many context-specific expressions (finance, media, governance, identity, hardware)
This lets one organism adapt to diverse environments while preserving internal coherence.
Skyzai expression pattern
- Shared genome: the pipeline, SPECTRE, invariants, adapter contracts
- Phenotypes: APU, Circle, ReFu, OFN, Aureus, Nexus, Helios, POS, etc.
This is a comparative reuse image, not a custody or product-family classification. apu.bot remains independent; adjacent ventures, including Aureus, retain their own ownership and authority.
Why it matters
- Reuse compounds execution speed
- Governance remains intelligible across products
- Learning in one phenotype can transfer to others
- Failure in one phenotype need not kill the genome
Design tests
A new product proposal should answer:
- Which invariant set governs it?
- Which existing adapters can be reused?
- Which phenotype-specific constraints are novel?
- How will receipts prove metabolic contribution?
Related pages
Historical predecessor wording — retained on 2026-09-28, not active rules
Predecessor passage 1
Each product is not a random startup. It is a phenotype of the same operational DNA.