Rule-ROM Ecosystem
Philo describes principles. Verification happens in code, artifacts, and applications.
| Domain | Role |
|---|---|
| Rule-ROM | Registry of projects and publication boundaries |
| Decima-8 | v3 physics, runtime, .d8p format, IDE, and benchmarks |
| Bakery | Architect tools for building and auditing personalities |
| Whaler | First applied family: market tape, event sensor, and trading contour |
| C-SAFE | Verification and audit |
| PKI | Signatures and artifact provenance |
Publication Boundary
A verifiable contract does not require publishing all intellectual property. The format, runtime physics, hashes, and verification method may be open while a particular bakery, source and validation tapes, and application rules remain private.
This boundary matters for personality: a user can know what is executed and verify that a .d8p is unchanged without automatically receiving its creation recipe.