The Foundation

[F]orge — The Digital Asset Model

You cannot govern what you cannot see. Most critical infrastructure operators have asset data scattered across SCADA, EMS, historians, maintenance systems, financial databases, and compliance spreadsheets. None of them agree.

FORGE takes that scattered data and builds a clean digital asset model that the governance stack can read. No $10M platform. No 18-month deployment. Just clean data, handed off to ATLAS.

Forge builds. Tenet governs.

Methodology

Four phases. Clean handoff.

FORGE follows the same discipline as the Tenet governance stack. Every phase produces a defined output. The final output feeds directly into ATLAS Phase 1.

01

Source Discovery

Map every system that holds operational data. SCADA, EMS, historians, CMDB, maintenance, financial, compliance. Complete source inventory with format, frequency, and ownership.

02

Data Extraction

Pull governance-relevant data from each source. Asset identity, classification, operational metrics, maintenance history, financial position, regulatory status. Not all data — the right data.

03

Model Assembly

The core. Build a unified digital model for each physical asset. One record per asset. Conflicts resolved. Duplicates merged. Orphans flagged. Missing attributes documented.

04

Handoff

Clean digital asset model delivered to ATLAS. No manual data entry. No spreadsheet migration. Direct ingestion into the canonical register.

Conditional

FORGE deploys when the data is not ready.

Not every client needs FORGE. Clients with clean, unified operational data go straight to ATLAS. FORGE is the on-ramp for clients whose data is scattered — and in critical infrastructure, most is.

FORGE deploys when

Multiple departments maintain separate asset lists

No single source system produces a complete inventory

Naming conventions conflict across systems

ATLAS Phase 1 discovers fragmented source data

Regulatory deadline requires faster deployment than a platform build

FORGE is skipped when

Client has clean, unified operational data

Client runs Palantir Foundry or equivalent platform

Data complexity is within ATLAS Phase 1 scope

Single source system provides complete asset inventory

The Full Stack

From scattered data to governed portfolio.

Step 1 · Build

[F]orge

Builds digital asset model from raw operational data

Step 2 · Register

[A]tlas

Registers every asset in the canonical register

Step 3 · Model

[C]odex

Builds the governance model for each asset

Step 4 · Govern

[T]enet

Maps each asset to every applicable regulation

Step 5 · Engage

[A]nchor

Deploys through four stages

Step 6 · Optimize

[C]ompass

Quarterly reshape · 5-year trajectory

↑ Loop back · ATLAS updates · CODEX rescores ↑

Positioning

Not a platform. A purpose.

Palantir builds a $10M general-purpose operational data platform. FORGE builds a governance-ready digital asset model in weeks. Different purpose. Different timeline. Different economics.

If the client already runs Palantir, FORGE is unnecessary — ATLAS reads from Foundry directly. FORGE exists for the majority of operators who need governance before they need a platform.

No platform dependency. No vendor lock-in. FORGE builds the model and hands it off.

Forge builds. Tenet governs.

If your data is scattered and your regulatory deadline is not waiting, the conversation starts with Discovery.

Begin with Discovery →