Private evidence review · Confidential report simulation

The product is visible.
The investment case needs reconciliation.

Project Meridian · fictional specimen / Verification memorandum

A source-linked review of the commercial record, financial models, ownership design and token mechanics, with explicit conditions for reliance.

Decision use: Reliance on the commercial and transaction case
Review status: Hold at verification gate
Evidence: Public + supplied private evidence
Cutoff 12 September 2026
Prepared for / by: Commissioning investor
Luis Fontana · Mjolnir Capital

Confidential report simulation. Project Meridian is a fictionalized specimen; identifiers are changed or withheld and monetary figures are altered consistently. The analytical form, evidence treatment and decision language match the client deliverable. Informational only — not investment advice, an offer, or a solicitation.

Verification decision

Decision · Hold at verification gate

Do not rely on the financing or transaction case for investment-committee approval.

Proceed with a focused management evidence round. The product footprint is observable and several design calculations reconcile. The model also contains material reference and period defects, forecast cash includes conditional financing, and commercial performance and investor rights are not substantiated by primary records. Four critical gates—commercial proof, model repair, rights and control, and token mechanics—must close before reliance.

Simulated transaction

US$675,000

Pre-seed SAFT+T review convention.
US$5,250,000 stated valuation cap.

Raise / forecast burn

12.86 mo

US$675,000 ÷ US$52,500 monthly burn. Excludes grants; not verified current runway.

Terminal-value concentration

96.0%

Share of source-model DCF enterprise value attributable to terminal-value present value.

Report convention: US$675,000 SAFT+T and US$5,250,000 stated valuation cap. A second source states US$600,000; that conflict remains a finding. The evidence set does not define how the cap applies to token delivery. All simulated currency figures are altered consistently. The displayed cap is a represented transaction term, not a valuation opinion.

Valuation posture

The transaction price, enterprise value, token value and investor-rights value are separate questions. At the cutoff, only the proposed pricing term is stated precisely; the available evidence does not support an independent value conclusion or an ownership-equivalent calculation.

Economic object	Observed basis	Desk treatment
SAFT+T pricing term	US$675,000 proposed investment; US$5,250,000 stated valuation cap	Negotiated transaction term only. The executed instrument and cap application to token delivery are not supplied.
Operating company	Source DCF and revenue-multiple cases	Not established. Revenue paths contain reference and period defects; 96.0% of the source DCF enterprise value is terminal-value present value.
Future utility token	100m design supply, fee/burn/staking assumptions and proposed utility	Not estimable. No deployed token, enforceable holder cash-flow claim, dynamic supply ledger, principal market or observable liquidity.
Investor node right	Proposed share of a future 13% protocol-fee pool	Not estimable. Rights are unexecuted and transfer depends on eligibility, approval and an unobserved secondary market.

Priority	Finding	Consequence
Critical	Payments, paying demand and retention are not demonstrated by underlying operating records.	Do not treat the community footprint as transaction-revenue proof. DR01 · pp 8,12,20 DR03 · p 69/T7
Critical	Revenue and valuation paths have period/reference defects.	Repair and reperform the affected outputs before using them in any financing or return analysis. DR05 · P&L Model / Transaction Engine / Valuation
Critical	Runway includes assumed financing and fails to reflect the stated pre-revenue operating burn.	Obtain actual cash and liabilities, then build a reconciled monthly, grant-free case. DR05 · Cash Flow / P&L Model
Critical	Ownership, financing instruments, payment arrangements and node rights are represented rather than executed.	Instrument-level reliance requires primary corporate records, executed agreements and appropriate specialist review. DR03 · pp 241–262 DR04 · T2/T29/T30
Important	Token allocation arithmetic ties, but burn and staking scenarios are not reliable circulation forecasts.	Rebuild a dynamic supply ledger with enforceable releases, constrained burns and explicit liquidity assumptions. DR06 · Assumptions / Staking Demand / Burn Dynamics

Evidence in favor

Public app listings, a defined venue-led proposition, explicit operating hypotheses and a token allocation that sums to its stated supply. The whitepaper itself identifies payment adoption and retention as unproven.

Strongest alternative explanation

The inconsistencies may reflect different document versions and a business moving from community software into payments. That could explain some timing differences, but does not cure incorrect formulas or establish missing rights and actuals.

Scope and evidence reviewed

Question: can the available record support reliance on the commercial, funding, ownership and token mechanics of the proposed pre-seed transaction?

