A Denied Branch
Survives the Merge.

Two AI agents ran governed workflows in parallel. One was allowed. One was denied. When the branches merged, the denied result was preserved — not erased, not overridden, not washed out. The aggregate said denied, and anyone can verify it from public bytes alone.

The problem with merging parallel agents

When two AI agents fork from a single root and run in parallel, they each receive independent policy verdicts. The fork is straightforward — the merge is where governance breaks down.

Most orchestration systems treat the join as a simple sync point: wait for both branches to finish, then proceed. If one branch was denied, the denial is lost — consumed by the merge, invisible in the workflow's final state. The join washes out governance.

PromptKing's join does something different. It binds both branch receipts — including their policy verdicts — into a single hash-anchored commitment. Then it derives a deterministic aggregate that cannot ignore a denial.

Three fields, never collapsed

A join produces three separate governance signals. Collapsing them into a single "allowed" or "denied" destroys information. PromptKing publishes each one independently:

deny_dominates-v1

The aggregate disposition follows a deterministic, fail-closed rule derived entirely from publicly verifiable branch receipts:

The aggregate is never persisted. It is derived at serve-time by recomputing each branch receipt's hash, confirming its binding in the join commitment, and reading the policy verdict from inside the hash-verified preimage. A stranger recomputes the same result from public bytes — no PromptKing credentials, no database access, no trust required.

What was proven in production

Verify it yourself

Every receipt below is independently verifiable. No login. No credentials. The hash recomputes in your browser.

What this is not

PromptKing does not sit in the data path. It does not intercept agent traffic or enforce decisions at the network layer. The join aggregate is a derived governance signal — it tells you whether the combined workflow should proceed, backed by cryptographic evidence. Your orchestration stack reads the aggregate and acts on it. PromptKing decides. Your stack enforces. The receipt proves it.