The mechanics behind every allocation decision
Alpina Investments doesn't run on a single black-box algorithm. It runs on a defined sequence of features — input capture, band assignment, structuring, and monitoring — each one auditable on its own.
How inputs become a portfolio structure
Each feature below performs a narrow, specific job. Together they form the chain that turns a risk profile into a set of held positions.
Input Processing
Every profile begins with a structured intake: time horizon, capital constraints, liquidity needs, and stated risk tolerance. The feature set here is deliberately narrow — it captures what's needed to assign a band, and nothing that would introduce noise or subjective override into the next stage.
Inputs are versioned. If you update your profile, the prior version is retained for reference rather than overwritten, so the reasoning behind a past allocation stays visible.
- Intake fieldsFixed set
- Profile versioningRetained
- Manual weighting overrideNot permitted
Band Assignment
Inputs map to one of a fixed number of risk bands. The mapping logic is consistent across accounts — two profiles with the same inputs receive the same band, without exception handling or discretionary adjustment.
Constraint Layer
Once a band is assigned, a constraint layer defines the boundaries of what the portfolio can hold: maximum single-position exposure, minimum liquidity reserve, and permitted asset categories for that band.
Why the sequence matters
Structuring a portfolio in a fixed order — input, band, constraint, then position selection — means the same profile always produces the same structural outcome. There is no step where a discretionary call can quietly change the result. This is a design choice, not a guarantee of any particular return.
Built to be inspected, not just used
Most of what differentiates Alpina Investments isn't a single feature — it's the fact that each part of the process is separable and can be examined on its own. You can look at how your band was assigned without needing to also trust the rebalancing logic, and vice versa.
That separation is intentional. It means updates to one part of the system — say, how drift is measured — don't require you to re-evaluate the whole platform from scratch.
When each feature runs
Features don't all activate at once. Some run at onboarding, others run continuously in the background.
Data Capture
Risk inputs and constraints are recorded once, at setup, and stored as the baseline reference for everything that follows.
Band Assignment
The intake data is mapped to a fixed risk band using consistent rules, before any position is selected.
Structuring
Positions are selected within the constraint layer defined by the band, respecting exposure and liquidity limits.
Monitoring
The portfolio is checked against its own band definition on a set schedule, flagging drift before it compounds.
The safeguards running underneath the allocation
These are the features that act as boundaries — they don't select positions, they limit what the structuring layer is allowed to do.
-
01
Drift Threshold Monitoring
Tracks how far current holdings have moved from the target band and marks the account for review once a defined threshold is crossed.
-
02
Exposure Caps
Prevents any single position or asset category from exceeding the limit set by the constraint layer, regardless of recent performance.
-
03
Liquidity Buffer
Reserves a minimum portion of the portfolio in readily accessible holdings, sized according to the profile's stated liquidity needs.
-
04
Rebalance Cadence
Reviews are triggered on a fixed schedule rather than in response to short-term market moves, reducing reactive adjustments.
-
05
Profile Change Log
Every update to a risk profile is timestamped and retained, so the rationale behind a structural change stays traceable.
-
06
Manual Review Flag
Accounts that breach a threshold are flagged for review rather than automatically adjusted without visibility into the change.
What each feature does, and what triggers it
A condensed reference for how the individual controls fit together.
| Feature | Function | Trigger Condition |
|---|---|---|
| Intake | Captures risk tolerance, horizon, and liquidity needs | Account setup or profile update |
| Band Assignment | Maps intake data to a fixed risk band | Immediately after intake |
| Constraint Layer | Defines exposure and liquidity boundaries for the band | Set at band assignment |
| Drift Monitoring | Compares current holdings against target band | Scheduled review cycle |
| Rebalancing | Adjusts holdings back toward the constraint layer | Drift threshold exceeded |
| Change Log | Records profile and structural changes with timestamps | Any profile or holdings update |
Features define boundaries, not outcomes
None of the controls described above are designed to predict market movement or guarantee a return. Their purpose is to keep a portfolio aligned with the risk profile it was structured for, and to make deviations visible rather than silent. Capital remains at risk regardless of which features are active on an account.
Review the features against your own profile
If you want to see how these controls would apply to your own risk tolerance and time horizon, the next step is a profile setup — not a sales conversation.