Artifact · captured 2026-10-10 03:21Z
https://docs.saldor.com/
What was published
Saldor Docs Saldor Docs Saldor Docs Search ⌘ K Open console Welcome Getting started Quick start Concepts Requests Workflows Purchases Three-way matching Spend AI Agents MCP Teams Account Integrations Gmail Slack Brex QuickBooks Xero NetSuite API reference Welcome Procurement from
Custody — each question answered separately
- Does Junctiq hold the bytes? — ProvenStored, then downloaded back and re-hashed to the recorded digest at 2026-10-10 03:21Z.
- Does the origin still serve it? — ProvenRe-checked 2026-10-15 08:21Z: HTTP 200, and the origin served these exact bytes.
- 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? — ProvenNo. All 5 later captures, to 2026-10-15 08:21Z, hashed identically.
The record
- SHA-256
- 986d99f449bbbfd248180c9c919c361c904765286f490dbe8d4a8325e630b76e
- Bytes
- 78,830
- Captured
- 2026-10-10 03:21ZWhen 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:27Z | 200 | 78,830 | 3c4aec5c947e… | differs | yes |
| 2026-09-18 22:43Z | 200 | 78,830 | 3c4aec5c947e… | differs | yes |
| 2026-09-21 09:21Z | 200 | 78,830 | 3c4aec5c947e… | differs | yes |
| 2026-09-22 10:21Z | 200 | 78,830 | 3c4aec5c947e… | differs | yes |
| 2026-09-23 11:21Z | 200 | 78,830 | 3c4aec5c947e… | differs | yes |
| 2026-09-24 12:21Z | 200 | 78,830 | 3c4aec5c947e… | differs | yes |
| 2026-09-25 13:21Z | 200 | 78,830 | 3c4aec5c947e… | differs | yes |
| 2026-09-26 14:21Z | 200 | 78,830 | 3c4aec5c947e… | differs | yes |
| 2026-09-27 15:21Z | 200 | 78,830 | 3c4aec5c947e… | differs | yes |
| 2026-09-28 16:21Z | 200 | 78,830 | 3c4aec5c947e… | differs | yes |
| 2026-09-29 17:21Z | 200 | 78,830 | 3c4aec5c947e… | differs | yes |
| 2026-09-30 18:21Z | 200 | 78,830 | 3c4aec5c947e… | differs | yes |
| 2026-10-01 19:21Z | 200 | 78,830 | 3c4aec5c947e… | differs | yes |
| 2026-10-02 20:21Z | 200 | 78,830 | 3c4aec5c947e… | differs | yes |
| 2026-10-03 21:21Z | 200 | 78,830 | 3c4aec5c947e… | differs | yes |
| 2026-10-04 22:21Z | 200 | 78,830 | 3c4aec5c947e… | differs | yes |
| 2026-10-05 23:21Z | 200 | 78,830 | 3c4aec5c947e… | differs | yes |
| 2026-10-07 00:21Z | 200 | 78,830 | 3c4aec5c947e… | differs | yes |
| 2026-10-08 01:20Z | 200 | 78,830 | 986d99f449bb… | identical | yes |
| 2026-10-09 02:20Z | 200 | 78,830 | 986d99f449bb… | identical | yes |
| 2026-10-10 03:21Z | 200 | 78,830 | 986d99f449bb… | this | yes |
| 2026-10-11 04:21Z | 200 | 78,830 | 986d99f449bb… | identical | yes |
| 2026-10-12 05:21Z | 200 | 78,830 | 986d99f449bb… | identical | yes |
| 2026-10-13 06:20Z | 200 | 78,830 | 986d99f449bb… | identical | yes |
| 2026-10-14 07:20Z | 200 | 78,830 | 986d99f449bb… | identical | yes |
| 2026-10-15 08:21Z | 200 | 78,830 | 986d99f449bb… | identical | 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.