Loading public metadata…
Captured scope
A frozen capture is not evidence that today's public heads were polled.
Schedules can be delayed or disabled. Check the latest workflow attempt; this page reports the last published receipt, not the success of a later failed run.
Python snapshots, Git time series
The Python processor reads public data, selects useful fields and saves plain JSON. The scheduled job commits only real changes. Read successive versions or their diffs to see prices, counts and positions move.
See changes over time Latest world snapshot · Repository snapshot
python3 scrape.py
git log -p -- snapshots/world.jsonGit is the history. No browser SQL runtime is needed. Optional metadata SQLite download can be queried locally. There is no hosted SQL API.
Machine-readable entrypoints and integrity
- Catalog index + database SHA-256
- Generation manifests, partition hashes and column definitions
- Captured repository JSON / CSV
- Observed public repository state
- Measured status summaries CSV
- Separate freshness receipt
- Query presets / SQL schema
- Artifact hashes / SHA256SUMS
- Metadata coverage and withheld-payload boundaries
Bounded measured-workflow observations
Reported independent exercises, bound to public-safe summary hashes—not re-executed or universally certified by this catalog. A successful local bridge does not clear the withheld full carrier or change accepted authority.
Captured repositories
Carried commits never silently become live heads. New public repositories discovered by polling appear in observed state; their file content is not retroactively added to this frozen generation.
| Repository | Carried commit | Paths | Public observation | License detection |
|---|
Scope is not authority, compatibility or availability
Exact full carrier: WITHHELD
Clear for exact publication: false. The public artifact is an allowlisted metadata/query projection, not the raw/private payload. No plaintext or encrypted-full download is offered.
Payload availability · Withholding policy · Policy and separately cleared future assets. A known hash is not a download offer.
Checkpoint, normative content and implementation candidate are distinct
Historical parser outcomes such as accepted, refused, or unverified_history are bounded measurements under a pinned captured witness. Legacy declarations remain separate from RAPP1 declarations. They do not establish current runtime interoperability, source ratification, signature trust, or activation.
Authority pins · Capture provenance · Component licenses and rights · Rebuild and cold-start instructions