Time-delayed public disclosure with cryptographically-committed unlock timestamps. Sensitive procurement becomes public on schedule.
Filed · Patent pending
ABT methodology family · variant ABT-S · public sector spending
A defense contract that publishes itself on the date set in 2025
How a time-locked cryptographic commitment enforces mandatory disclosure — without depending on any administrator to execute it.
US Provisional Patent 64/056,353 · Filed May 4, 2026 · sidratnam.com/abt/
disclosure_eligible_at is set at contract award · The key releases automatically on that date · No administrator action required or permitted
Amara Kone awards a defense systems contract
Senior contracting official Amara Kone signs a defense procurement contract. The ABT-S envelope is constructed at award time. The disclosure timestamp — 2031-01-01T00:00:00Z — is cryptographically committed at this moment.
disclosure_eligible_at2031-01-01T00:00:00Z · committed at award · hash-chained
DISCLOSURE UNLOCKS IN: 5 years, 5 months, 17 daysdisclosure_eligible_at: 2031-01-01T00:00:00Z
The disclosure date is set once — at contract award. No procurement official can extend it. No contractor can delay it. No political event prevents it. The disclosure_eligible_at timestamp is a cryptographic commitment embedded in the envelope at construction time. The key releases when the clock reaches that value — regardless of who is in office.
Procurement authority holds the full terms — public tier sealed
The defense procurement office administers the contract using the procurement tier. Contractor identity, total value, technical scope, and delivery milestones are fully accessible here. The public tier is sealed by time-lock.
Procurement tier · DPO-8847 (decrypted by procurement key)
classificationCONFIDENTIAL · waived at disclosure_eligible_at
public_tier[ time-locked · cannot be opened before 2031-01-01 by any party ]
Even the procurement authority cannot open the public tier early. The time-lock is enforced by the key release schedule — it is not an administrative commitment. Early release would require forging the disclosure timestamp commitment, which is hash-chained to the award event.
FOIA request filed — 2027 — before the time-lock releases
A journalist files a FOIA request for DPO-8847 in 2027. The procurement office responds: the public tier is time-locked until 2031. No decision is required by any official. The lock is structural.
FOIA_request:
requestor: [journalist name redacted]
target: DPO-8847
filed: 2027-03-22
requested: contract terms · contractor identity · total value
response:
status: disclosure_eligible_at not yet reached
current_date: 2027-03-22
disclosure_eligible_at: 2031-01-01T00:00:00Z
public_tier_status: sealed · time-lock active
exemption_invoked: none (structural time-lock · not a FOIA exemption)
expected_release: 2031-01-01 (automatic · no administrative action required)
This is not a FOIA exemption — it is a deferred disclosure schedule. The contract is not withheld permanently. The public tier is time-locked to 2031 by design. The response is a statement of fact: the key has not yet released. When 2031-01-01 arrives, the key releases and the public tier becomes readable — without any official needing to approve, sign, or release it.
2031-01-01T00:00:00Z — the time-lock activates
The disclosure clock reaches the committed timestamp. The registry key release endpoint verifies the current time against the sealed disclosure_eligible_at value. The public tier key is released. No human action is required.
DISCLOSURE_ELIGIBLE_AT REACHEDpublic tier key released · 2031-01-01T00:00:01Z
The release is automatic and cannot be blocked. No official can prevent the release once the disclosure_eligible_at timestamp is passed. No contractor can extend the delay. The cryptographic commitment made at award in 2025 executes in 2031 regardless of institutional or political conditions at that time.
Public tier disclosed — the contract is now publicly readable
The public tier is decrypted using the released key. The full contract summary — contractor identity, total value, scope, delivery milestones — is now accessible to any party with access to the public disclosure channel.
The disclosed public tier matches the commitment made in 2025. The hash chain proves the content was not altered between award and disclosure. Any modification to the public tier projection after award would break the chain integrity — detectable by any party verifying the envelope against the registry log.
Integrity verified — the chain proves no alteration
Anyone can verify that the disclosed public tier is identical to the content committed at contract award in 2025. The hash chain entry at award links forward to the disclosure event in 2031.
The six-year integrity guarantee. Between the 2025 award and the 2031 disclosure, no party — not the procurement office, not the contractor, not any administration — could alter the public tier content without breaking the hash chain. The 2031 disclosed document is the document committed in 2025. The registry log proves it.