Rules
Conditional logic that controls which sections appear in fund reports.
Conditional logic that controls which sections appear in fund reports.
Numbered points map to the blue chips on the screen above. Use these as talking points in the presentation.
Rules are first-class objects, not side-effects of templates. They get audited, reused, and reasoned about as a portfolio. Cost: one extra nav item. Benefit: makes the platform credible to a regulated audience.
Brand-true: on light surfaces the primary CTA flips to ink fill with mint label. Import sits next to it as outlined secondary because creating is far more frequent than importing.
Same problem as the banner but a different action: this filters the table to just the broken rules so the user can work through them. Warning treatment uses the proposed semantic token, not the decorative mint.
Schema drift is the silent killer of rule systems. Surfacing it on the library page means it's caught before someone opens a template and produces a broken report. Banner gives a one-click Review action.
Users scan for what a rule does, not what it's called. The mono font keeps field references like Volatility = High legible at small size. Truncation rather than wrap keeps row height predictable for large libraries.
Status is lifecycle (Active, Draft, Archived). Health is "is this actually running cleanly right now". Combining them would hide the most important signal: an Active rule with a missing field is the urgent case.
Matched, Field missing, Not tested, em-dash for never-run. Surfacing runtime health on a management page closes the loop between configuration and what users actually see in their reports.