Source and provenance

RustEDA's modules have separate source histories and licenses. The superproject's gitlinks identify the exact combination used by a checkout. The public release snapshots for RustROAD, RustEDA flow and Studio record their prior source identities under each module's docs/provenance/source-publication.json.

Existing RustSys and RustSTA public histories remain available. The original RustEDA Common source revision remains reachable because published consumers reference it. New consumers use the current exact HTTPS revision.

Benchmark and verification receipts retain their original tool versions, source hashes, scope, failures and limitations. Updating a README, visual identity or publication snapshot does not create a new equivalence proof or signoff result.

The modules' LICENSE, NOTICE and per-fixture provenance files remain authoritative. Reference executables, design inputs, PDKs and rule decks keep their own licenses. Private development notes and local recovery archives are not shipped with the documentation site. Publication and history cleanup are not legal certification.