@@ -186,6 +186,55 @@ Notes:
186186- apps and APIs should surface this bundle, not only country package versions
187187- a bundle may reuse a previously staged data artifact if compatibility is explicitly certified
188188
189+ ## TRACE export
190+
191+ The internal build manifest and certified runtime bundle remain the operational source of
192+ truth.
193+
194+ TRACE sits on top of those manifests as a standards-based export layer.
195+
196+ ### What gets exported
197+
198+ Country ` *-data ` repos should emit a ` trace.tro.jsonld ` file for each published data
199+ release. That TRO should cover:
200+
201+ - the release manifest itself
202+ - each published artifact hash listed in the release manifest
203+ - the build-time model provenance recorded in the release manifest
204+
205+ ` policyengine.py ` should emit a separate certified-bundle TRO. That TRO should cover:
206+
207+ - the bundled country release manifest shipped in ` policyengine.py `
208+ - the country data release manifest resolved for the certified data package version
209+ - the certified dataset artifact hash
210+ - the certification basis used to allow runtime reuse
211+
212+ ### What TRACE does not replace
213+
214+ TRACE is not the source of truth for compatibility policy.
215+
216+ In particular, TRACE does not decide:
217+
218+ - whether a new model version can safely reuse an existing data artifact
219+ - how ` data_build_fingerprint ` is computed
220+ - which staged artifact becomes a supported runtime default
221+
222+ Those decisions still belong to the country data build manifest and the
223+ ` policyengine.py ` certified runtime bundle.
224+
225+ ### Why we still want it
226+
227+ TRACE adds three things our internal manifests do not provide by themselves:
228+
229+ - a standard declaration format for provenance exchange
230+ - a composition fingerprint over the exact artifacts in scope
231+ - a better external surface for papers, audits, and reproducibility reviews
232+
233+ That is why the recommended design is:
234+
235+ - internal manifests for build/certification control
236+ - generated TRACE TROs for standards-based export
237+
189238## Compatibility rule
190239
191240The architecture should avoid forcing a new data build for every harmless country model release.
0 commit comments