delphi.question.published
Appended 15 Aug 2026, 15:53 UTC. Its place in the chain is fixed by the hash of the entry before it; what follows is whether that place is covered by a signature.
The entry
- sequence_
number - 26
- entry_
type delphi.question.published- entity_
type forecast_question - entity_
id ba007bf6-84af-41a3-bad7-f36ecf2ac953- logged_
at 2026-08-15T15:53:36.111539+00:00- previous_
hash 8687a6c8598f68007a1574ec326cfad97bf0caefafc7fd596d7ab52b9c351b76- payload_
hash e662c034dfbe39fe099b421748d5eb12dba155970adca6ed2a48df342d633f9a- entry_
hash 660529669c5d28af23f2999783a5dbc8e6ceda848baa39041e849ca29693fe55
sourceGET /api/transparency/entries/{n}· one entry, as served to this reader· payload served
Payload
{
"slug": "will-anthropic-announce-a-new-claude-model-between-24-august-and-30-september-2026",
"title": "Will Anthropic announce a new Claude model between 24 August and 30 September 2026?",
"origin": "EDITORIAL",
"timebase": {
"clock": "REAL_UTC"
},
"closes_at": "2026-08-23T22:00:00.000000Z",
"opened_at": "2026-08-15T15:53:36.108383Z",
"blind_mode": true,
"provenance": "PUBLIC_RECORD",
"description": "Anthropic released Claude Sonnet 5 on 30 June 2026 and Claude Opus 5 on 24 July 2026, and has announced nothing since. This asks whether the cadence continues inside a five-week window.",
"question_id": "ba007bf6-84af-41a3-bad7-f36ecf2ac953",
"resolution_criteria": "YES if a post dated between 24 August and 30 September 2026 inclusive on anthropic.com/news has as its subject the availability of a Claude model not previously available. Pricing, safety policy, personnel, partnership posts and availability of an existing model on a new platform do not count.",
"expected_resolution_at": "2026-10-01T12:00:00.000000Z",
"canonical_source_policy": "The dated post list at https://www.anthropic.com/news.",
"resolution_rule_revision": 1
}Shown indented so it can be read. The hash is taken over the canonical form of the same object — keys sorted by code point, no insignificant whitespace, UTF-8 rather than escaped ASCII, timestamps RFC 3339 in UTC to microseconds, decimals as their plain string form. The check below re-encodes the object canonically before hashing it, which is why an indented display cannot make it pass or fail.
Verify it here
Recomputing the hashes in this browser… If this sentence stays, this browser has no Web Crypto and nothing here has been verified locally.
The proof, as served
- leaf_
index - 26
- tree_
size - 181
- leaf_
hash d909540080eb4d697ae5bdf6a502548e80aad4956c95a422ae5a9a31fce697ad- audit_
path (8) 0: 4b80680a00c9fa3f9330a2b3ffcd20dd54d14531a3190a7e4fdddad72bf5651b1: 143f0bb32796d42c9f3df69f3d99492112ebe710d90fd1b52a424032aca9795d2: 9388af5d6c467dfae025223077240609a9f56df811b859f128b52d504c7444693: 1cf5d64fb4965f4940c526fa698108d7c4578146408b3cd51dabd149d5674bd74: 7d6682fa6e600d077f7841e30621efe19877a3f61ce600d24a3eb3948d17dd255: b74c92a6356a40d4a8987db99772ead75d18bf349905054ba53bbc3401d9b2b96: 432b3bec17cc8d9bd118f5d2d11fc56d0578ec1940af60be2192f2f1b8d43dc67: 9635acfeb8c2590a96fbee35cfdc30839f075e00ba35b025d06547731fc18743- root_
hash 4c26c3ce818fe1e45410fef48bf0969b94f9e5bc0389388f5310d968c2e42fdc
The earliest published head that covers this entry
No published tree head covers this entry yet, so there is nothing signed to check it against. That is the ordinary state of an entry appended since the last checkpoint, and it is neither a failure nor a permanent one.
sourceGET /api/transparency/proof/inclusion· leaf_hash, audit_path, root_hash· audit-path nodes: 8