FinOps Engine Thinking Flow

Create machine-readable source material while preserving document, page, row, and visual context for later evidence checking.

Run deterministic and model-assisted safety review across the source registry, then redact or block unsafe material before deeper analysis.

Keep selected visual pages or screenshots alongside extracted text so architecture diagrams, dashboards, and tables are not lost.

Use uploaded sources to establish current-state claims. Use criteria, anti-patterns, tactics, taxonomies, and reference documents only as controlled analytical context.

Build a source registry that persists the location and type of each evidence unit before domain reasoning begins.

Use deterministic domain signals to rank chunks and reduce irrelevant context before model interpretation.

Prioritize high and medium relevance, retain gap and contradiction signals, and stop near the packet target before context becomes noisy.

Use stronger or more independent model profiles where the task is consequential, and preserve ordered provider fallbacks rather than allowing free model choice.

Verify the quote, surrounding context, packet coverage, and score calibration independently from the forensic auditor.

Give negative findings their own semantics so a zero score cannot automatically become a positive maturity signal.

Feed the disputed criterion IDs and verifier feedback into a targeted audit task, then run the evidence check again.

Replace unsupported or over-scored counts, preserve adjustment reasons and rescan status, and merge all domain verification results.

Normalize 30 maturity and 30 anti-pattern scores, subtract 50% of burden, add a small clearance bonus only when anti-pattern coverage is sufficient, and apply evidence caps.

Below the evidence floor, classification is “Insufficient evidence.” Otherwise, readiness bands separate Crawl, Walk, Walk with significant friction, and Run.

Below 30% density, readiness is capped by available evidence and the Quality Gate blocks action. Between 30% and 60%, readiness remains capped until stronger evidence is supplied.

HIGH requires at least 70% evidence density, 95% delivery integrity, and no more than 10 silent maturity areas. LOW is triggered below 30% density, below 70% integrity, or above 18 silent areas. Everything between is MEDIUM.

Build a factual assessment layer before causal interpretation or planning language is introduced.

Connect verified patterns across domains without changing the locked score or inventing organization facts.

Translate the same factual diagnosis into FinOps terminology and operational priorities without changing the facts.

Use business and financial language while preserving the same evidence boundaries and avoiding unsupported ROI claims.

HIGH can produce directive phases and tactics. MEDIUM produces cautious phases with confidence and assumptions. LOW produces evidence-backed findings, candidate themes, missing evidence, and a validation plan—without a directive roadmap.

Separate diagnosis from prognosis: a valid diagnosis can coexist with a NO_GO planning decision when the evidence is not strong enough for implementation.

Place the complete tactic-ID lookup ahead of strategy generation, scan the resulting JSON for invalid IDs, and regenerate when the model invents, abbreviates, or modifies an identifier.

Compare action language and cited tactic rules against the locked finding corpus; replace a mismatched tactic or remove the unsupported action.

Check evidence summary and diagnosis separately from planning decisions and roadmap actions, then run bounded regeneration and a stronger retry when blockers survive.

Operate on exact claims and source locations. Rewrite known metric misuse, remove unsafe roadmap actions, and quarantine unsupported fragments that can be located in the generated structure.

Block below the evidence floor or when material unsupported claims survive. Warn for partial evidence, weak anti-pattern coverage, many silent areas, sanitation, or incomplete fact-checking. Otherwise issue GO.

Persist stage traces, model usage, warnings, packet status, evidence adjustments, and report diagnostics. Use synthetic Crawl, Walk, and Run fixtures as an MVP drift procedure.