Control the change before the change controls the business.

Guide section

Precondition ladders name what must become true first

Before expanding an AI workflow, Folium defines the preconditions that need to turn green: source ownership, data custody, model behavior, review gates, service health, rollback path, and operating owner.

• precondition ladders
• dependency root map
• proof unlock order
• blocked-versus-ready status

Guide section

Give every service a boundary

Agents, dashboards, retrieval stores, model gateways, automations, and support tools need operating contracts. The contract names role, owner, version, upstream dependency, allowed actions, health, freshness, fallback, and evidence duties.

• service boundary contract
• AI service evidence contract
• mode and authority declaration
• owner and escalation map

Guide section

Rollback on truth drift, not only outages

A workflow can be technically online and still unsafe. Folium helps define rollback triggers for mismatched state, unclear provenance, hidden provider substitution, split ownership, stale sources, or a support layer acting outside its approved role.

• truth-drift rollback plan
• hard-stop criteria
• degraded-mode honesty
• repair and re-entry gate

Guide section

Make governance binding

Written policy is not enough when AI can route work, draft messages, summarize records, or recommend actions. Folium separates guardrails that only log from controls that block, route for approval, fail closed, or stop high-risk behavior.

• advisory-to-binding governance review
• approval and human-review gates
• fail-closed access checks
• live-action boundary plan

Guide section

Move work without drift

Modernization and private AI often mean moving pieces into new runtime lanes. Folium separates what must stay authoritative from what can be delegated, then stages migration through shadow, compare, canary, cutover, soak, and rollback.

• no-drift migration plan
• stay-or-move authority map
• storage and model road readiness
• active-versus-claimed operations reality map

Guide section

Certify agents, routes, and promotion paths

Before an open-source agent, model route, memory branch, prompt, or workflow behavior is adopted, Folium can test runtime class, local-model fit, repeatability, monitoring, fallback, held-out performance, and independent readback.

• open-source agent certification lab
• AI route and memory governance
• held-out AI promotion gate
• persisted verdict and promotion record

Guide section

Keep lifecycle records for every AI worker

A serious AI estate should know which models, agents, routes, databases, and automations are active, experimental, parked, retired, or replaced. Folium builds lifecycle records with owner, purpose, compatibility, training or evaluation evidence, promotion decision, rollback path, and deactivation notes.

• model owner grid
• model compatibility and serving matrix
• agent and model lifecycle ledger
• promotion, parking, and retirement notes

Guide section

Expose the operating cockpit

AI operations needs one review surface for incidents, logs, dependency readiness, runbook state, launch checklists, evidence exports, and confirm-gated state-changing actions.

• AI operations cockpit
• dependency readiness board
• incident and runbook inbox
• proof export path

Guide section

Protect recovery, exposure, and spend

Folium can review public and private service surfaces, admin paths, secrets custody, data recovery risk, scheduled retries, unattended agents, stop behavior, and budget controls before expansion.

• AI infrastructure exposure review
• data recovery triage and preservation plan
• AI spend safety guard
• pause, stop, and retry controls

Guide section

Keep a gap ledger

Serious AI work should make unfinished truth visible. A gap ledger separates open gaps, partial controls, blocked items, unverified capabilities, dormant pieces, closed items, and contradictions so leaders know what is real.

• gap and contradiction ledger
• evidence-status and dormant-system classification
• closure condition list
• operating responsibility map