nx_cost_federation_test.nx

nx_cost_federation_test.nx -- how the cost database GROWS AND GROWS, opt-in. The seed lands on a chip, measures it (nx_self_measure_cost), and -- ONLY IF the user opts in -- contributes that profile back to the shared database, through the SAME germination trust gate the seed uses for code: integrity hash + sanity proof + crew-council governance. So: * opted-in + sane -> ADMITTED, the DB gains a real profile for that chip * poisoned (mul<add) -> REJECTED, the shared costs cannot be corrupted * opted-OUT -> stays LOCAL, never leaves the node (consent honored) Across a fleet, the DB grows to characterize every chip Nishi runs on -- our own uops.info, federated, that uops.info itself can never have (sovereign cores, sensors, damaged units). The richer it gets, the better every node optimizes. Known answer: opted-in sane profile admitted (DB grows), poisoned rejected, opt-out kept local -> exit 0.