apps/treasury_proof · port 3003 · lead Dan

TreasuryProof

Liquidity, covenants, borrowing bases, and payment authority

treasuryproof.liquidityVault NavyREPO DOC CATALOG NEXT → ACQUIREPROOF

First receiptLiquidityPacketReceipt / CovenantStatusReceipthttp://127.0.0.1:3003CONTRACT MVP DEMOS EVIDENCE ROOM FEEDS ARCHIVE

01 · Canonical Contract And Positioning

Canonical Contract

Slugtreasury_proof

LeadDan

Port3003

Brand accentVault Navy #1B2A4A

Workflow identifiercash_snapshot_to_authorized_payment.v1

Receipt domaintreasuryproof.liquidity

Schema version1.0.0

Canonical first receiptLiquidityPacketReceipt / CovenantStatusReceipt

Local URLhttp://127.0.0.1:3003

Product And GTM Positioning

Vertical: Liquidity, covenants, borrowing bases, and payment authority
Audience: Lenders, owners, controllers, and treasury teams
Reviewer: Credit officers, lenders, boards, and auditors
Developer wedge: Webhook listener and CLI verifier for bank and ledger events.
Commercial model: Team $1,500 per month and Assurance from $25k per year.

02 · MVP Boundary And Claims Limitation

MVP Boundary

Declared cash and AR/AP files, selected calculations, authority records, and liquidity/covenant packet export.

V1 expansion is reserved for: Plaid, bank APIs, and treasury system connectors for recurring packet refreshes. MVP docs, UI, and demos do not imply those integrations exist yet.

Claims Limitation

Does not assert creditworthiness, covenant compliance, lending eligibility, or lender approval.

03 · Demo Dataset And Scenarios

Canonical Demo Dataset

Subject

Synthetic borrower liquidity package

Review packet

Liquidity and covenant packet

Source records

accountsar_agingap_agingborrowing_basedscrauthorized_payments

The dataset is synthetic and deterministic. It exists to show the workflow, receipt lifecycle, verification behavior, and static Evidence Room export without depending on production connectors.

Demo Scenarios

clean_pathissued_and_verifiedCanonical receipt validates, issues, and verifies offline.
failed_validationschema_rejectedRequired evidence field is omitted before kernel issuance.
tampered_artifactverification_failedReceipt is issued, then verification runs against a mutated signed payload.
unauthorized_actorauthority_rejectedActor scope is outside the declared MVP workspace authority.
schema_version_mismatchschema_rejectedPayload asks for an unsupported schema version.

04 · Evidence Room And Local Commands

Evidence Room Narrative

The export packages receipt JSON, canonical receipt envelope material, artifact digests, source data, schemas, verification output, limitations, and review-log entries into a static local folder for reviewer inspection.

README.mdmanifest.jsonreceiptsartifactssource-dataschemasverificationlimitationsreview-log

Receipt payload sections

envelopeauthorityeventevidenceverificationclaimslineage

Local App Commands

cd apps/treasury_proof
bin/demo
bin/rails server -p 3003
open http://127.0.0.1:3003

Native kernel methods used

doctorissue_receiptverify_receiptdigest_artifactsvalidate_schema

docs/companies/treasury_proof.md →

05 · Operator Queue

Recent Receipts

10:41Cash Position ReceiptVerified
13:29Covenant Review ReceiptVerified

Decision Queue — C.

Covenant ReviewCovenant Receipt #6High Risk
Cash ForecastCash Receipt #44Needs Approval

06 · Planning History (not canonical)

ARCHIVE — earlier workshop, pricing-studio, and pre-seed planning material. Where it disagrees with the repo, the canonical contract above wins.

MVP Use Case

A company produces a verified weekly liquidity and covenant packet containing cash position, receivables, payables, borrowing-base inputs, covenant status and management approval.

Small and middle-market companies become more bankable by converting treasury operations into lender-readable evidence.

Phase 1 Artifacts

·Treasury operating map
·Community-bank reporting map
·Borrowing-base evidence taxonomy
·Covenant evidence specification
·Treasury-risk register
·Lender design-partner interview guide
·Initial unit economics

MVP Artifacts

·Treasury dashboard
·Weekly liquidity workflow
·Cash-position receipt
·Covenant-status receipt
·Receivables evidence receipt
·Lender packet export
·Local verifier
·Simulated borrower and lender accounts

V1 Artifacts

·Bank account ingestion
·Receivables aging import
·Covenant configuration
·Borrowing-base calculation evidence
·Approval chains
·Exception receipts
·Multi-lender packet formats
·API for treasury and vertical-fintech developers

VC-Readiness Proof