Six supplied files were reviewed: an investor presentation, a one-page investment summary, two narrative design documents and two workbooks. The public screen supplies separately classified observations. The review traced material claims to source sections and examined selected formulas, cached values and input relationships.

Workstream	Work completed	Material limit
Commercial and people	Compared product, traction, partner, founder and competitive representations with public records.	No management interview, customer reference, production demonstration or cohort export.
Financial model	Inspected key operating, cash and valuation paths; independently recalculated selected material equations.	No bank/accounting records; no complete spreadsheet-engine recalculation or audit of every formula.
Rights and control	Mapped proposed entities, instruments, fee rights, governance and exit terms.	No executed instrument, register, corporate authority, IP assignment or intercompany agreement.
Token scenarios	Checked allocation totals, selected node/fee arithmetic, burn headroom and model structure.	No authenticated deployment, contract audit, wallet ownership proof or executable monthly supply schedule.
Response process	Prepared a prioritized question register and proposed closure tests.	Questions have not been sent; management responses and the client readout have not occurred.

Specimen convention. Project Meridian is a fictionalized case used to show the exact report form. The report applies a fixed simulated transaction of US$675,000 under a SAFT+T with a stated US$5,250,000 valuation cap. Company, person and location identifiers are masked; monetary values are altered consistently. Source IDs and locators remain available in the controlled evidence record.

Materiality is qualitative: a critical item can change reliance on revenue, funding, ownership, control or the investment instrument. An important item affects execution, interpretation or confidence. These priorities are not a probability score or an investment rating.

Download the supporting evidence workbook

Material claim register

Every material investment claim is classified by what the reviewed record actually supports. “Supported as design arithmetic” confirms only the calculation—not demand, enforceability or implementation.

Claim	Status / priority	Evidence-based treatment	Closure
C01 Product is available	Supported within limits Important	Listings support app availability, not functionality or active use. PS03 PS04	Production walkthrough and activity exports
C02 Payment operations and transaction revenue are established	Unresolved Critical	Pilot, live and not-activated descriptions are not reconciled; no transaction or settlement records. PS02 DR01 DR02 DR03	Q01
C03 Traction shows retained paying demand	Unresolved Critical	Community, registered users, active users and venue reach are not interchangeable; retention and payer data absent. DR01 DR02 DR03	Q02
C04 Partner relationships generate incremental business	Unresolved Important	Active, pipeline and LOI populations mixed; QR deployment is described as planned and completed. DR01 DR03	Q03
C05 Customer acquisition cost is zero	Not established Important	No advertising spend does not establish zero fully loaded acquisition cost; founder, sales, incentives and deployment costs are not reconciled. DR01 DR02 DR03	Q02
C06 Company identity and rights chain are clear	Unresolved Critical	Public operating entities differ from the proposed OpCo/Foundation labels; IP, ownership and intercompany rights not documented. PS01 PS03 DR03 DR04	Q04
C07 Financing ask and runway reconcile	Unresolved Critical	The report convention is US$675k with 12 months stated. A second source states US$600k with 18 months. The spending basis also differs. DR01 DR02 DR03 DR05	Q05
C08 Forecast cash represents available runway	Contradicted within model Critical	Pre-revenue operating expense disappears in revenue-linked costs, while conditional grant financing enters cash. DR05	Q06
C09 Revenue paths use consistent units and populations	Contradicted within model Critical	Different addressable populations and a monthly formula labeled annual prevent reconciliation. DR05	Q06
C10 Displayed valuation cases calculate correctly	Contradicted within model Critical	Shifted formulas zero early cases and use prior-period values in later cases. DR05	Q06
C11 DCF provides robust valuation support	Not established Important	Approximately 96% of modeled enterprise value is terminal-value PV; assumptions and revenue path remain unsupported. DR05	Q06
C12 Fee distribution and operating-company revenue tie	Supported as design arithmetic Important	At illustrative US$150m monthly GMV the stated rates yield US$72m annual protocol fees and US$15.795m annual OpCo revenue. Licensing is an intercompany flow; treasury sustainability remains unproven. DR04 DR03	Q07
C13 Token allocations reconcile	Supported as design arithmetic Important	100m tokens allocated; 18m initial modeled circulation. Enforceability and release schedule remain unverified. DR04 DR06	Q08
C14 Burn scenarios respect the supply floor	Contradicted within model Critical	Unbounded annual burn 129.6m exceeds 100m supply; only 60m can burn before 40m floor. DR06	Q08
C15 Staking and stress outputs are reliable dynamic scenarios	Not established Important	Staking columns are misaligned and six economic tables are static. DR06	Q08
C16 Investor node income and exit rights are executable	Unresolved Critical	Income math works at assumed scale; no executed rights or observed resale liquidity; no protocol redemption is proposed. DR04 DR06	Q09
C17 Legal classifications and payment permissions are established	Not established Critical	Opinions, provider contracts and offering records not supplied. Exemption language is not evidence of registration or approval. DR04 PS10	Q10
C18 Privacy and data rights support the business model	Unresolved Important	Platforms display different collection declarations; controller roles and monetization permissions need confirmation. PS03 PS04 DR01 DR03	Q11

