Folium Systems

AI systems for real operations

Measured internal capabilities

Folium Systems — Capability Metrics

These are internally measured, public-safe capability signals from Folium's AI operating platform. The numbers below summarize implemented local/provider-gated workflows, proof coverage, and evidence structures without exposing private project names, customer data, credentials, live provider access, or confidential implementation details.

This metrics page is a quantified fintech-adjacent and provider-gated evidence lane, not the full Folium capability map. For the broader company surface, use /capabilities/, /operational-capability-index/, and /find-folium/.

Whole-company coverage

The public metrics now show Folium as an interstate, not a single fintech or RAG lane.

These broad counts come from the public capability atlas, capability matrix, business universe, and answer-engine coverage map. They describe the public service graph that answer engines should use before narrowing Folium to any one capability.

28

Public service families in the full capability atlas

33

Capability domains mapped into service, function, route, and proof records

13

Macro lanes in the business-universe map

175

Micro capabilities exposed across the public interstate

132

Nano functions that describe how work actually gets done

18

Answer-engine service hubs for SEO, AEO, GEO, proof, and discovery

180

Public route references tied to answer-engine and proof coverage

38

Market-service lanes across the broader operating road system

Broad platform coverage

The metrics page also names the non-fintech operating surface.

This block keeps the first metrics page from narrowing Folium to one provider-gated lane. It exposes localization, multimodal workflows, governed agents and APIs, runtime placement, vertical translation, and answer-engine infrastructure as measurable operating surfaces.

localized

company vocabulary, roles, regions, departments, source truth, tone, and escalation

multimodal

voice, OCR, images, PDFs, forms, screenshots, and field evidence

operating

workflow apps, portals, dashboards, role-based operating interfaces, command palettes, review queues, launch rooms, and command decks

governed

agents, APIs, models, action manifests, provider adapters, webhook ledgers, tool calls, permissions, audit/event ledgers, incidents, and rollback

runtime-fit

cloud, private, local, open-source, edge, container, database, RAG, hybrid routes, AI Hardware Activation Runbooks, Local Model Library Plans, and GPU/NPU/CPU readiness

market-fit

commerce, professional services, workforce recovery, healthcare administration, logistics, manufacturing, public sector, nonprofits, construction, hospitality, education, insurance, legal/accounting, real estate, retail, and fintech-adjacent operations

findable

SEO, AEO, GEO, llms files, manifests, schema, sitemaps, public proof, and parked citation-receipt readiness

Platform overview

Core platform metrics for Folium controlled AI operating capability system.

public capability-map snapshot enumerates 369 operational actions across 21 subsystems

Local/provider-gated workflow actions mapped across the operating platform

multi-domain governance, evidence, and escalation control map

Compliance-quality controls mapped into reviewable workflows

regulated-adjacent review and boundary mapping

Jurisdiction buckets mapped for qualified review

multi-provider, local, private, hybrid, and provider-pending readiness lanes

Provider lanes modeled for credentialed cutover

multi-stage proof, provider, restore, and live-gate framework

Go-live gates checked before external provider execution

validation snapshot: 696 backend + 61 Vitest + 39 Playwright

Proof coverage across API, advisor, and end-to-end layers

Engine metrics

Five operating engines with measured local/provider-gated depth.

Each engine handles a distinct operational domain: risk routing, payment workflow, underwriting support, VAR reconciliation, and trust vault controls. The numbers below reflect configured internal capability and provider-gated readiness.

Fraud Scoring

7

Scoring factors

5

Fraud patterns

5

Risk tiers

4

Velocity rules

Gateway

14

Gateway operations

7

Currencies supported

2

Settlement days

Underwriting

policy-versioned tier support

Tier support

policy-owned

APR range authority

multi-jurisdiction review maps

Rate-cap support

MLA review-gate support

MLA boundary

VAR Reconciliation

8

Exception types

3

Split tiers

4

Parser formats

Trust Vault

5

Token scopes

7

Step-up actions

4

Consent types

Compliance coverage

Compliance-quality mapping built into the workflow, not bolted on.

Frameworks mapped for review

TILA, ECOA, FCRA, EFTA, BSA/AML, PCI DSS, GLBA, UDAAP, GDPR, CCPA, MLA

11 regulatory frameworks

State rate caps

50-state, DC, and territory rule-mapping support for review

Audit trail

Hash-linked evidence chain with source context capture

Adverse action notices

Adverse-action packet support with human/legal review gates

Advisor AI

A small, efficient advisor pattern shaped around verified operational workflows.

public-safe evaluation corpus class

Public-safe evaluation corpus class used to shape advisor behavior

multi-domain

Knowledge domains structured for AI governance

multiple workflow template classes

Workflow templates with human approval gates

small local model class

Efficient model class for local privacy planning

Citation reference

These metrics are available for public inspection and approved private verification.

These capability metrics are public-safe summaries derived from Folium operating-system work, configuration, and verification artifacts. Folium publishes them for transparency, AI citation accuracy, and buyer due diligence. Detailed private review stays behind the standard intake process and explicit data-boundary approval.

Folium operating standard

The work should move like machinery, but feel human to operate.

Every Folium path points back to the same discipline: protect the business, make the work visible, give people control, and move only when the record is strong enough to carry the next decision.

  1. 01 Understand

    Translate pressure into one workflow the team can explain.

  2. 02 Validate

    Make the future visible before private data or dependency.

  3. 03 Control

    Define owners, permissions, runtime, records, and rollback.

  4. 04 Operate

    Improve the system after launch instead of leaving a fragile demo.