02 / Area of Work

Software Intelligence

In long-lived systems, the code is the only accurate specification of behavior. Changing it safely means recovering that specification first.

We build tools that help engineers understand what large software systems actually do, what must be preserved, and what can safely change.

Behavior recovery and modernization: PRISM

Technical approach

Static analysis at codebase scale
Behavior extraction and specification graphs
Evidence anchoring to file and line
Dependency and coupling analysis
Must-preserve contract detection
Transformation safety and review gates
AI-assisted reasoning over code
Code reduction and debloating research

Systems

Work in this area.

PRISM

Prototype

Legacy modernization fails when nobody can say what must not change.

PRISM generates a Behavior Specification Graph from a codebase: an explainable, navigable behavior map of entry points, core behavior, dependencies, outputs, and risk signals. Proposed modernization changes are behavior-preserving, gated by safety checks, and always subject to human approval.

Behavior Specification Graph
Legacy Modernization
Static Analysis
Safety Gates

Learn more

Working on a hard technical problem?

We work with government organizations, research institutions, and technology teams across cybersecurity, software, and autonomous systems.

Start a Conversation