PayGod/

OPEN CANONICAL KERNEL · APACHE-2.0

Evidence for decisions, beyond the system that made them.

PayGod Kernel is an open-source deterministic decision core with portable artifacts and independent verification. Inspect the code, run the verifier, examine the documented limits, and contribute to the canonical implementation.

OPENApache-2.0 canonical software
v0.4Standalone verifier contract
CIPortable and tamper witnesses
0/10Qualifying real B2 cases

01 / PROOF & LIMITS

What is implemented—and what remains unproven

All public software capabilities refer to the canonical Kernel repository, not external experimental harnesses. The pinned claims register ↗ distinguishes source tests, observed CI results and research-only claims; the generic CLI does not enforce each Pack's embedded input schema automatically.

CapabilityKernel evidenceBoundary
Deterministic decision artifactsREADME, reproducible CLI, packs and test vectorsOpen the source ↗The rule evaluation does not prove an external fact
Independent portable verificationManifest, receipt, ledger, artifact and digest checksOpen the source ↗Integrity does not establish an authenticated origin by itself
Detached receipt authenticationOptional Ed25519 verification with recipient-supplied trust keysOpen the source ↗A valid key is not regulator or organization authorization
Single canonical decision pathRegistered adapters are tested against invented verdicts and receiptsOpen the source ↗Does not assert control over arbitrary external execution
Pre-kernel evidence admissionWITHHELD and NOT RUN preserve unsupported mandatory factsOpen the source ↗These are not additional Kernel policy verdicts
Real-world readinessCurrent B2 report has 0/10 qualifying cases and 0/5 nondeveloper recipient verificationsOpen the source ↗Market adoption, production money release and willingness to pay unproven

02 / EVIDENCE DISCIPLINE

Boundary discipline is part of the technical asset

Do not silently upgrade a file integrity check into source authenticity, a signature into authorization, or a test witness into universal assurance.

01 / BOUNDARY

Evidence first

A missing fact is not FALSE; required unavailable evidence must be WITHHELD before evaluation.

Open the source ↗
02 / BOUNDARY

Coherent rewrite challenge

A fully re-authored bundle can satisfy internal hashes; an independent receipt commitment distinguishes substituted bytes.

Open the source ↗
03 / BOUNDARY

Authority stays canonical

A demo adapter cannot invent a verdict, receipt or identity of a canonical bundle.

Open the source ↗
04 / BOUNDARY

Numeric representability

paygod-c14n-v1 rejects JSON fractions, exponents and unsafe integers; domain conversions need separately tested admission.

Open the source ↗
Integrity ≠ truth · Signature ≠ mandate · Decision ≠ downstream execution

03 / SOURCE & CONTRIBUTION

Open components and reproducible boundaries

A contributor can use the Kernel and verifier without relying on a hosted PayGod service. Changing frozen semantics requires reviewed evidence.

04 / PARTICIPATION

Build on the canonical asset—not on unpromoted research

Contribute a documented counterexample, independently reproducible test, pack or verifier improvement. Commercial hosting, institutional partnerships and scale are possible future paths, not established offerings.

Developer contribution

Source, contracts, tests, contribution and review gates are open to inspection.

Read contribution guidelines →CI / GATES →

Research and institutional partners

A credible next step is a scoped real source, an independent recipient and a measured comparison—not a claim that local tests already prove market value.

ROADMAP →B2 REAL READINESS →