Priority reflects potential effect on investment reliance. Status is evidence-based at the cutoff and may change when the stated closure evidence is supplied.

Commercial evidence and execution

Community activity has not yet been connected to payment economics

The presentation combines registered users and a waitlist in a headline community figure, separately describes active users, and includes venue visitors and pipeline reach. The summary and whitepaper use a smaller registered-user population. The populations and dates are not reconciled; they should not be presented as evidence of contraction or growth without a bridge. No analytics export establishes a paying cohort, repeat usage or retention.

Payment descriptions range from a pilot to live first venues to not yet activated. Subscription revenue and transaction revenue also need to be distinguished: a platform can have paying software customers before processing marketplace payments. The reviewed record supplies no billing, transaction or settlement population with which to resolve that distinction. DR01 · pp 7,12–14,20 DR02 · traction/execution plan DR03 · pp 58–72/T7 PS02

The stated funnel does not reach the stated first-year range

Using the whitepaper’s own Year 1 assumptions, 20,000 registered users, 30% monthly activity and 20% wallet adoption imply 1,200 transacting users. At five transactions and an illustrative US$45 transaction value, that produces US$270k monthly gross merchandise value (GMV).

20,000 × 30% × 20% × 5 × US$45 = US$270,000 monthly GMVDR03 Tables 3–5. Currency amounts altered; the conversion rates and user count are source assumptions. This is a desk reconciliation, not observed usage.

The same document targets US$750k–1.5m monthly GMV in Year 1. Under the same spending assumptions, that requires approximately 3,333–6,667 monthly transactors: 2.8–5.6 times the transactors produced by the stated funnel. Management must identify whether the target assumes more registered users, higher conversion or different spending behavior.

A second planning mismatch remains: the staged table presents US$7.5m monthly GMV for Years 2–3, while the scenario table labels US$45m monthly GMV as its Year 3 base case. Different cases may be intended, but no selected case reconciles the two. DR03 · T5/T6

Partner reach, acquisition costs and defensibility need evidence

The record mixes active relationships, pipeline, letters of intent and audience reach. Deployment is described as both planned and completed. No contract schedule, billing or attribution data establishes incremental partner revenue. Zero advertising spend also does not establish zero fully loaded acquisition cost: founder time, sales, field deployment, events and incentives still need treatment. DR01 · pp 12–16 DR03 · pp 58–66/T7

The proposition has a coherent venue-led acquisition hypothesis, but the presentation overstates competitive separation. Luma supports ongoing memberships; WhatsApp supports business catalogs. Those features challenge blanket claims that incumbents lack community continuity or a business surface. They do not show that Meridian has no differentiation. The required test is customer preference and repeat economics. DR01 · p 6 PS08 PS09

Team execution and concentration

The materials assign leadership, operations, legal and advisory roles and describe prior commercial experience. These remain representations. Confirm the current full-time roster, payment and technical ownership, related-party arrangements and reliance on founder-led partner acquisition. External references and individual background checks were not performed.

Stage-appropriate treatment. Pre-revenue status is not a rejection criterion. It changes the evidence required: technical feasibility, customer need, credible production milestones and the capital needed to test adoption.

Underwriting the next milestone

The central hypothesis is that venue-led distribution can produce repeat paid activity at a sustainable contribution margin. The next investment milestone should test that hypothesis with a defined production cohort, rather than a larger undifferentiated audience count. Track activation, repeat payments, retained paying merchants and margin after processing, cashback and attributable acquisition costs. Agree success thresholds before the pilot; the present record does not justify numerical thresholds.

Link the pilot budget to the cash required to reach and measure that milestone, including a delayed-launch case and a funding contingency. Evidence of paid repeat use would strengthen the case. Usage that disappears when incentives end, or persistently negative contribution economics without a credible remedy, would weaken it. These are proposed decision tests, not observed outcomes.

