✓RC → ✓HEV → ✓Propagation → ✓Compliance → ✓Deal → ✓Export → 7AI Ready

Enterprise Reconstruction · Module 7

Can this enterprise receive AI tomorrow?

AI deployment is not a technology decision. It is an architecture decision. The question is not whether the company wants AI — it is whether the enterprise is observable enough to receive it without breaking what already works.

Score 1 if the condition does not exist · 3 if partial or inconsistent · 5 if complete and consistent

Data observability — Can the enterprise see itself?

AI runs on data that already exists in the enterprise. If that data is fragmented, inconsistent, or lives in human heads — AI cannot reach it.

Operational objects carry their own state and history as they move through systems — no manual reporting required to reconstruct what happened.
Data from different functions is connected through shared objects — not synchronized through periodic exports or manual reconciliation.
When a decision is made in one domain, the outcome is visible in adjacent domains without manual escalation or reporting.
The enterprise can answer "what is the current state of X" in real time — without asking a person.

Process architecture — How much is compensation vs creation?

AI automates what the architecture already does — not what humans compensate for. Manual compensation work does not become AI-ready by adding a model on top.

High-volume, rule-bound decisions execute without human routing — humans intervene by exception only.
The architecture enforces sequence — later steps cannot begin until earlier conditions are met, automatically.
Process documentation exists in systems — not in the heads of three people who have been here for ten years.
When a process fails, the system detects it — it does not wait for a person to notice.

System integration — Can systems talk without humans translating?

Core systems (ERP, CRM, operational platforms) share data through APIs or integrated objects — not through file exports, email, or manual entry.
When a boundary is crossed between systems, the object carries its context — no re-entry of information is required.
A new system can be connected to the existing architecture without requiring a multi-year integration project.

Knowledge architecture — Where does the enterprise's intelligence live?

AI can only augment knowledge that exists in systems. Knowledge that lives in people evaporates when those people leave — and cannot be acquired by an AI model.

Decisions made in the past are retrievable from systems — not from people's memory or email archives.
When a critical employee leaves, the knowledge they carried can be reconstructed from system records — not lost.
The enterprise's operational intelligence is captured as structured data — not as institutional memory in long-tenured employees.

Enterprise parameters

Manual process headcount (FTEs doing compensation work) 20
Number of disconnected systems (no API) 8
% of decisions made by humans that could be rule-based 40%
Key person dependency (critical knowledge holders) 4
Enterprise value ($M) — for cost estimation $50M
Complete the assessment above and calculate

Unable to calculate. Please try again.