TakaCompassটাকা কম্পাস
DEMO DATA — NOT LIVEFictional educational examples · not current market guidance

Methodology, assumptions and limits

Trust and transparency

Read the rules behind TakaCompass's educational planner and the differences between the browser demo and reference engine.

TakaCompass uses deterministic code to illustrate how goals, liquidity, time horizon and risk constraints can affect a plan. The browser app is a simplified demo: its capacity score and allocation bands are rules-based teaching proxies, and its scenario chart is illustrative arithmetic. A separate reference engine contains more detailed policy and calculation logic; neither is validated personalized advice or a return forecast.

Editorial update: 2 min readRelease evidenceIndependent financial review not recorded

Suitability logic in the reference model

The reference methodology models risk tolerance, financial capacity and required risk separately. It caps the recommendation at the lower of tolerance and capacity. Emergency reserves and known near-term withdrawals are ring-fenced before an allocation is considered. If the goal requires more risk than capacity permits, goal-rescue options include contributing more, extending the horizon, reducing the target, building reserves or addressing expensive debt.

Browser demo boundaries

The shipped browser calculation in `apps/web/lib/demo.ts` is not the portfolio engine or FastAPI service. It estimates capacity from a horizon proxy, income-stability cap, loss-tolerance proxy and reserve penalty; an illustrative allocation then respects that cap and uses whole-taka rounding. Its fan chart calls `simulatePortfolioBands` to run a seeded 1,024-path monthly teaching simulation from rounded sleeve weights, hypothetical return and volatility assumptions, horizon, starting amount and month-end contributions. The displayed bands have not been validated for historical coverage. They are not forecasts or guarantees; fees, tax, inflation and withdrawals are excluded. Research rows are fictional fixture records.

Reference policy and uncertainty

The separate reference engine uses a versioned horizon/strategy ceiling, eligibility-first filtering, concentration and denomination constraints, whole-share rounding and a visible residual-cash line. Its scenario module uses a seeded random stream, monthly return draws and explicit assumptions; the stated percentiles are estimates, not forecasts. Coefficients, normal-return assumptions and historical-quantile tail measures are educational model choices, not empirically validated suitability thresholds or complete representations of market risk.

Versioning and source record

The source repository records methodology, data lineage, compliance and model limitations. A result's data and transformation dates must not be confused: effective time describes when an observation applies; retrieval time records when it was obtained. The current browser dataset is fictional and remains labelled `DEMO DATA — NOT LIVE`.

Change one assumption. See what follows.

From reading to practice

Try the idea with fictional amounts. Keep the calculation and its limitations in view.

Open the learning toolReview assumptions in Panchayat