ForTriage is designed with clear data boundaries. Most of the dashboard — Overview, Drill-down, Executive Summary, and Report Explorer — operates entirely offline and never communicates with any external service. Only AI Insights and the follow-up chat send data externally, and what they send is strictly limited to aggregated metrics — never your Fortran source code.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/acdeveloper-sci/fortriage/llms.txt
Use this file to discover all available pages before exploring further.
What stays local (always)
The following data never leaves your machine under any circumstances:- Your Fortran source code is never sent to any external service — not to Google, not anywhere. ForTriage uploads source files to a temporary local directory, runs the Forti4D analysis pipeline locally, then discards them.
- There is no database and no persistent storage. Nothing is saved between sessions; each analysis run is fully isolated.
- Uploaded files exist only in memory during the active session. Closing or refreshing the browser tab immediately clears all session data.
- The Overview, Drill-down, Executive Summary, and Report Explorer tabs are entirely offline. They make no external network calls regardless of whether an API key is configured.
What AI Insights sends to Google
When you run an analysis and AI Insights is configured, ForTriage builds a pre-aggregated context snapshot and sends it to Google’s Gemini API. The snapshot contains only computed metrics — never source code lines. Sent for the initial insights generation (1 request per analysis run):- KPIs: total units analyzed, dead code unit count, critical risk unit count, average legacy percentage, direct migration candidate count
- Unique source file count
- Tier distribution counts (CRITICAL / HIGH / MEDIUM / LOW / DEAD_CODE)
- Up to 5 “core knot” units — unit name, file name, CC value, Fan_In value (units with CC ≥ 11 and Fan_In ≥ 5, ranked by CC × Fan_In)
- Up to 3 common coupling risk entries — block name, N_Units, N_Files, risk level (ranked by risk severity then unit count)
- Clone concentration summary — total duplicate pairs and status distribution counts
- Migration strategy distribution across all units
- Everything above, plus the top 15 highest-scoring units with their CC, Fan_In, Fan_Out, LOC, implicit-none, and equivalence metrics
- The complete Forti4D executive summary text
- The AI Insights overview, key risks, and recommended actions already displayed on screen
| What stays local | What is sent to Google |
|---|---|
| All Fortran source code | Unit names and file names |
| Raw CSVs and DataFrames | Aggregated metric counts and scores |
| Uploaded zip archives | Tier and strategy distribution counts |
| Analysis pipeline logs | Top-N risk unit metric snapshots |
| Report Explorer file content | Executive summary text (chat only) |
| Session state after tab close | AI Insights summary text (chat only) |
GEMINI_API_KEY, or review the data handling terms linked above before proceeding.
Running without AI Insights
Disabling AI Insights requires no configuration change — simply do not provide aGEMINI_API_KEY:
- The full dashboard, including all analysis views, works with no network access whatsoever
- If a key is absent or the secrets file does not exist, AI Insights will show a generic error message (not a crash) — no other part of the app is affected
- All risk prioritization, drill-down analysis, executive summaries, and report exploration run entirely on your local machine using the Forti4D pipeline
Ephemeral sessions
ForTriage has no database, no persistent storage, and no user accounts. The application is entirely stateless between sessions:- Uploaded files exist only in memory for the duration of the analysis
- Closing or refreshing the browser tab clears all session data, including analysis results and chat history
- No analysis results, metrics, or conversation content are written to disk by ForTriage itself