Skip to content
Platform

Capture what the system does, not what someone remembers.

Most legacy-modernisation tools read code. The Filix approach — patent-pending — observes the system as it runs, learns from what it sees, and produces formal specifications and linked tests that reflect what the system actually does. The result is documentation that matches behaviour, because it was derived from behaviour.

What it produces

Specifications with provenance you can trust.

From behaviour, not just source

Execution-trace specification capture

production
The platform observes the system as it runs and derives a specification from what it actually does — grounding rules in real execution rather than in a reading of the code alone.
Read more
Portable evidence

Product & rule mining → ACORD TXLife

production
Product configuration and business rules are mined and projected into ACORD TXLife 2.30 at ≥95% round-trip fidelity — a portable, industry-standard evidence pack rather than a private format.
Read more
Impact analysis

Field-level lineage

production
Answer “what breaks if this field changes?” with field-level lineage, carrying Exact confidence on dependencies gated by IF and EVALUATE logic — not a guess dressed up as an answer.
Read more
Why it holds up

Confidence, stated honestly.

A specification is only useful if you can tell how much to trust each line of it. The platform tags dependencies with their confidence — marking as Exactthe ones it can prove from IF/EVALUATE-gated logic — and links every rule back to the execution that produced it. That is the difference between a document you can act on and a document you have to re-verify by hand.

See it on your code

Capture a specification from one of your programs.

Bring a program whose behaviour has outlived its documentation. We will capture a specification from how it actually runs.

Book a technical walkthroughRead the white paper