The engine underneath the diagnosis.
Most software in this category is a dashboard with alerts bolted on. Helcyon was built the other way around: an engine first, held to the standard a diagnosis deserves, with the delivery kept deliberately simple. This page is for the reader who wants to know what that standard is: the owner who takes their money seriously, the accountant putting their name on a brief, the lender evaluating the framework.
Five disciplines govern everything the engine produces. Each has its own page.
It knows what every transaction is.
Before any diagnosis begins, every transaction is resolved into a canonical model of the economic event it represents, not the category a bookkeeper filed it under. The engine reasons about your business, not your chart of accounts. That is why a margin slip traces to a specific vendor and a specific product, not to a category total.
Financial Ontology →It proves the books balance before it reads them.
Helcyon rebuilds your books inside its own double-entry model and verifies that every dollar is matched by the obligation that created it. If the books do not reconcile inside the engine, it says so instead of proceeding. A diagnosis built on unbalanced books is the wrong medicine.
Obligation Integrity →Debits
Credits
It separates what the business produced from what it merely held.
The books report a net number. They do not tell you how much of it your recurring operations actually produced, or how much was temporary, one-off, or a discretionary use of that production. Helcyon measures production first, then separates every use, so the figure reflects the engine of the business rather than the noise around it.
Cash Production Capacity →It grades its own evidence.
Every finding carries a grade for the strength of the evidence behind it, with the transaction-level records attached. When the data cannot support a conclusion, the engine reports "not yet assessable." It never fills a gap with a guess, and no number renders unless it survives a trace back to the transactions that produced it.
Evidence Grades →It was tested before it ever read your business.
The rule set was built by operators, pressure-tested by working CFOs, and tested across hundreds of businesses in 20 industries, including holdout businesses the engine never sees during calibration. No rule ships on its author's word alone.
Validation →The method is published.
None of this is a black box. The methodology behind the engine is documented in working papers on SSRN and in the Helcyon methodology brief.