Tell me what you are trying to build, fix, govern, prove, or launch, and I will point you to the public Folium page that fits. It uses public routes only, so do not send private data here.
AI operating doctrine
Control the change before the change controls the business.
AI operating doctrine is the practical layer between a promising review build and a business dependency. It helps leaders see what must stay authoritative, what can be delegated, what must be demonstrated, and when the safest move is to pause.
Guide section
Precondition ladders name what must become true first
Before expanding an AI process, Folium defines the preconditions that need to turn green: source ownership, data custody, model behavior, review points, service health, rollback path, and operating owner.
- precondition ladders
- dependency root map
- review 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 record duties.
- service boundary contract
- AI service record contract
- mode and authority declaration
- owner and escalation map
Guide section
Rollback on truth drift, not only outages
A process 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 review
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 points
- 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
Evaluate agents, routes, and promotion paths
Before an open-source agent, model route, memory branch, prompt, or process behavior is adopted, Folium can test runtime class, local-model fit, repeatability, monitoring, fallback, held-out performance, and independent readback.
- open-source agent evaluation lab
- AI route and memory governance
- held-out AI promotion review
- 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 records, 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, support-guide state, launch checklists, record exports, and confirmed state-changing actions.
- AI operations cockpit
- dependency readiness board
- incident and support-guide inbox
- record 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
- record-status and dormant-system classification
- closure condition list
- operating responsibility map
Start here
Turn the guide into a first reviewable build.
The best next step is a narrow process, visible records, and a plan your team can explain.
- 01 Scope
- 02 Build
- 03 Prove
- 04 Operate