It replaces the Founderβs Reading Guide as the current interpretation authority. It does not replace the original reports. The original reports remain preserved as first-version outputs.
Version: 1.0 Prepared for: BGC Γ iBLOOMING Founders and Core Team Prepared by: Prof. NOTA Simulator owner and principal implementer: Fabio Kalandra (βUncle Kalβ) Date: 5 August 2026 Status: Active decision-support reference
This document explains:
what SIMALPHA is;
what it successfully does;
what its current data and reports support;
what they do not support;
how founders should read the first simulation results;
what must be corrected before future policy approval.
It replaces the Founderβs Reading Guide as the current interpretation authority.
It does not replace the original reports. The original reports remain preserved as first-version outputs.
SIMALPHA is an internal decision-support web application.
Its workflow allows a permitted user to:
upload or select a versioned business-data snapshot;
define or select a policy scenario;
run a deterministic simulation;
review money, ALPHA, distribution, and risk outputs;
compare completed runs;
SIMALPHA is not:
a public token;
a smart-contract deployment;
a wallet;
a cash-out system;
a treasury;
The working MVP includes:
data-snapshot versioning;
import and validation;
scenario storage;
deterministic execution;
result references;
This is a substantial technical deliverable.
The application is suitable for structured internal policy exploration.
The current compiled dataset contains:
236 records;
25 monthly periods;
April 2024βApril 2026;
BGC and iBLOOMING records;
monthly-tier aggregation.
Examples of synthetic record keys include combinations such as:
BGC + month + membership tier;
iBLOOMING + month + membership tier.
These are not persistent individual member identities.
The dataset can support:
monthly aggregate analysis;
source-system comparison;
tier comparison;
issuance and cash-release sensitivity;
cashflow-proxy discussion.
It cannot validly support:
real active-user count;
new-user count;
retained-user count;
churn;
member-level Gini;
Any metric derived by treating each aggregate record as a person must be removed or relabeled.
The dataset labels BGC cash-in as:
cash in;
recognized revenue;
gross margin.
These labels must not be interpreted as audited revenue, gross margin, profit, or free cash.
The available data does not deduct:
physical-product cost;
inventory;
shipping;
fulfillment;
operating expense;
An initial policy reference using the current model assumptions.
It is not a validated reproduction of the complete historical economy.
A lower-issuance and lower-cash-release policy.
It demonstrates sensitivity to tighter parameters.
A higher-issuance and higher-cash-release policy.
It does not demonstrate real revenue or user growth because no independent future-growth evidence is included.
The name is misleading.
The scenario:
uses the same imported historical business data;
has no meaningful future shock;
mainly lowers issuance;
tightens caps;
restricts cash-out frequency;
Correct interpretation:
Treasury Preservation / Restrictive Policy Scenario
It retains the most modeled cash because the model releases the least cash.
That is a parameter consequence, not an independent finding that the policy is best.
Replace:
Ready;
Needs Review;
Do Not Use.
With:
All four current scenarios should carry:
Preliminary Pass β Insufficient Evidence for Implementation Approval
Replace:
ALPHA is the practice version of iBC/iBTC.
With:
ALPHA is a neutral simulation unit used to test alternative representations of rights, rewards, access, or internal value. It does not imply that a public token will be launched.
Replace:
Actual Payout Out
With:
Modeled ALPHA Cash Release
Historical cash-out is a different data field and must be shown separately.
This statement must be removed.
PC and SP represent different rights.
Any future conversion must define:
which original right is extinguished;
whether conversion is reversible;
whether product or payout rights remain;
whether the conversion creates a new liability.
Replace:
Net Cash
With:
Incomplete Net Cash Proxy
Until the model includes:
rewards payable;
pools;
fulfillment;
COGS;
OpEx;
Remove or relabel:
Active User Count;
New Active User Count;
Retained Active User Count;
Affiliate Retention;
Top 10% Member Share;
Suggested label where retained:
Aggregate Segment Concentration
The current source data contains:
pool reward fields;
historical cash-out fields;
internal credit spend.
The first reports show:
pool funding owed = zero;
much lower modeled ALPHA cash release;
fulfillment cost = zero.
This does not automatically prove a software bug.
It proves that field mapping, liability treatment, or policy treatment is incomplete or undocumented.
The next technical review should trace:
SIMALPHA can support decisions such as:
whether a scenario issues more or less ALPHA;
whether cash-release restrictions retain more modeled cash;
whether report outputs change consistently;
whether assumptions are visible;
It can support the conclusion:
Do not approve current tokenization.
It cannot support the conclusion:
This system is economically safe and ready for token implementation.
Required:
versioned input;
documented mapping;
reproducible results;
no unsupported member-level metrics.
Required:
reproduce historical observed totals;
separate actual from modeled values;
explain every material difference.
Required:
PC obligations;
reward obligations;
pool obligations;
COGS;
fulfillment;
Required:
independent product buyers;
repeat purchases;
product usage;
margin;
retention;
Only after Gates 0β3:
caps;
fees;
internal access;
entitlement policy;
cash-release rules.
Compare:
conventional database;
EventHub or evidence anchoring;
non-transferable credential;
internal rights;
public token.
No token implementation before written approval.
Before reading numbers, confirm whether the report says:
actual;
modeled;
assumed;
missing;
preliminary.
A scenario is useful only when the changed rules are clear.
Always check:
obligations;
costs;
reserve;
rights;
user impact.
Every future token-related simulation must include:
No-token / conventional-system control
A simulator result should lead to one of:
reject;
study further;
request evidence;
approve limited pilot;
approve implementation.
βGreenβ is not automatically approval.
Select a versioned dataset.
Confirm source and mapping notes.
Select a scenario.
review changed parameters;
confirm actual-versus-modeled flags;
change verdict labels;
add Insufficient Evidence;
relabel cash release;
relabel net cash;
remove invalid user metrics;
reconcile pool fields;
reconcile partner payouts;
reconcile fulfillment;
trace internal credit;
document formula mapping;
calibrate against observed totals;
show differences;
explain opening and closing balances.
Add support for:
independent product demand;
direct product sale;
repeat purchase;
product margin;
digital access usage;
Apply:
new-join decline;
product-revenue decline;
cash-out increase;
PC redemption increase;
COGS increase;
SIMALPHA is a working internal decision-support MVP with preliminary policy-sensitivity outputs. It is not yet a calibrated historical economic replay, a validated sustainability model, or a basis for final token parameters.
This is not a failure.
It is the correct status for a first serious simulation product.
The next value of SIMALPHA is to support Product-Led evidence, no-token controls, and disciplined founder decisions.
P.S. Read this document freely for information and guidance. Do not redistribute or restateβno quotes, summaries, paraphrases, or derivativesβwithout prior written permission from . Sharing the link is allowed. So, share the link, not the text. Do not discuss or re-tell the contents in any formβwritten, spoken, or recordedβwithout prior written permission.
export reports for founder discussion.
an exchange;
a legal or tax engine;
an audited accounting system.
duplicate-run governance;
comparison;
data-versus-assumption separation;
report generation;
PDF export;
founder-oriented summaries.
real top earners;
P95 or P99 by person;
member-level referral behaviour;
individual cash-out behaviour;
longitudinal cross-application activity.
outstanding PC;
reward liability;
pool liability;
reserve restrictions.
raises cash-out friction.
reserve;
PC liability;
intercompany movements.
member-level Gini;
member-level P95/P99.
OpEx;
reserve;
intercompany transfers.
product-market evidence.
run the model;
review warnings and missing evidence;
compare with a no-token control;
export the result;
attach a Decision Note;
obtain named approval before changing any live system.
separate historical cash-out from modeled release;
document aggregate-data limitations;
rename Stress interpretation.
add no-token control.
product-passport adoption;
conventional-versus-Web3 cost.
OpEx increase;
reserve limitation.
Cash in
$4,034,038.00
$21,117.00
$4,055,155.00
Recognized-revenue field
$4,034,038.00
$6,335.10
$4,040,373.10
Baseline
253,462.58
47,250.55
70,138.55
136,073.48
Preliminary Pass
Run completed and did not cross current model thresholds
Material Review Required
One or more model or evidence risks require review
Model-Detected Risk
Current assumptions create a model threshold breach
Insufficient Evidence
No responsible implementation conclusion can be made
source field
β import mapping
β model variable
β formula
β report line
β founder interpretationGross-margin field
$4,034,038.00
$6,335.10
$4,040,373.10
Internal credit or sink spend
$567,234.00
$0.00
$567,234.00
PC volume
403,403,617
0
403,403,617
SP reward basis
2,823,835
0
2,823,835
Global/direct reward
$411,385.60
$1,429.46
$412,815.06
Pool reward
$508,288.57
$950.52
$509,239.09
Historical cash-out
$546,506.11
$25,715.08
$572,221.19
$3,970,234.55
0.25Γ
Conservative
185,770.06
35,690.04
37,558.99
112,521.03
$4,002,814.11
0.24Γ
Growth
304,155.10
56,173.06
85,512.27
162,469.77
$3,954,860.83
0.25Γ
Stress
128,168.01
24,016.75
29,569.66
74,581.59
$4,010,803.44
0.24Γ