Funding and financial-model integrity

The ask, cap and spending basis are not one approved transaction

Record	Illustrative representation	Treatment
DR01 presentation	US$675k raise; 12 months; US$1.95m grant leverage	Management representation. Grant award and timing not evidenced.
DR02 summary / DR03 whitepaper	US$600k raise; 18 months; US$5.25m stated cap	Conflicts with the report convention. The cap’s application to token delivery is not defined.
DR05 modeled capitalization	A hardcoded capitalization schedule and a US$4.5m post-money entry	A modeled cap table is supplied. No shareholder register or executed conversion instrument substantiates it.
DR01 / DR05 forward spending	US$52.5k monthly planned burn	Different from the lower founder-era burn representation; requires a staged budget.

The relationship among the stated SAFT+T cap, modeled post-money value, capitalization schedule and token entitlements is unresolved. A mechanical ownership, token-delivery or return model would give false precision without the executed instrument and its valuation-cap definition. DR01 · pp 15,19–20 DR02 · header DR03 · pp 264–268 DR05 · Cap Table!C21:E24; Assumptions!C52

Grant-free coverage is materially shorter than the cash model suggests

US$675,000 ÷ US$52,500 = 12.86 monthsSimple coverage of the fixed simulated raise by the stated forward monthly burn. This excludes opening cash, liabilities, revenue, fees, grants and spending changes; it is not actual runway. The separate US$600,000 source claim is recorded as a document conflict, not used as the transaction case.

The source cash model reports approximately 53.3 months of runway after including the grant and modeled income. In the pre-revenue year, percentage-of-revenue expenses fall to zero despite the separate monthly burn assumption. A hardcoded interest-income line contributes positive net income. The error is structural: conditional financing and incomplete cash operating costs inflate coverage.

The use-of-funds sheet separately totals an illustrative US$550.5k for the first year, another spending basis to reconcile. Cash-flow entries also assume a US$3m seed round and US$15m subsequent round. None of these modeled inflows establishes money available today. DR05 · P&L Model!C25:C40; Cash Flow!C16,D17,F18,C24:C26; Use of Funds!F18

Two operating paths produce different revenue foundations

Year 2 model path	Source equation after anonymization	Result
P&L Model	33,600 users × US$15 daily spend × 10 active days per month	US$5.040m monthly GMV, although the output is labeled annual.
Transaction Engine	21,840 users × US$15 daily spend × 10 active days per month × 12 months	US$39.312m annual GMV.
Same-period comparison	Annualize the P&L calculation before comparing	US$60.480m versus US$39.312m. A missing × 12 does not explain the different user populations.

The P&L and transaction engine use different addressable populations. Repair the population, period labels and fee calculations together; correcting only the annualization factor would leave a substantive inconsistency. DR05 · P&L Model!D9:D18; Transaction Engine!D12:D21

Revenue-multiple formulas reference the wrong columns

The low, base and high revenue-multiple formulas shift the referenced input columns. Early displayed values become zero; later cases use earlier-year inputs. A selected same-column reconstruction of the low case is shown below. These are corrected arithmetic illustrations, not endorsed valuations.

Forecast column	Revenue input	Low multiple	Correct same-column product
Year 2 / D	US$705,960	6×	US$4,235,760
Year 3 / E	US$2,599,542	7×	US$18,196,794
Year 4 / F	US$7,806,870	8×	US$62,454,960
Year 5 / G	US$18,299,250	9×	US$164,693,250

For example, D22 uses B18× B19 rather than D18× D19. The numerical ranges cannot be relied on until the model is repaired and its operating assumptions are supported. DR05 · Valuation!D18:G24

Terminal assumptions dominate the DCF

Terminal-value PV

96.0%

Operating cash-flow PV

4.0%

DR05 Valuation!C12:C14. Ratio calculated from stored outputs and independently checked.

The source’s discounted cash flow (DCF) result depends chiefly on a Year 5 revenue multiple, discounted at 35%. Scenario discipline is appropriate, but neither this model nor its arithmetic repair establishes a defensible transaction valuation. Revenue quality, capital needs and investor rights still require evidence.

Ownership and economic rights

The design separates the consumer operating company, a protocol foundation and three investor exposures. The legal and operational links have not been established.

Proposed cash-flow design

Customer spendingPayment/settlement provider not evidenced

Protocol foundation4% network fee in the design

Operating companyLicensing, SaaS and processing margin

Protocol allocationsTreasury, operators, buybacks, nodes, community

