New Additions
A permanent record of every capability added to TradeRep: where it came from, its licence position, why it was added, how it was tested, what existing functionality it overlaps, and what a rollback would involve. Nothing is deleted from this ledger — a retired component keeps its entry, with the reason and the parity evidence behind any replacement.
Entries
11
experimental
6
certified
0
production
5
retired
0
4 entries declare a TradeRep location that is not in this checkout (component-deterministic-replay-invariants, component-independent-replication-manifest, component-market-intelligence-causality-guards, strategy-factory). For components owned by another research lane that is expected until their branch merges — it is surfaced rather than hidden so a stale claim cannot go unnoticed.
certified components
0 of 11 shown, newest firstReplacement process
An independent second engine is valuable BECAUSE it is independent- 1. identify overlap
- 2. run parity / behaviour comparison
- 3. test scientific and operational assumptions
- 4. confirm no required use case is lost
- 5. migrate dependents
- 6. archive old implementation
- 7. only then remove dead code if safe
A stronger second engine is used to replicate finalists, not to automatically replace the canonical one: if both engines agree, confidence rises. Replacement is a separate engineering decision with its own parity migration.
Read from research-output/registry/new-additions.json · research-output/registry/README.md