Artifact · captured 2026-10-14 07:20Z
https://oroagents.com/docs
Requested https://docs.oroagents.com/ and was redirected here. The difference is kept as evidence.
What was published
ORO Documentation | ORO Docs ORO AI Blog Compete Leaderboard Dashboard Docs Research AssistantEval ORO Bench ShoppingBench Blog Compete Leaderboard Dashboard Docs Research AssistantEval ORO Bench ShoppingBench Docs Docs Search ⌘ K Overview ORO Documentation ORO Bench Architecture
Custody — each question answered separately
- Does Junctiq hold the bytes? — ProvenStored, then downloaded back and re-hashed to the recorded digest at 2026-10-14 07:20Z.
- 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. The one later capture, to 2026-10-15 08:21Z, hashed identically.
The record
- SHA-256
- ca9e1eab860ddd9d8b93e64e00f561620deacc2c361c310c8ccc7d0aa8fcc444
- Bytes
- 718,970
- Captured
- 2026-10-14 07: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-10-09 02:20Z | 200 | 695,745 | 8e9fc18535b0… | differs | yes |
| 2026-10-10 03:20Z | 200 | 695,745 | e329c69a7c67… | differs | yes |
| 2026-10-11 04:20Z | 200 | 695,745 | e329c69a7c67… | differs | yes |
| 2026-10-12 05:20Z | 200 | 695,745 | e329c69a7c67… | differs | yes |
| 2026-10-13 06:20Z | 200 | 695,745 | e329c69a7c67… | differs | yes |
| 2026-10-14 07:20Z | 200 | 718,970 | ca9e1eab860d… | this | yes |
| 2026-10-15 08:21Z | 200 | 718,970 | ca9e1eab860d… | 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.