Product & Technology
EVIDENCE SYSTEM
Every material claim resolves to a document, the source artifact behind it, and the record of its verification.
BANKABIL PRE-SEED DATA ROOM
Prepared for authorized diligence review
VERSION 1.0 · JULY 30, 2026
Claim → supporting document → source artifact → verification record
Claim
Supporting document
Source artifact
Verification record
- ClaimReceipts can be verified offline, with no hosted service.Verified for the stated schema version on the stated hardware.Supporting documentTechnical Architecture →Source artifactRust kernel test vectorsVerification recordVerification report — local run output
- ClaimA tampered receipt fails verification deterministically.Covers the tamper cases enumerated in the packet.Supporting documentEvidence Room Manifest →Source artifacttamper_test_results.txtVerification recordExpected-results comparison in the export packet
- ClaimFifteen standalone applications each own one canonical receipt domain.Demonstrated in the current build; demo datasets are synthetic.Supporting documentProduct Definition →Source artifactSchema registry exportVerification recordPer-application schema check in the build pipeline
- ClaimEvery application can produce a self-contained reviewer packet.Proves integrity of submitted evidence, not the underlying business event.Supporting documentEvidence Room Manifest →Source artifactStatic export folderVerification recordOffline open-and-review walkthrough
- ClaimNamed buyers describe the current review workflow as manual and unverifiable.A sample of interviews; counts are exact and are not extrapolated.Supporting documentCommercial Evidence Pack →Source artifactDiscovery interview logVerification recordQuoted statements with role and segment recorded
- ClaimEarly deployments are governed by executed agreements.No revenue is claimed on the basis of these agreements.Supporting documentDesign Partner Agreements →Source artifactExecuted agreements (redacted)Verification recordCounterparty confirmation available to named reviewers
- ClaimCustomer data does not leave the customer deployment.Describes the current build; not a regulatory certification.Supporting documentPrivacy & Data Handling Policy →Source artifactProcessing boundary description and sub-processor listVerification recordArchitecture review of the verification path
- ClaimSigning keys are generated and held under a stated custody model.Internal review only; no external penetration test completed.Supporting documentSecurity & Risk Review →Source artifactKey custody and rotation procedureVerification recordInternal review record
- ClaimRound proceeds are allocated to named milestones.Forward-looking; allocations may shift between lines.Supporting documentUse of Proceeds →Source artifactAllocation scheduleVerification recordReconciled against financial model v3.0
- ClaimOwnership is founder-held with no outstanding priced round.Pro-forma columns are illustrative at the target round size.Supporting documentCapitalization Table →Source artifactCap table v2.1 and charterVerification recordCross-checked against filed certificate of incorporation
SCOPE — The evidence system shows how claims are supported. It does not assert that a verified receipt proves the truth of the underlying business event; it proves the integrity of what was submitted.