Release evidence · mechanical decision gate

Evidence before action.

Created by Filip Majchrzak. This is the public showcase for the Apify Actor filipmajchrzak/ai-claim-checkpoint ↗.

A compact checkpoint that asks one practical question before a release decision is trusted: does the required evidence exist, match the policy, and make sense in time?

Kompaktowa bramka dowodowa: zanim decyzja zostanie zaakceptowana, sprawdza kompletność, zgodność z polityką i spójność czasową dowodów.

Real Apify runtime Exact-byte SHA-256 Fail-closed Hard 50/day cap

Live infrastructure demonstration

See a release claim become a decision.

Choose a fixed synthetic scenario. The demo launches a real Apify run, verifies the returned proof, and shows a decision tied to a concrete run ID and exact-response digest.

Wybierz syntetyczny scenariusz. Demo uruchamia prawdziwy run Apify, weryfikuje dowód i pokazuje decyzję powiązaną z konkretnym run ID oraz skrótem exact-response.

CreatorFilip Majchrzak

Apify Actorfilipmajchrzak/ai-claim-checkpoint

RuntimeLive Apify Actor

Decision surfaceALLOW / BLOCK

Proof anchorRun ID + SHA-256

Failure postureFail closed

01 · Run a decision

Choose a controlled scenario

Both paths use fixed synthetic release evidence. No arbitrary Actor input is accepted from the browser.

ALLOW path✓

Evidence supports the release

Required test and review evidence is present, valid and temporally consistent.

Wymagane dowody z testów i przeglądu są obecne, poprawne i spójne czasowo.

tests: PASSreview: PASS

BLOCK path×

A required control fails

At least one required condition fails, so the release decision must not proceed.

Co najmniej jeden wymagany warunek nie jest spełniony, więc decyzja o wydaniu zostaje zatrzymana.

tests: FAILpolicy: required PASS

02 · Understand the gate

Three things happen before a decision is shown

Evidence is fixed

The browser chooses a scenario ID, not arbitrary policy or Actor input.

The policy evaluates it

The live Actor checks required evidence and returns a bounded decision artifact.

The proof is rechecked

The demo only presents a decision when OUTPUT and VERIFICATION agree.

03 · Example rule

Temporal integrity: evidence cannot arrive after the decision

This is one simple example of why an evidence gate is useful: a later artifact cannot retroactively justify an earlier decision.

✓ Valid sequence

✓Evidence collectedAug 8, 12:00

▶

◆Decision madeAug 9, 00:00

✓ ALLOW

Evidence existed before the decision — the claim can be supported.

× Invalid sequence

◆Decision madeAug 9, 00:00

▶

!Evidence collectedAug 10, 13:00

× BLOCK

Evidence postdates the decision — the claim is rejected rather than silently accepted.

The rule

Every evidence item must carry a timestamp before the decision's logicalTime. Evidence dated after the decision cannot support that decision.

04 · What this demo proves

Concrete, inspectable proof — with a narrow claim ceiling

Real infrastructure

The decision comes from a real external Apify run, not a prerecorded animation.

Specific provenance

The result is tied to an external run ID and an exact raw-response SHA-256.

Bounded exposure

The public path is access-gated, fail-closed and hard-capped at 50 external attempts per UTC day.

No inflated claim

Synthetic evidence demonstrates the mechanism. It is not certification and does not prove production safety, security or compliance.