Visual system

Enterprise fintech infrastructure, not AI SaaS theatre.

Segment 14 turns the visual language into controlled infrastructure: deep navy, charcoal, muted grey, restrained white, and amber only where risk or warning emphasis is useful.

Deep navy

#082052

Primary infrastructure ground and major panels

Charcoal

#0f172a

Dense text and technical surfaces

Muted grey

#64748b

Secondary copy, rules, and borders

Restrained white

#f8fafc

Readable surfaces and generous whitespace

Subtle amber

#b45309

Risk, warning, and approval-gate emphasis only

Required visuals

Every visual should clarify control.

The site should help a senior buyer understand where operating logic lives, who approves it, how runs execute, and what evidence remains.

1

Homepage hero visual

System-to-control-layer diagram, not a product screenshot.

2

Layer map

Inputs, governed operating layer, controls, and outputs.

3

Knowledge Graph visual

Structured standards, firm logic, mappings, checks, exceptions, evidence.

4

Before-and-after proof cards

Show what changed and what control record survived.

5

Six-step how-it-works visual

Source, analysis, logic, controls, deterministic run, evidence.

Component rules

Restrained systems language, explicit governance cues.

Component patterns should feel like financial operations infrastructure: maps, ledgers, gates, records, and evidence trails.

Use

Institutional sans-serif, strong hierarchy, 16-18px body text, 1.5-1.6 line height, generous whitespace.

Show

Systems, rails, records, gates, lineage, exception routing, approvals, replay, and audit evidence.

Avoid

Robots, brain imagery, AI gradients, dashboard screenshots as hero, cartoon workflows, floating particles, and neural networks.