Nobody Knows Why the Legacy System Works This Way.

SCN-034Institutional capacity & sovereignty

Nobody Knows Why the Legacy System Works This Way.

A system can remain operational long after the decisions, people and documentation that made it understandable are gone.

ScaleNational
UrgencyHigh
Coordination gapHigh
StakesEssential service · Security · Money
Knowledge AttritionLegacy DependencyContext lossSingle Point Of Failure
What Koali changes

Koali links technical components to decisions, incidents, policy rules, known exceptions and knowledge holders. Modernization teams can reconstruct why before removing what merely looks unnecessary.

← Back to the full Mosaic
What breaksKnowledge Attrition · Legacy Dependency · Context loss · Single Point Of Failure
Who holds part of the picture

frontline practitioners • domain experts • decision-makers

Koali response

Koali links technical components to decisions, incidents, policy rules, known exceptions and knowledge holders. Modernization teams can reconstruct why before removing what merely looks unnecessary.

Real-world parallels
  • Critical federal legacy systems — U.S. GAO
  • Phoenix pay system — Auditor General of Canada
What success looks like

The relevant state remains visible across handoffs and time. • Responsibilities, unresolved questions and escalation paths are explicit.

Documented parallels show that the failure mechanism is real; they do not claim Koali would have changed a specific outcome.

Nobody Knows Why the Legacy System Works This Way.

A system can remain operational long after the decisions, people and documentation that made it understandable are gone.

The problem

A decades-old system contains patches, exceptions and hidden dependencies. Documentation says what modules do, but not why a rule exists or which historical failure created it. Staff become afraid to change anything.

What breaks

  • Knowledge Attrition
  • Legacy Dependency
  • Context Loss
  • Single Point Of Failure

Who holds part of the picture

  • frontline practitioners
  • domain experts
  • decision-makers
  • affected people

With Koali

Koali links technical components to decisions, incidents, policy rules, known exceptions and knowledge holders. Modernization teams can reconstruct why before removing what merely looks unnecessary.

Human authority

Authorized humans and institutions retain their existing legal, professional and democratic authority. Koali structures knowledge, coordination and traceability; it does not take sovereign or professional decisions.

What success looks like

  • The relevant state remains visible across handoffs and time.
  • Responsibilities, unresolved questions and escalation paths are explicit.
  • The outcome produces reusable memory for the next comparable case.

Real-world parallels

U.S. GAO — Critical Legacy Systems

GAO identified critical federal legacy systems 8 to 51 years old, including outdated languages, unsupported technology and known vulnerabilities.

Relation to scenario: DIRECT
Source: https://www.gao.gov/products/gao-19-471

Auditor General of Canada — Phoenix example

The Auditor General reiterated that Phoenix executives prioritized schedule and budget over critical elements and did not provide senior officials a complete picture of project risks.

Relation to scenario: STRONG ANALOGUE
Source: https://www.oag-bvg.gc.ca/internet/docs/parl_oag_202310_07_e.pdf

Boundary

The documented cases illustrate analogous failure mechanisms. They do not establish that Koali would have prevented the event or guaranteed a different outcome.

Koali loop

signals → shared meaning → evidence → choice → responsibility → action → verification → memory → better knowledge