Record the result.
Keep the input, rule reference and decision together.
420 kWh · recorded decision: FLAGEVIDENCE INFRASTRUCTURE
Evidence beyond
the system
that produced it.
Give another party the evidence they need to check your result. Package the decision context and committed evidence artifacts that are actually included in a bundle; independently check their integrity beyond the producer. External source truth and omitted raw inputs remain separate.
Try an evidence handoffExplore the architecture ↓Explore real Pack use cases ↗Claims, tests & evidence limits ↗
DETERMINISTIC CORE / PORTABLE ARTIFACTS / OPEN VERIFICATION
TRUST PATH 01 → 06
PRODUCER ENVIRONMENT
ObservationPolicyContext
✳
Deterministic kernelEvidence + explicit decision logic
ENVIRONMENT BOUNDARY
Portable evidence bundleEXPORT
manifest.jsoncontent commitments
receipt.jsondecision binding
receipt.sig.jsonoptional issuer signature
ledger.jsonlhash-linked records
evidence artifactsinspectable bytes
✓
Independent verifierArtifact checks. No original execution.
06The evidence travels. The producer's environment does not.
01 Measurement→02 Evidence→03 Inference→04 Proof→05 Portable bundle→06 Verification
ONE DECISION. TWO ENVIRONMENTS.
From an internal result
to someone else's checks.
An operations team records a measurement. A reviewer needs to inspect the evidence outside that team's application.
Send the package.
Download the evidence files and their integrity commitments.
One portable bundleCheck what arrived.
Import the file into a separate verifier. No producer session required.
Integrity checked · provenance explicitIllustrative industrial workflow. The demo below uses a synthetic fixture.
01 / THE PROBLEM
A conclusion is only
as useful as the evidence
someone else can inspect.
Systems generate measurements, decisions and claims. But their evidence often stays inside the application, workflow or organization that produced it.
When the evidence moves, context is lost. A dashboard becomes a screenshot. A decision becomes a status. A reviewer is asked to trust an answer they cannot check.
PayGod makes the evidence a transferable artifact—with explicit contracts, decision context and verifiable integrity.
02 / CORE CAPABILITIES
From a measurement
to an inspectable conclusion.
One evidence path. Clear boundaries between what was observed, what was inferred and what can be verified.
Measurement contracts
Give observations a defined metric, unit and context. Keep the measurement distinct from the conclusion drawn from it.
observation → measurementStructured evidence
Organize the artifacts supporting a claim. Use schema-governed records to preserve their role in a decision.
contracts + artifactsDeterministic evaluation
Apply explicit policy packs to defined inputs. Bind the resulting verdict, rule and reason to a recorded decision.
input + pack → decisionTamper-evident proof
Connect artifact digests, manifests, receipts and hash-linked ledger records. Make inconsistencies detectable.
SHA-256 + receipt bindingPortable evidence bundles
Transfer the evidence required for verification across environments without transporting the original runtime.
manifest + receipt + ledger + evidenceIndependent verification
Check the transferred artifacts without rerunning the original policy pack or relying on producer-local state.
artifact-only verificationImplementation scope: the open kernel provides decision evidence and integrity verification. Domain-specific measurement and inference require defined contracts, policy packs and trustworthy inputs. Evidence register (pinned CI and scope) ↗ Executable Packs are policy examples, not independent scanners, ISO/SOC certifications or production release gates. Input-shape admission is not universally enforced by the current CLI run path.
03 / ARCHITECTURE
Small trust core.
Evidence that can leave.
A / SOURCE & EVALUATION
01
Observations & context
External systems, measurements, supporting records
02
Contracts & policy packs
Defined inputs, explicit logic, versioned meaning
03
PayGod kernel
Canonicalization · evaluation · decision artifacts
B / PORTABLE BOUNDARY
EVIDENCE BUNDLEThe handoff is
The handoff is
an artifact.
- Manifest & artifact hashes
- Decision-bound receipt
- Optional detached issuer signature
- Hash-linked ledger
- Supporting evidence
An inspectable package, independent of its transport.
C / RECIPIENT ENVIRONMENT
04
Independent verifier
Integrity, bindings, ledger consistency
05
Machine-readable result
Scoped integrity result, with explicit trust dimensions
Verification ≠ execution
The verifier checks evidence. Downstream systems decide how to act.
04 / INDEPENDENT VERIFICATION
Trust the checks.
Understand their limits.
A verifier should explain exactly what it checked—and what it did not establish.
Read the verification boundary ↗CHECKED BY THE CURRENT VERIFIER
Artifact SHA-256 digests and byte counts. Manifest and receipt bindings. Decision-critical claims against the locked ledger. Ledger hash-chain integrity.
NOT ESTABLISHED BY THESE CHECKS
The truth of an external fact, organization/regulator authorization, policy replay, trusted third-party time or permission to execute a transaction. A detached Ed25519 signature can separately authenticate a receipt to a recipient-trusted key.
Integrity is not provenance.
Current repository witnesses include cross-environment, standalone, browser-parity and detached Ed25519 issuer-authentication verification within CI. Production key governance, rotation and revocation remain separate milestones.
05 / TRY THE HANDOFF
Download the evidence.
Check it somewhere else.
Start with a readable card. Inspect or change the sample, download the bundle, then open it in the separate verifier.
SYNTHETIC INDUSTRIAL EXAMPLE
One measurement. A review decision.
The sample records 420 kWh against a fictional 400 kWh review threshold. The recorded decision is FLAG. This is a prepared fixture, not a live meter or policy execution.
JSON file · up to 2 MB
If the sender gave you the receipt hash through a separate channel, paste it here. A mismatch fails integrity verification.
No trusted issuer keys loaded.
The trust store is recipient-supplied. It is not accepted from inside the evidence bundle.
Download demo trust store TEST KEY ONLYWAITING FOR EVIDENCE
No bundle loaded.
Choose a downloaded bundle or paste its JSON below. Nothing is sent to a server.
EVIDENCE CARDSELF-DECLARED CONTENT
- Recorded decision
- Rule reference
- Declared source
- Recorded time
- Package contents
This card reads the supplied files. It does not establish that the measurement happened or the source is authentic.
View or edit technical files NO BUNDLE
UTF-8 file strings preserve artifact bytes. This transport wrapper is a website handoff format, not a new kernel standard. Maximum total size: 2 MB.
VERIFICATION DIMENSIONSNOT RUN
Waiting for a bundle.
Choose a bundle to begin the checks.
- Integrity
- Not checked
- Issuer authenticity
- Not verified
- Replay
- Not performed
- Time authority
- Not checked
- External receipt pin
- Not provided
Inspect technical checks 0 checks
ISSUER SIGNATURE
Not checkedRECEIPT SHA-256
Not calculatedLEDGER HEAD
Not calculatedMANIFEST SHA-256
Not calculatedBUNDLE DIGEST
Not calculatedIntegrity and issuer authentication are separate. A valid Ed25519 signature authenticates a trusted signing key for this receipt commitment; it does not prove the external fact or issuer authorization.
Integrity VERIFIED means the supported byte, manifest, receipt and ledger checks passed. Issuer authenticity is VERIFIED only when receipt.sig.json validates under a recipient-supplied trusted Ed25519 key. Neither claim proves the real-world evidence is true.
NEXT / THE RECIPIENT'S SIDE
The file carries the evidence.
Download this bundle above, then choose that file in the separate verifier. It opens empty and does not inherit the producer's results.
This browser verifier implements paygod-c14n-v1 integrity checks and optional detached Ed25519 receipt authentication, regression-tested alongside the standalone Python verifier v0.4. Policy replay, trusted third-party time, organization authorization and real-world truth remain separate claims.
Inspect the reference verifier06 / APPLICATIONS
One primitive.
Many evidence boundaries.
Illustrative integration patterns. Each requires its own contracts, provenance and domain validation.
AI systems
Carry evaluation inputs, policy context and decision records beyond the model or agent runtime.
EVALUATION EVIDENCEPayments
Provide inspectable evidence for a release decision, separate from the bank or PSP that executes it.
DECISION HANDOFFIndustrial & environmental
Package measurement context, calculation inputs and review outcomes for independent inspection.
MEASUREMENT RECORDSEnterprise workflows
Preserve why an approval, exception or procurement decision occurred across system boundaries.
WORKFLOW ACCOUNTABILITYCompliance
Make control-evaluation evidence transferable and checkable by a reviewer outside the originating application.
CONTROL EVIDENCESTART WITH ONE EVIDENCE HANDOFF
Bring one decision.
Define the evidence.
Choose a source, an explicit rule and a recipient who needs to check the result. Use the pilot brief to scope a real workflow before building an integration.
01 · Identify the source02 · Define the decision03 · Agree on recipient checks