·Time required to generate lender reporting
·Reduction in missing lender documentation
·Frequency of verified treasury packets
·Design-partner lender feedback
·Willingness to pay by facility size
·Expansion from one packet into recurring treasury monitoring

Investor Narrative

TreasuryProof makes cash, runway, covenants, receivables, borrowing bases and working-capital claims independently reconstructable.

Gate Path

G1Gate 1 — Thesis ReadyThe specific workflow · The evidence failure · The developer user · The economic buyer · Why the founder is suited to solve it · Why the startup should exist independently
G2Gate 2 — MVP ReadyOne Rails workflow · One Rust receipt family · One local verification path · One Evidence Room export · One developer quickstart · One design-partner use case
G3Gate 3 — Pilot ReadyExternal acceptance criteria · Integration documentation · Measurable baseline · Commercial terms · Claims boundaries · An explicit end-of-pilot decision
G4Gate 4 — V1 Venture ReadyProduct functionality · Developer adoption · External workflow completion · Verified artifacts · Willingness to pay · Repeatability and expansion potential · Capital requirements

Phase Timing

Phase 0 — Founder-Market ThesisWorkshop kickoff9 artifacts
Phase 1 — Pre-MVP Venture Thesis PackWeeks 1-210 artifacts
Phase 2 — MVP Artifact PackWeeks 3-620 artifacts
Phase 3 — Pilot-Ready Artifact PackWeeks 6-923 artifacts
Phase 4 — V1 Venture-Readiness PackWeeks 9-1231 artifacts

One-click investor export

Downloads the full pre-seed package for TreasuryProof, Inc. — every folder, checklist and manifest in one file. ZIP ships README, manifest.json, checklist.csv and per-folder markdown; PDF ships a single reviewer-ready document.

INVESTOR SHARE

TreasuryProof, Inc.Standalone diligence roomDerived from playbookInvestor-ready0 / 18

Minimum investor-ready set — 18 items

Incorporated entityPENDING
EINPENDING
Founder stock and vesting documentationPENDING
Complete IP assignmentPENDING
Clean cap tablePENDING
Bankabil license agreementPENDING
Investor deckPENDING
One-page overviewPENDING
Two-page investment memoPENDING
24-month financial modelPENDING
Use-of-funds planPENDING
Product requirements documentPENDING
Workflow diagramPENDING
First receipt schemaPENDING
Demo Evidence RoomPENDING
At least 15 customer interviewsPENDING
At least three design-partner lettersPENDING
Product-specific claims-limitation documentPENDING

Bankabil Technology License and Services Agreement

Establishes that TreasuryProof, Inc. is diligenceable on its own: investor rights here create no rights in any other cohort company.

›Bankabil owns or controls the shared Rails/Rust infrastructure.
›The startup receives a defined license to use it.
›The startup owns its customer relationships and domain-specific workflow.
›Domain-specific product improvements are clearly allocated.
›Shared-kernel improvements are clearly allocated.
›Hosting, security, maintenance, service levels and fees are defined.
›No startup automatically owns another startup’s product data or intellectual property.
›Investor rights in one startup do not create rights in the others.

Bankabil architecture-use scheduleIntercompany data-isolation policyShared-services pricing scheduleOpen-source dependency scheduleFounder/company intellectual-property boundary memo

01 · Company formation and ownership

Each independent legal entity needs its own EIN and corporate records. The IRS issues EINs directly and charges no application fee.

Certificate of incorporationPENDING
BylawsPENDING
Initial board consentPENDING
Founder stock purchase agreementPENDING
Founder vesting schedulePENDING
Intellectual-property assignment agreementPENDING
Proprietary information and inventions agreementPENDING
Founder roles and responsibilities memoPENDING
Current capitalization tablePENDING
Fully diluted capitalization tablePENDING
Stock ledgerPENDING
Option-pool plan or proposed option-pool memoPENDING
EIN confirmationPENDING
Business bank account confirmationPENDING
State registrations and foreign qualifications, where applicablePENDING
Beneficial ownership and corporate-record checklistPENDING
Conflict-of-interest disclosurePENDING
Related-party transaction disclosurePENDING

02 · Fundraising materials

For a SAFE financing, use a recognized form adapted by company counsel. A Regulation D offering generally requires a Form D notice filed through EDGAR after the first sale; counsel determines the correct federal and state process.

10–12 slide investor deckPENDING
One-page company overviewPENDING
Two-page investment memoPENDING
Founder-market-fit narrativePENDING
“Why now?” memoPENDING
Market mapPENDING
Competitive landscapePENDING
Business-model summaryPENDING
Go-to-market planPENDING
Initial customer pipelinePENDING
Fundraising target and use-of-funds planPENDING
Milestone-based financing planPENDING
Investor FAQPENDING
Risk-factor memoPENDING
Current fundraising-status trackerPENDING
Investor outreach listPENDING
Warm-introduction mapPENDING
Follow-up and diligence trackerPENDING
Financing instrument summaryPENDING
Draft SAFE or other financing instrument reviewed by counselPENDING
Pro forma post-financing cap tablePENDING

