A long-lived application is often treated as a technical object: programs, interfaces, files, jobs and dependencies. Those views matter. Yet they do not explain the policies, decisions, obligations and vocabulary the software enforces.

That distinction becomes urgent when documentation is incomplete, experienced people are leaving or a major decision depends on behavior no one can explain with confidence.

A map is not meaning.

Technical analysis can show that one program calls another or that a data element moves across several components. A business participant needs a different answer: what does the field mean, which business rule uses it, what event triggers the behavior and which process depends on the result?

When these questions are answered separately in spreadsheets, interviews and diagrams, connections decay. The value comes from keeping the business statement attached to the technical evidence that supports it.

Your business is not your code. Its policies and decisions have been encoded there.

One repository, several ways to examine it.

Discovery 1.0 recovers a connected set of business rules, terms, events, processes, data relationships and program relationships. The views are not independent reports. They are different ways to examine the same evidence-backed model.

A business analyst can read a rule in natural language. A subject-matter expert can verify terminology. A technologist can follow the finding back to the relevant program and data. A decision-maker can examine the implications without first learning to read COBOL.

Why the connection matters

Natural language without source can become opinion. Source without business meaning remains inaccessible. The useful asset is the connection between them.

A durable asset for later decisions.

The immediate use may be an audit, retirement risk, consolidation or delivery plan. The recovered model also prepares the organization for future work. It gives later modernization teams a shared starting point and gives AI agents governed context instead of asking them to infer the business from raw code.

Discovery 1.0 is read-only. Its purpose is to make what exists visible and reviewable. The broader Workbench is designed to preserve validated knowledge as people later add, modify or retire business intent.