Move a firm policy threshold. The entire portfolio re-grades tonight.
Your firm has policy. LTV caps, concentration limits, interest-reserve minimums, debt-service coverage floors. Most firms keep these in a Word document and reconcile by hand. In Capital Refinery they are eleven explicit knobs in a single configuration surface — and every deal in your portfolio is graded against them on the next render.
Your firm policy lives in a place the platform can't read.
The investment policy document was last updated by the CIO in March. The deal models reference the old thresholds. The covenant memos reference an older set still. The risk committee tightened the LTV cap two quarters ago in a meeting; the platform never heard.
The result is a quiet, persistent drift between what the firm formally requires and what the platform actually measures. Anything that depends on this drift — the Risk Signals scoreboard, the IC memo's "observed vs firm policy" rows, the Outliers page — silently runs against last quarter's answer.
Watch and max, in pairs.
Every threshold is explicit. There is no implicit "watch is half of max" derivation. When the firm tightens, every consumer of the policy sees the new value on the next read. No code change. No coordinated cutover. No reason-rephrasing.
The platform ships with default thresholds that match the prevailing standards in the rest of the product. Your firm sets its own values through a single configuration surface — no engineering work, no consultant project, no code change. The Risk Signals scoreboard, the "observed vs firm policy" rows in every IC memo, and the Outliers page all read from the same configured values on the next render.
What happens when you tighten a knob
Tighten max_portfolio_ltvfrom 0.80 to 0.75. Every position re-grades on the next read. Risk Signals rows that previously rendered green now render amber. The IC memo for the affected deals shows the new policy threshold in the "observed vs firm policy" row. The Outliers page surfaces the positions that crossed the new threshold. The Covenants & Breach surface re-ranks proximity-to-break with the new floor in place.
No code change. No deploy. No reconciliation memo. No consultant project to re-render the portfolio report against the new policy. The system absorbs the change and exposes the consequence.
The structural commitment
- Watch and max thresholds are explicit, paired knobs — no derivation, no implicit doubling
- Reasons cite the policy threshold inline so IC memos can show 'observed | firm policy | delta' without extra plumbing
- Tenant overrides do not require a code change — a single lookup table flips the rendered value across every consumer
- Defaults are hardcoded; overrides are additive; the system always knows which value applied at any historical point
Who reaches for this first
- CROs who need every position re-evaluated against a new policy stance overnight — not over a quarter
- CIOs who want to model the portfolio consequence of a tighter cap before committing to the policy change
- IC chairs who want the 'observed vs firm policy' row in every memo to reflect the actual policy as of today
- Auditors and LPs who ask 'what is your policy on X' and expect the answer to be a system value, not a paragraph
See your policy as a live setting the platform reads.
Bring us your investment policy document. We'll load the relevant thresholds, run your portfolio against them, and surface every position that would re-grade if you tightened a knob.