03 · Product definition

Every company answers the same eleven questions: company name, product name, founder-market fit, primary buyer, primary reviewer, repeatable workflow, first receipt primitive, Evidence Room contents, pricing wedge, MVP boundary, claims limitation.

Product requirements documentPENDING
Product thesisPENDING
Target-customer profilePENDING
Buyer-versus-reviewer mapPENDING
Workflow specificationPENDING
Receipt schema specificationPENDING
Evidence Room specificationPENDING
MVP scope documentPENDING
Explicit non-goals documentPENDING
Claims-limitation documentPENDING
User-permission matrixPENDING
Data-source inventoryPENDING
Integration roadmapPENDING
Product roadmap for the next 12 monthsPENDING
Demo scriptPENDING
Demo acceptance criteriaPENDING

04 · Customer discovery and commercial proof

A letter of intent should identify intended workflow, expected users, demo or pilot period, evidence to be generated, success criteria, proposed commercial price, data-access limitations, and a statement that the letter is nonbinding unless counsel specifies otherwise.

Minimum of 15 documented customer interviewsPENDING
Interview notesPENDING
Interview consent and attribution statusPENDING
Pain-point frequency matrixPENDING
Current-workflow diagramPENDING
Current-tool and substitute analysisPENDING
Willingness-to-pay findingsPENDING
Buyer-budget-owner analysisPENDING
Procurement-path memoPENDING
Reviewer-requirements summaryPENDING
Design-partner target listPENDING
At least three design-partner lettersPENDING
At least one pilot letter of intentPENDING
Customer pipeline spreadsheetPENDING
Objection logPENDING
Lost-customer or declined-pilot logPENDING
Pricing-interview summaryPENDING
Initial channel-partner listPENDING

05 · Demo dataset and Evidence Room

Each company needs a synthetic but realistic first demo company. Never copy private data from a real person or organization without authorization.

Demo-company profilePENDING
Demo user personasPENDING
Demo workflow timelinePENDING
Synthetic source documentsPENDING
Data dictionaryPENDING
Ground-truth answer keyPENDING
Expected receipt hashesPENDING
Expected signature outputsPENDING
Invalid or tampered-document examplesPENDING
Demo verification test casesPENDING
Reviewer walkthroughPENDING
Claims-limits filePENDING
Demo READMEPENDING
Sample ProofMail messagePENDING
One-click or scripted verification instructionsPENDING

06 · Technical architecture and security

Boundary stays fixed — Rails: human workflow, state, permissions, intake and presentation. Rust: canonicalization, hashing, signing and deterministic receipt generation. Evidence Room: reviewable artifacts and source manifest. ProofMail: controlled external handoff.

System architecture diagramPENDING
Rails workflow architecturePENDING
Rust trust-kernel architecturePENDING
Rails-to-Rust API contractPENDING
Canonicalization specificationPENDING
SHA-256 hashing specificationPENDING
Ed25519 signing specificationPENDING
TLV schema specificationPENDING
JSON receipt specificationPENDING
Key-generation procedurePENDING
Key-storage and rotation policyPENDING
Signing-authority policyPENDING
Verification procedurePENDING
Evidence-retention policyPENDING
Tenant-isolation architecturePENDING
Role-based access-control matrixPENDING
Audit-log specificationPENDING
Incident-response planPENDING
Data-backup and recovery planPENDING
Threat modelPENDING
Abuse-case analysisPENDING
Software bill of materialsPENDING
Open-source license inventoryPENDING
Penetration-test roadmapPENDING
Security and privacy FAQPENDING

07 · Financial model

The model must separate customer revenue, Bankabil license or service expense, cloud and verification costs, implementation labor, customer support, sales costs and company-specific legal/compliance costs.

24-month monthly operating modelPENDING
Five-year annual summaryPENDING
Headcount planPENDING
Product-development budgetPENDING
Hosting and infrastructure assumptionsPENDING
Bankabil licensing or shared-services expensePENDING
Sales and marketing budgetPENDING
Legal and compliance budgetPENDING
Insurance budgetPENDING
Gross-margin modelPENDING
Customer-acquisition-cost assumptionsPENDING
Contract-value assumptionsPENDING
Sales-cycle assumptionsPENDING
Churn and renewal assumptionsPENDING
Cash-burn schedulePENDING
Runway calculationPENDING
Financing requirementPENDING
Base, downside, and upside scenariosPENDING
Use-of-funds schedulePENDING
Milestones unlocked by the roundPENDING
Founder salary assumptionsPENDING
Capitalization model before and after financingPENDING

