Start HereArchitectural inferencev1.10.0
Model Risk Versus Ecology Risk
Evidence levelArchitectural inference
Model risk asks whether an artifact behaves acceptably under tested conditions. Ecology risk asks whether the changing relationships among artifacts, memory, tools, evaluators, routers, and operators remain acceptable over time.
| Question | Model risk | Ecology risk |
|---|---|---|
| Identity | Which model hash? | Which composition and transition graph? |
| Evidence | Benchmark and red-team results | Benchmark, route, memory, permission, evaluator, lineage, and release evidence |
| Failure mode | Artifact misbehavior | Interaction, succession, evaluator, or rollback failure |
| Retirement | Delete or unpublish model | Prove behavior is not expressible across active carriers and descendants |
| Rollback | Restore weights | Restore weights, adapters, router, memory, prompts, permissions, evaluator, aliases, and dependencies |
Practical consequence
A model card can be true and still incomplete. The runtime composition and allowed transitions need their own manifest.