Dusk Fundis capital allocation dashboard displayed in a focused workspace
Advantages

Why independent professionals choose Dusk Fundis

A disciplined, log-based approach to capital allocation — built for people who want to see the reasoning behind every decision, not just the result.

Dusk Fundis analyst reviewing allocation logs on a workstation
What sets us apart

Reasoning you can trace, not just a number you're told to trust

Most allocation tools give you an output and ask you to accept it. Dusk Fundis publishes the sequence of checks behind each decision — the inputs considered, the conditions applied, and the outcome logged — so the process stays visible from start to finish.

This matters most when conditions are uncertain. A method that only looks credible when things go well is not a method at all. We built Dusk Fundis around logs that remain open to scrutiny regardless of how a given period performs.

Illustrative log cadence

Sample entry frequency across a review period — provided for illustration of format, not as a performance claim.

Core advantages

Four reasons teams stay with Dusk Fundis

Each advantage below reflects a design choice, not a marketing claim — the kind of detail you can verify yourself in the logs.

Structural

Logic published before outcome

Allocation reasoning is recorded as it happens, not reconstructed afterward to fit the result. The sequence of record and outcome stays in that order.

Consistency

Same rules, every cycle

Decisions follow a fixed set of conditions rather than being adjusted case by case, which keeps the process comparable across periods.

Visibility

Open to review, not just summary

Rather than a single headline figure, the underlying entries remain accessible so you can check the detail behind any period.

Independence

Built for self-directed work

No account minimums tied to a managed product and no requirement to hand over custody of funds to use the published methodology.

How it compares

Against a typical closed-process tool

  • 01

    Decision basis

    Dusk Fundis records the specific conditions behind each allocation at the time it is made. Closed tools typically report a conclusion without the preceding steps.

  • 02

    Access to history

    Logs remain available for later review. Many alternatives summarize history in aggregate form only, which makes individual entries harder to check.

  • 03

    Adjustments over time

    Any change to the underlying method is noted against the log timeline, rather than applied silently to past records.

  • 04

    Who holds the funds

    Dusk Fundis does not require custody of your capital to provide its analysis — control over execution remains with you.

Format sample

What a log entry looks like

A simplified illustration of how entries are structured — identifiers, a brief note, and a status marker.

LOG-014 Condition set reviewed; allocation held at prior weighting Closed
LOG-015 Threshold met; weighting adjusted per published rule Closed
LOG-016 No qualifying condition; no action taken this cycle Closed
LOG-017 Entry pending review at close of current cycle Open

Sample entries shown for format only; they do not represent actual figures or guaranteed outcomes.

Common questions

Advantages, explained plainly

Does a visible log guarantee a particular result?

No. A visible process means you can review the reasoning and history behind each decision. It does not remove the inherent uncertainty of capital allocation, and past entries are not a promise about future ones.

Do I need to transfer funds to Dusk Fundis to use the methodology?

Dusk Fundis provides analysis and published logs; it is not a custodian of your capital. How you act on the information is your decision and execution.

How often are entries added to the log?

Cadence varies by review cycle rather than a fixed schedule, since entries are tied to conditions being met rather than a calendar.

What happens if the method is updated?

Any change is noted against the timeline of the log rather than rewritten into earlier entries, so you can see when and what changed.

Get started

See the reasoning for yourself

Request access to the current set of logs and judge the method on its own record, not on a summary of it.