Every capability, grounded in a published log
Dusk Fundis is built around a single principle: nothing ships until it can be measured, logged, and checked against what actually happened. Below is how that principle takes shape across the platform.
Built to be checked, not just trusted
Most allocation tools ask you to take their word for it. Dusk Fundis is structured the other way around: every output is timestamped, every input is recorded, and every log is open to review by the people using it. The features below exist to make that discipline usable day to day, not just defensible on paper.
That means fewer dashboards designed to impress, and more infrastructure designed to hold up under scrutiny — including your own.
What Dusk Fundis actually does
Each feature below is paired with the practical benefit it's meant to deliver — not a list of buzzwords, but what changes in your day-to-day workflow.
Position sizing without the guesswork
The core engine processes incoming data streams and produces allocation suggestions sized against your stated risk tolerance, not a generic template. Benefit: you spend less time second-guessing position size and more time executing a plan you already understand.
Inputs that stay current
Market and operational data feed the engine on a rolling basis rather than a periodic refresh. Benefit: recommendations reflect conditions as they stand now, reducing the lag between what the system sees and what you act on.
A record you don't have to take on faith
Every allocation call is written to a log that's visible to the community using the platform, with outcomes tracked alongside the original recommendation. Benefit: you can audit the system's track record yourself before — and after — you rely on it.
Boundaries you set, not the other way around
Allocation thresholds, exposure limits, and sizing bands are configurable per user rather than fixed by the platform. Benefit: the engine works within the limits you're actually comfortable with, instead of forcing a one-size approach.
Forecasts checked against reality
Every prediction is reconciled against its actual result and the variance is recorded, not discarded. Benefit: the gap between forecast and outcome is visible and trackable, rather than quietly disappearing into a marketing claim.
Built for one person running their own book
The interface and reporting are scoped for an independent professional managing their own capital, not a desk-sized operation. Benefit: less clutter, fewer irrelevant modules, and reporting that maps to decisions you're actually making.
From data to decision to log
The features above aren't separate tools bolted together — they form a single sequence that repeats on every cycle.
-
01
Ingestion
Incoming data is normalized and checked for completeness before it reaches the engine, so recommendations aren't built on partial or stale inputs.
-
02
Allocation Modeling
The engine generates a sizing recommendation within your configured risk parameters, drawing on the current data set rather than a static assumption.
-
03
Logging
The recommendation, its inputs, and a timestamp are written to the performance log before any outcome is known — so the record can't be edited after the fact.
-
04
Reconciliation
Once the outcome is available, it's matched against the original log entry and the variance is published alongside it, closing the loop on accountability.
Reading the log is a feature in itself
Access to the log isn't an afterthought — it's structured so you can scan recent entries and verify specific calls without digging through raw exports.
Illustrative log entries shown for formatting purposes. Actual entries reflect live account activity once configured.
Feature-specific FAQ
Can I adjust risk parameters after setup?
Yes. Risk parameter controls are designed to be revisited, not set once and forgotten. Changes apply to future allocation calls going forward.
Is the performance log editable after an entry is made?
No. Entries are written before the outcome is known and are not altered afterward. Reconciliation data is appended alongside the original entry rather than replacing it.
Does the engine work without continuous data access?
The ingestion feature is built around a rolling data feed. Without current inputs, recommendations fall back to the most recent available data, which may affect their relevance.
Can I use Dusk Fundis alongside my existing workflow?
The platform is scoped for independent use and is intended to sit alongside — not replace — the tools and judgment you already rely on.
See how these features behave on real data
Request access to the analysis and review the log for yourself before making any decisions.