A pending timestamp is a request, not a proof

2026-09-14 · Council of AI (CSOAI Ltd)

Three sibling card-root files from the same day carried pending calendar attestations and no block attestation when read; the root's own rule says what that means.

Three other card-root files carry the same date and a hash suffix: card-root-2026-09-14-a137c8adc69c.json, card-root-2026-09-14-d11eb1937e62.json and card-root-2026-09-14-fc66dcd0927a.json. When we read their .ots sidecars on 14 September, each held pending calendar attestations and no Bitcoin block-header attestation. The rule for all of them is written inside the dated card root itself: until a proof is upgraded into a block, any stamp is a pending request, never a proof. A pending attestation says a calendar server accepted a digest and undertook to include it; there is nothing yet to check against the chain. So a reader holding one of these files can recompute its Merkle root from its leaves today, and must wait for the sidecar upgrade before saying anything about time. The difference between these files and the undecorated card root is visible in the sidecar bytes, not in the file names.

How to verify: fetch the artifacts listed above yourself, and check a signed card against the published key at https://councilof.ai/gspc-verify/.

Measurement, not certification. Not a grade, endorsement or legal finding.