08 · Legal, claims, privacy, and compliance

Conduct federal and common-law trademark clearance before committing to a company or product name. The USPTO recommends searching its trademark database before applying for registration.

Master claims-limitation policyPENDING
Product-specific claims matrixPENDING
Approved product languagePENDING
Prohibited product languagePENDING
Terms of servicePENDING
Privacy policyPENDING
Data-processing addendumPENDING
Customer agreementPENDING
Pilot agreementPENDING
Design-partner agreementPENDING
Confidentiality agreementPENDING
Subprocessor listPENDING
Data-retention schedulePENDING
Data-deletion policyPENDING
Security addendumPENDING
Customer-content ownership clausePENDING
AI-use disclosurePENDING
Synthetic-data disclosurePENDING
No-professional-advice disclaimerPENDING
Insurance requirements memoPENDING
Trademark clearance reportPENDING
Patent/trade-secret strategy memoPENDING

Demo Evidence Room — file manifest

Canonical

README.mdPENDING
claims_limits.mdPENDING
receipt.jsonPENDING
receipt.tlvPENDING
verification_result.txtPENDING
source_evidence_manifest.csvPENDING
reviewer_packet.pdfPENDING
developer_quickstart.mdPENDING

Required additions

demo_data_license.mdPENDING
synthetic_data_disclosure.mdPENDING
expected_results.jsonPENDING
tamper_test_results.txtPENDING
receipt_schema.jsonPENDING
public_key.pem (or documented public-key format)PENDING

Product & market documents

TreasuryProof_Product_Thesis.pdfPENDING
cash_snapshot_to_authorized_payment_Workflow.pdfPENDING
TreasuryProof_Buyer_Profile.pdfPENDING
TreasuryProof_Reviewer_Profile.pdfPENDING
TreasuryProof_Competitive_Map.pdfPENDING
TreasuryProof_Pricing_Memo.pdfPENDING

Workflow documents

Workflow specification — cash_snapshot_to_authorized_payment.v1PENDING
Buyer intake form — Corporate controllers running continuous treasury monitoring.PENDING
Reviewer requirements summary — Lenders requiring continuous compliance verification of borrower portfolios.PENDING
Authorization and closing-authority matrixPENDING
Reviewer packet templatePENDING

First receipt schemas

treasuryproof_liquidity_receipt.schema.jsonPENDING

Evidence Room contents

README.mdPENDING
claims_limits.mdPENDING
receipt.jsonPENDING
receipt.tlvPENDING
verification_result.txtPENDING
source_evidence_manifest.csvPENDING
reviewer_packet.pdfPENDING
developer_quickstart.mdPENDING

Commercial documents

Order form — $1,500/month Team Workspace for continuous treasury monitoring. $25,000 annual Assurance Pack for lenders verifying borrower portfolios.PENDING
Design-partner agreementPENDING
Pilot statement of workPENDING
Channel-partner referral memoPENDING

MVP and demo dataset

MVP boundary — Manual CSV upload and parsing of bank ledger balances.PENDING
V1 expansion — Direct Plaid and bank API integrations, programmatically signing cash balances, AR/AP aging metrics and borrowing-base parameters.PENDING
Developer wedge — A secure webhook listener that intercepts banking API transfers, verifies payload schemas and issues signed receipts.PENDING
Synthetic demo company profile (not yet drafted)PENDING
Tamper-test case set (not yet drafted)PENDING

Claims limitation

✕Scope limited to the MVP boundary: Manual CSV upload and parsing of bank ledger balances.
✕Does not provide legal, tax, audit or investment advice
✕Does not guarantee outcomes, funding or revenue
✕Verifies integrity, sequence, authorization and identified source relationships only

Recommended creation order

Weeks 1–2

Legal and thesis

·Incorporate each entity.
·Execute founder and IP documents.
·Finalize the Bankabil license structure.
·Write the one-page thesis for each startup.
·Confirm buyer, reviewer, workflow, receipt, MVP and claims boundary.

Weeks 3–4

Customer evidence

·Conduct 15–20 interviews per company.
·Obtain three design-partner letters.
·Validate pricing.
·Record reviewer requirements.
·Refine the workflow and MVP.

Weeks 5–6

Demo Evidence Rooms

·Build each synthetic demo dataset.
·Generate first receipts.
·Create tamper-test cases.
·Produce reviewer packets.
·Record concise product demos.

Weeks 7–8

Fundraise room

·Finish decks and investment memos.
·Complete financial models.
·Prepare use-of-funds schedules.
·Finalize draft financing documents with counsel.
·Open separate investor data rooms.
·Begin targeted introductions.