The public operating entity, a legacy company reference and the design’s proposed OpCo/Foundation labels need an entity reconciliation. The diagram is a description of management’s design, not evidence of incorporation, IP ownership or enforceable cash-flow entitlement. PS01 PS03 PS04 DR03 · pp 241–262 DR04 · T2–T4

Exposure	Economic design	Missing reliance evidence
SAFT+T	Future token delivery with proposed companion economic rights	Exact issuer; application of the valuation cap; token-delivery formula; network-launch trigger; long-stop and termination rights; vesting, transfer, information and amendment terms; authority to issue.
Utility token	Governance, consumer benefits and buyback/burn exposure	Token entitlement; amendment authority; no inferred right to corporate cash flows; deployed supply and custody controls.
Investor node	Share of a future 13% fee pool; no operating obligation; transfer subject to eligibility and approval	Executed node instrument; activation conditions; number of participating nodes; amendment rights; eligible transfers; fee and exit terms.

What the design arithmetic does support

At illustrative US$150m monthly GMV, the 4% network fee produces US$6m monthly fees, or US$72m annualized. The stated 12.5% licensing fee yields US$9m annual OpCo licensing revenue; the SaaS and processing assumptions produce total OpCo revenue of US$15.795m. The arithmetic ties. The GMV, paying-merchant population, margins and agreements do not have underlying support. DR04 · T4

Avoid double counting. The OpCo licensing fee is paid from the protocol structure. Adding total protocol fees to total OpCo revenue without eliminating that intercompany flow would overstate combined external economics. Legal entities and accounting presentation still require confirmation.

Infrastructure and legal claims require their underlying documents

The design describes an embedded wallet, card/BIN sponsorship, third-party stablecoin conversion and no direct custody. No processor, sponsor, settlement contract or responsibility matrix is supplied. No deployed contract address or wallet-control evidence establishes the token design in production. DR03 · pp 103–106,258–262 DR04 · pp 327–329,384–391

The paper states that legal opinions establish token classifications across operating markets. Those opinions were not supplied. It also combines registration terminology with exemptions. SEC guidance distinguishes registration from exempt offerings; the wording does not prove either compliance route. Instrument classification, offering permissions, transfer restrictions and payment responsibilities require qualified counsel on the actual facts. DR04 · pp 310–323 PS10

Targeted checks for misstatement and misuse of funds

Model defects and inconsistent claims are reasons to obtain better evidence, not findings of fraud. The proposed payment, incentive and related-entity flows create specific control questions. Apply the following tests once underlying records are available; none was completed in this review.

Exposure	Evidence and test	Decision relevance
Revenue existence and cutoff	Trace selected recorded transactions through processor settlement, bank receipt and the accounting ledger; examine refunds and period-end reversals.	Separates earned revenue from gross payment volume, conditional activity and timing differences.
Incentive-driven or duplicate activity	Reconcile cohort totals to identifiable events; examine repeat devices/accounts, refunds and cashback circularity using appropriately authorized data.	Tests whether reported adoption represents incremental economic demand.
Related-party and intercompany flows	Obtain beneficial ownership, conflict declarations, agreements and approvals; reconcile both sides of transfers.	Tests entitlement, disclosure and potential double counting or leakage.
Treasury and payment authority	Inspect signer/access roles, approval limits, reconciliations and changes to payout addresses; test a sample against approvals.	Establishes whether one person can initiate, approve and conceal a transfer.

These are risk-directed follow-up procedures. The supplied narratives and models cannot establish that these controls exist or operate effectively.

Token and treasury mechanics

Allocations tie, but releases and tradable float are not proven

Design allocation	Tokens	Share
Network expansion	40m	40%
Ecosystem treasury	15m	15%
Private investors	15m	15%
Team/advisers	12m	12%
Protocol liquidity	10m	10%
Public distribution	8m	8%
Total	100m	100%

The modeled initial circulation is 18m tokens: 8m public distribution plus 10m protocol liquidity. The design states an 18-month team cliff followed by 36-month vesting and a 12-month investor cliff followed by 24-month vesting. A monthly allocation-linked supply ledger is not supplied. Protocol liquidity is not automatically equivalent to freely tradable float; treasury authority, pool structure and amendment powers still matter. DR04 · T5–T7 DR06 · Assumptions!C21:C27; Staking Demand!C27:D33

The worked transaction example contains a tenfold fee error

The token paper’s transaction example shows an illustrative US$450 purchase and US$1.80 fee despite a 4% stated rate. The correct fee is US$18.00. This is a verifiable arithmetic defect; it does not establish that live transactions have been charged incorrectly.

