PromptKing

Continuity of accountable intent across control planes

An independent record of what an AI agent was asked to do, what it did, and what the evidence supports.

When autonomous work moves between agents, models, and systems of record, the claim that a decision was authorized and that the observed outcome matches the intended change is not automatically preserved. PromptKing produces a Work Record that another party can check without trusting the system that performed the work.

Public research surface · Live published record · Gaps remain visible

The object

One run, one chain: each link a claim with its evidence.

  1. ActorWho or what acted
  2. IntentWhat was authorized to occur
  3. AuthorityWhether the required authorization was established
  4. ActionWhat agents and tools actually ran
  5. EvidenceWhat changed in the systems of record
  6. LineageHow the work continued across agents or sessions
  7. OutcomeWhat the evidence establishes, and what it does not
  8. VerificationHow another party checks the record without trusting the system that did the work

The record sits outside the execution stack. Verification does not require trusting the runtime that performed the work. Authority gaps, incomplete observations, and unresolved references remain visible rather than filled in.

View published Work Record 0002 →

Check a record yourself

Start with the published record, rebuild its hash from the specification, or check the signed and timestamped receipt. The verifier kit is shared on request with researchers and technical teams.

Method

Records are produced from supplier observations (agent reports, system-of-record changes, controlled fixtures, and published traces) under a fixed adjudication kernel. The kernel is the sole source of verdicts. Public pages render only what the kernel established; they do not add executive interpretation or fill missing evidence.

Current published surfaces distinguish verification modes. Some receipts are publicly recomputable. Some obligation artifacts are server-recomputed. The distinction is stated on the record.

Primary database resides in Canada. Access to a system of record, when used, is read-only and outside the agent’s execution path.

Proof index

Each item below states what it shows and what it does not. Where a record is not public today, the entry says so.

Public, checkable now

Internal record, not public today

Published evidence

A chronological collection of runs, fixtures, and controlled tests is maintained with explicit limits for each entry. Each entry states its data origin, what it shows, and what it does not establish.

Evidence collection →
Standing limits. No record currently establishes deployment in a production environment. A receipt (August 11, 2026) carries a PromptKing issuer signature and an independent timestamp authority’s attestation that its digest existed by a stated time. That shows who issued it and when it existed; it is not a legal guarantee that no party can dispute it. Authority is frequently “Not established.” Multi-vendor continuity has been demonstrated in specific controlled settings; it is not claimed as a general production property.

Notes and working papers

Short write-ups of specific runs, failures, and design lessons. Each is a working note from PromptKing's own engineering record. None is peer-reviewed.

All insights →

Correspondence

This surface exists so that a technical or strategic counterparty can examine a live, stranger-checkable record and the method that produced it.

Researchers, institutions, and technical teams who want to examine or recompute a record are welcome to write to info@promptking32.com.