ROI & insights report¶
cortexbuild report pulls together existing CortexBuild signals into a
single report and tracks your conformance score over time. It writes:
.cortexbuild/ROI_REPORT.md-- human-readable insights..cortexbuild/roi_report.json-- a machine-readable summary.
What it reports¶
| Signal | What it shows | If not available |
|---|---|---|
| Risk hotspots | The riskiest areas of the codebase from your last analysis | shown empty, with a note |
| Adaptive rules proposed | How many new rules have been proposed from recent activity | 0 |
| Context completeness | How complete your project's context profile is | 0 |
| Conformance score | Your current conformance score | 0 |
| Conformance trend | How your conformance score has changed over time | "no trend yet" |
Tracking your score over time¶
Record a snapshot whenever you like:
cortexbuild report --record-trend # append a snapshot
cortexbuild report --record-trend --commit $(git rev-parse --short HEAD)
History is stored locally, append-only, and tamper-evident -- if a snapshot is edited or removed after the fact, the report notices and says so rather than showing a trend line as if nothing happened. Only numeric metrics are stored; no file paths, secrets or personal data are ever included.
An empty history renders as "no trend yet"; two or more snapshots produce a trend versus the first recorded point.
Determinism¶
The report is fully offline and deterministic: running it twice against the same repository state produces the same result, and it never leaks a local file path, username, secret or personal data into the output. An unconfigured repository never crashes -- every signal simply degrades to a safe default and the report still renders with an explanatory note.