Artifact · captured 2026-09-25 15:20Z
https://www.amboras.com/pricing
What was published
Amboras. The store builder that runs itself
Custody — each question answered separately
- Does Junctiq hold the bytes? — ProvenStored, then downloaded back and re-hashed to the recorded digest at 2026-09-25 15:20Z.
- Does the origin still serve it? — ProvenRe-checked 2026-10-15 09:20Z: HTTP 200. The origin now serves different bytes; this capture is the record of what it served at 2026-09-25 15:20Z.
- Does any public archive hold it? — UnknownNever checked for this record: no archive-availability row exists for it.
- Is it independently reproducible? — Not measurableNo instrument compares these bytes with a copy Junctiq does not control, so this is not answered either way.
- Has what the publisher served changed since? — Not measurableThe bytes differ in 19 of 19 later captures, first at 2026-09-26 16:20Z. Differing bytes are not a publisher changing the page — many pages vary on every request — and the method licensed to say what was removed has not yet passed its own blindness check, so Junctiq does not say what, if anything, changed.
The record
- SHA-256
- d5086097fdf1595d582cfbbff2c8a9daf1e7f3b6076f2adf88f12062763b2cda
- Bytes
- 39,217
- Captured
- 2026-09-25 15:20ZWhen Junctiq fetched these bytes — never the publisher’s date.
- Published
- The source did not state one.
- HTTP
- 200 · text/html; charset=utf-8
- Retention
- EXCERPT · retention-v0-2026-09-17Rule v0 is a draft (draft pending legal review). A reclassification would be a new capture under a new rule version, never an edit to this one.
Every capture of this page
Compared by digest only. “Differs” is a fact about bytes; it is not a finding that the publisher changed anything.
| Captured | HTTP | Bytes | SHA-256 | Against this one | Held |
|---|---|---|---|---|---|
| 2026-09-18 22:29Z | 200 | 101,374 | bd2d4fd21239… | differs | no |
| 2026-09-18 22:46Z | 200 | 101,374 | bd2d4fd21239… | differs | yes |
| 2026-09-21 10:20Z | 200 | 101,249 | 7cef5503e986… | differs | yes |
| 2026-09-22 11:20Z | 200 | 101,249 | 4af4331abd46… | differs | yes |
| 2026-09-23 12:20Z | 200 | 101,249 | 5685ee4c7780… | differs | yes |
| 2026-09-24 14:20Z | 200 | 101,249 | 9adc6873f97a… | differs | yes |
| 2026-09-25 15:20Z | 200 | 39,217 | d5086097fdf1… | this | yes |
| 2026-09-26 16:20Z | 200 | 39,209 | e928c56347d1… | differs | yes |
| 2026-09-27 17:20Z | 200 | 42,399 | 8f4fddcede32… | differs | yes |
| 2026-09-28 18:20Z | 200 | 42,399 | f5fef8fbbe32… | differs | yes |
| 2026-09-29 19:20Z | 200 | 42,399 | 833c66a963c5… | differs | yes |
| 2026-09-30 20:20Z | 200 | 42,399 | 71636f72a8a9… | differs | yes |
| 2026-10-01 21:20Z | 200 | 41,945 | 746ecd933a3b… | differs | yes |
| 2026-10-02 22:20Z | 200 | 41,945 | 0c4bb14c3339… | differs | yes |
| 2026-10-03 23:20Z | 200 | 41,945 | 9fdf9ae1994c… | differs | yes |
| 2026-10-05 00:20Z | 200 | 41,949 | efbc81062843… | differs | yes |
| 2026-10-06 01:20Z | 200 | 41,949 | 8c51626927d4… | differs | yes |
| 2026-10-07 02:20Z | 200 | 98,836 | f2ae38d93d63… | differs | yes |
| 2026-10-08 03:21Z | 200 | 99,069 | de8c38a23f9a… | differs | yes |
| 2026-10-09 04:20Z | 200 | 99,083 | d01c0e44de50… | differs | yes |
| 2026-10-10 05:20Z | 200 | 99,083 | 8e018d1f1d47… | differs | yes |
| 2026-10-11 06:20Z | 200 | 99,083 | a173d2d31390… | differs | yes |
| 2026-10-12 07:20Z | 200 | 99,083 | a173d2d31390… | differs | yes |
| 2026-10-13 08:20Z | 200 | 99,083 | 5a7bff471ed1… | differs | yes |
| 2026-10-14 09:20Z | 200 | 99,083 | 07125a300d35… | differs | yes |
| 2026-10-15 09:20Z | 200 | 99,083 | ab53948936a6… | differs | yes |
Provenance
- Artifact
- Excerpt
- Claim
- Commitment
- Resolution
The chain stops at the excerpt. Extracting dated claims from an artifact, committing them and resolving them externally are not built: they wait on Kill Test 1, which is re-measured on 2026-12-16. Until then this record is custody only, and it says so rather than ending quietly where the data ends.