Investment Committee
Cover Memorandum
Project Meridian · Proposed US$675,000 SAFT+T digital-asset investment at a stated US$5,250,000 valuation cap, with company and token rights requiring further verification.
Confidential report simulation. Project Meridian is fully fictional; every entity, person, source and figure is synthetic. The analytical form, evidence treatment and decision language match the intended client deliverable. Informational only — not an offer or solicitation. The commissioning investor retains the final decision.
Decision ask
Do not approve, sign or fund the proposed US$675,000 SAFT+T at the stated US$5,250,000 cap.
The product footprint is observable and selected design arithmetic reconciles. Payment activity and paying demand are not evidenced by primary records; revenue, valuation and runway outputs contain material defects; forecast cash includes conditional financing; and the ownership, token-delivery and node-right chains are unexecuted or unresolved.
Mandate fit
| Dimension | Assessment |
|---|---|
| Exposure | Early-stage company, future token and proposed node economics with uncertain timing, enforceability and liquidity. |
| Potential fit | Could fit a high-risk digital-payments mandate if milestones, rights and downside are documented. |
| Current fit | Fails the fictional mandate’s 5.00% minimum ownership test because ownership cannot be calculated. |
| Main mismatch | Operating-company, token and node economics are combined without an executed rights chain or reliable return model. |
| Next step | Conditional diligence; no investment approval or funding authorization. |
Investment thesis and dissent
Product and payments
Public listings support a visible venue-led proposition. Actual payment operations, transaction revenue, payer conversion and retention are not supported by primary records.
Network and token
The design allocates 100m tokens and describes fee, staking, burn and node concepts. A dynamic supply ledger, constrained release controls, deployed infrastructure and liquidity are absent.
Financing and upside
The raise could cover 12.86 months at the stated burn, excluding grants. That is a desk calculation rather than verified runway.
Dissent / alternative explanation
A transition from community software to payments may explain version differences. It does not repair formula defects, establish actuals or create enforceable investor rights.
The upside case requires three unverified transitions at once: visible product use must become paid transaction volume, forecast economics must become cash generation, and proposed rights must become enforceable and liquid.
Evidence ledger
| Finding | Status | IC treatment |
|---|---|---|
| Public product footprint | Supported within limits | Evidence of listings and availability; not proof of functionality or active use. |
| Token allocation arithmetic | Supported as design arithmetic | 100m allocation ties; enforceability and release remain unverified. |
| Payment operations and revenue | Unresolved | Require transaction, processor, settlement, refund and accounting records. |
| Paying demand and retention | Unresolved | Require dated cohorts, payer definitions, repeat use and retention exports. |
| Revenue and valuation model | Contradicted within model | Repair periods, references, populations and formulas. |
| Forecast runway | Contradicted within model | Rebuild from actual cash, liabilities, fixed costs and grant-free assumptions. |
| Investor rights and ownership | Unresolved | Require executed instruments, registers, authority, IP and intercompany agreements. |
| Burn and staking scenarios | Not established / contradicted | Rebuild dynamic supply, floor constraints and scenario formulas. |
| Legal, payments and privacy perimeter | Not established | Obtain qualified specialist review and underlying agreements. |
Valuation and return posture
| Economic object | Available basis | Underwriting treatment |
|---|---|---|
| SAFT+T | US$675,000 proposed investment; US$5,250,000 stated cap | Negotiated term only; executed instrument and cap application are not supplied. |
| Operating company | Source DCF and revenue-multiple cases | Not established; revenue paths and valuation references require repair. |
| Future utility token | 100m design supply; fee, burn and staking assumptions | Not estimable; no deployed token, enforceable cash-flow claim, principal market or observable liquidity. |
| Investor node | Proposed share of future 13% protocol-fee pool | Not estimable; rights are unexecuted and resale liquidity is unobserved. |
No reliable ownership percentage, token entitlement, dilution outcome, cash yield, exit value or expected return can be calculated. A mechanical return case would imply precision that the executed instrument, operating actuals, token controls and liquidity evidence do not support.
Key risks
| Priority | Risk | Consequence |
|---|---|---|
| Critical | Payment activity and paying demand are not evidenced. | Product visibility may be mistaken for revenue traction. |
| Critical | Revenue and valuation formulas contain reference and period defects. | Forecast value and return outputs cannot be relied upon. |
| Critical | Runway includes conditional financing and inconsistent burn bases. | Actual financing need and survival period are unclear. |
| Critical | Issuer, ownership, instrument and node rights are unresolved. | Entitlement, dilution, control and recourse cannot be established. |
| Critical | Token burns can exceed the supply floor in the stated scenario. | Supply and value mechanics are not internally constrained. |
| Important | Protocol liquidity is treated as potential float. | Tradability and exit assumptions may be overstated. |
| Important | Treasury headroom is sensitive to cashback participation. | Higher participation can create a deficit before other costs. |
| Important | Legal, payments and privacy claims lack underlying records. | Execution, regulatory and data-use risk remains open. |
Hard conditions to reopen
| Gate | Reopen only when the record includes |
|---|---|
| Commercial proof | Dated transaction and payment records reconciling activity, conversion, repeat use, revenue, refunds, settlement and cash. |
| Model integrity | One approved case, consistent periods, corrected valuation formulas, fixed-cost budget and grant-free/delayed-funding cases. |
| Rights and control | Exact issuer and beneficial ownership, current registers, executed SAFT+T/node forms, delivery mechanics, authority, IP, custody and payment responsibilities. |
| Token mechanics | Authoritative vesting/circulation ledger, constrained burns, consistent staking, governance controls and deployed enforcement. |
| Legal and infrastructure | Qualified counsel review of instrument, offering, jurisdictions, PSP/BIN sponsorship, data roles and permissions. |
| Governance and capacity | Current roles, commitments, incentives, related parties, decision rights and operating capacity. |
IC decision record
The appropriate action is to require primary evidence. A future approval must rest on reconciled actuals, repaired models, executed rights and a constrained token and liquidity framework.
Basis and limitations
This cover memorandum is the decision layer above the detailed verification memorandum and evidence workbook. It does not replace the source-linked finding register. Project Meridian remains a fictionalized, anonymized specimen with consistently transformed monetary figures.
Open the fictional evidence room Open the investor challenge brief