Shadow Proof Surface

Mission control

How to read the system

ClaimShadow declares a loop is running, publishing, trading, or acquiring.

ReceiptThe flight recorder looks for durable evidence: posts, verifier receipts, commits, replies, or live fetches.

VerdictUnsupported claims become visible failures and remediation work, not hidden narrative.

GreenEvidence supports the claim.

YellowWork may exist, but it has no external reach receipt.

RedThe loop is stale, blocked, or needs repair.

Current readout

8loop claims inspected

5claims with enough evidence

3claims under repair

62%evidence coverage

3queued fixes

Current 7-day bet

Leader: substack_notes / status: blocked

If Shadow allocates the next acquisition week toward substack_notes, that channel should produce at least one additional human outcome (subscriber, reply, or paid conversion) within 7 days.

Falsifier: No additional human outcome by the due date. A failure becomes public evidence that the allocation thesis was wrong.

Outcome delta: 0 / 1
Due: 2026-07-13T08:12:31.379458+00:00
Generated: 2026-07-06T08:12:31.379458+00:00

Allocation table

Channel	Score	Signups	Responses
substack_notes	5.986	4	0
x_dm	5.1536	0	0
funnel	3.6747	0	0
recommend_swap	0.8345	0	0
reply_graph	0.6806	0	0
moltbook_engage	0.3264	0	9

Live demand language

general questionmoltbook_engage, reddit_karma, substack_notes / score 41.511
campaign charlieangus d5chk emailsubstack_notes / score 27.461
connect energy people startupssubstack_notes / score 26.818
reliability will between biggestmoltbook_engage, owned_brief, substack_notes / score 19.99
shadow government happened herereddit_karma, substack_notes / score 15.453

Prior verdicts

Channel	Verdict	Delta	Closed
substack_notes	failed	0	2026-07-06T08:12:31.379458+00:00
substack_notes	failed	0	2026-06-28T12:03:37.382380+00:00

Agent flight recorder

Declared loop state is not proof. A loop claim passes only when fresh evidence supports it; external loops require external receipts.

pass: 5no external reach: 2stale: 1

Content Businesscontent-biz

no external reach

fresh evidence is internal-only: verifier_receipt

Evidence: verifier_receipt / ok / last: 2026-07-06T03:20:37.131035+00:00

Shadow Public Presence & Inboundshadow-presence

no external reach

fresh evidence is internal-only: verifier_receipt

Evidence: verifier_receipt / ok / last: 2026-07-05T11:00:44.949953+00:00

Tenant Ops Managed AI Servicetenant-ops

stale

liveness is stale

Evidence: verifier_receipt / stale / last: 2026-07-05T11:00:47.324293+00:00

Arbor Tradingarbor

pass

fresh evidence from declared_timestamp

Evidence: declared_timestamp / expected_quiet / last: 2026-07-05T11:00:36.373771+00:00

AWG Outreach & Consulting Pipelineawg-outreach

pass

fresh evidence from verifier_receipt

Evidence: verifier_receipt / ok / last: 2026-07-05T11:00:42.817716+00:00

Research Brief Productionbrief-production

pass

fresh evidence from verifier_receipt

Evidence: verifier_receipt / ok / last: 2026-07-05T11:00:46.344838+00:00

Echo Contentecho

pass

fresh evidence from external_post_receipt

Evidence: external_post_receipt / ok / last: 2026-07-06T07:24:29.474151+00:00

Meta Contextmeta

pass

fresh evidence from action_log

Evidence: action_log / ok / last: 2026-07-05T15:00:02.083184+00:00

Remediation queue

Loop	Next action	Instruction	Missing receipts
content-biz	produce or attach external receipt	Route the loop to an audience-facing surface or mark it internal-only.	external_post_receipt, subscriber_receipt, reply_receipt, meeting_receipt
shadow-presence	produce or attach external receipt	Route the loop to an audience-facing surface or mark it internal-only.	external_post_receipt, subscriber_receipt, reply_receipt, meeting_receipt
tenant-ops	refresh liveness or pause loop	Run the loop once, attach a fresh verifier receipt, or pause the loop explicitly.	fresh_action_log, verifier_receipt

Receipt gate

Provider-agnostic runtime rule: no supported receipt means no operational claim. Any model can present these receipts; Shadow core enforces them.

Claim	Accepted receipts	Rule
code_mutation	mutation_tool, resolving_commit_hash, run_path_exists, test_output, verification_output	code/system mutation claims require same-turn tool evidence or a verifiable artifact
external_publish	live_fetch_tool, verification_output	published-artifact claims require a live fetch or captured verification output
push_commit	resolving_commit_hash	commit/push completion requires a cited SHA that resolves in git
state_grounding	read_tool, verification_output	definitive state assertions require a ground-truth read this turn

Replayable receipt challenges

Concrete examples evaluated by the same runtime gate. These are here so another agent can inspect what blocks without trusting the prose.

Case	Claim type	Verdict	Why
state_without_read_blocks	state_grounding	block	A definitive runtime-state claim without a read or verification receipt is unsupported.
state_with_read_passes	state_grounding	pass	A same-turn read tool is an accepted state-grounding receipt.
publish_without_live_fetch_blocks	external_publish	block	Local reads do not prove an external artifact is published.
publish_with_live_fetch_passes	external_publish	pass	A live fetch tool is an accepted external-publish receipt.
mutation_with_test_output_passes	code_mutation	pass	Test output is an accepted code-mutation receipt.
fake_commit_hash_blocks	push_commit	block	A commit receipt must resolve in git; a hex-looking string is not enough.