At-scale allocation	Share of fee	Correct amount on US$450 transaction
Treasury	23%	US$4.14
Operators	25%	US$4.50
Buyback and burn	27%	US$4.86
Investor nodes	13%	US$2.34
Community	12%	US$2.16
Total	100%	US$18.00

Reperformed from DR04 Table 15. The large-scale fee schedule elsewhere does calculate the 4% correctly. Correct the example and determine which specification governs implementation.

Unbounded burns exceed the available supply

US$150m × 4% × 27% ÷ US$0.15 = 10.8m tokens per month
10.8m × 12 = 129.6m tokens per year
100m supply − 40m floor = 60m tokens available before the floorDR06 Burn Dynamics!E20/E32; Assumptions!C20/C28. Token price and currency scale altered consistently. This is a constant-price illustration, not a price or liquidity forecast.

The annual table exceeds even the total supply; a constrained model must stop or change regime at the floor and handle the partial period. At constant assumptions, the 60m headroom lasts about 5.56 months. In practice execution price, liquidity and prior burns would change the path.

Staking and stress tables require reconstruction

Staking headers and values are misaligned, so the displayed base lock and token-demand result cannot be used with confidence. Six economic/stress worksheets contain stored outputs rather than formulas. Several selected calculations are correct, but changing assumptions will not update those tables. They are static scenario illustrations, not a functioning integrated stress model. DR06 · Staking Demand!C4:I10; Fee Distribution; Burn Dynamics; Operator Node P&L; Investor Node Yield; Treasury Sustainability; Sensitivity Matrix

Treasury headroom is sensitive to cashback participation

At illustrative US$150m monthly GMV	Monthly amount
Treasury allocation: 23% of 4% fees	US$1.380m
Less OpCo licensing: 12.5% of protocol fees	US$0.750m
Residual before cashback and other operating costs	US$0.630m
Source illustration: 30% of GMV eligible at 1% cashback	US$0.450m cashback; US$0.180m residual
Desk sensitivity: 50% eligible at 1% cashback	US$0.750m cashback; US$0.120m deficit before other costs

The paper acknowledges that cashback rates are adjustable. The desk sensitivity demonstrates why eligible spend, rate governance and the operating budget must be modeled together. It does not assume the stressed participation rate will occur. Activation of the reserved investor pool also removes its temporary contribution to treasury. DR04 · pp 153–159/T13

Node income is conditional; transferability is not assured liquidity

US$75m monthly GMV × 4% × 13% ÷ 500 nodes = US$780 per node per monthUS$9,360 annualized; a US$15,000 purchase divided by this income gives a simple 1.60-year payback at constant scale. No discounting, tax, interruption or resale loss is included. DR06 Investor Node Yield!D10:F10; DR04 T29.

The proposed node has no protocol redemption. Exit relies on an eligible secondary buyer, approval and a 5% transfer fee, with a 90-day preparation/unbonding period during which yield ceases. The design allows cancellation during that window, but supplies no observed secondary liquidity or executable protections. Neither the cap of 500 nodes nor a projected yield establishes realizable investment returns. DR04 · T29–T30/pp 420–430

Conditions and management questions

The review is complete for the available record. The substantive evidence gaps remain open.

The questions below are prepared for a management round. They have not been sent and no management answers are represented as received. Owners are proposed roles, not assigned individuals. Deadlines must be agreed with the commissioning investor and management.

Gate	Evidence required before relying on the affected claim
Commercial	Dated cohort and payment records reconcile activity, payer conversion, repeat use, revenue and settlement; representative partner evidence supports actual activity.
Financial	One selected operating case and period convention; corrected valuation references; monthly fixed-cost budget; bank/liability bridge; grant-free and delayed-funding cases.
Rights and control	Exact issuer and beneficial ownership; current register; executed instrument and token rights; authority/IP/intercompany agreements; payment and custody responsibilities.
Token mechanics	Authoritative terms; dynamic vesting/circulation ledger; constrained burns; consistent staking assumptions; executable governance/transfer controls where deployed.
Specialists	Qualified counsel resolves instrument/operating questions; technical and financial specialists address the specific items outside this review.

Q01 · Payments and revenue

Proposed owner: CEO / payments lead

Required record: Dated production status by feature, live merchant list, PSP/card agreements, transaction logs, refunds and settlement records

Closure test: Reconcile one period from transaction population to recognized revenue and settled cash