DOKU INFRASTRUCTURE
AI INFRASTRUCTURE TECHNICAL UNDERWRITING
METHOD CHANGE LOG

Current version: 1.2
Review owner: Jorg Doku, Founder, Doku Infrastructure
Current review date: July 24, 2026
Planned review cadence: Quarterly and before proposal-controlled reliance

PURPOSE

This public log records material changes to Doku's AI infrastructure technical
underwriting method. It is a transparency artifact, not customer evidence, an
assurance report, a rating methodology, or a representation of predictive
performance.

VERSION 1.2
Date: July 24, 2026

- Added three irreversible decision gates covering credit approval, funding or
  draw, and operating surveillance.
- Added a four-stage engagement sequence from high-level first contact through
  written authorization.
- Published a standalone engagement protocol for financing, procurement,
  security, legal, and technical reviewers.
- Clarified the local prepared-email state, founder response window, no-fit
  outcome, and pre-evidence control boundary.
- Added structured engagement steps and the protocol artifact to the public
  page metadata.

The underlying useful-compute-to-debt-protection model and public proof
boundary did not change.

VERSION 1.1
Date: July 24, 2026

- Added role-specific review paths for infrastructure credit, technical risk,
  equipment finance, and structured or portfolio credit.
- Added a public engagement-readiness register that separates what can be
  reviewed now, what must be agreed before restricted evidence, and what Doku
  does not claim.
- Added a bounded rapid-screen buyer packet with scope, participation,
  acceptance, procurement, reliance, and specialist guardrails.
- Added an illustrative lender decision record and technical underwriting
  procurement checklist.
- Expanded direct-link, keyboard, mobile, accessibility, and no-JavaScript
  release tests.

VERSION 1.0
Date: July 24, 2026

- Published the useful-compute-to-debt-protection underwriting chain.
- Defined eight capacity states from installed equipment through cash available
  for debt service.
- Established cross-layer review of power, facility, workload, topology,
  storage, operating software, team, control, and redeployability.
- Established evidence authority, provenance, confidence, owner, closure, and
  residual-risk conventions.
- Published the initial 96-source register and public claim boundaries.

CHANGE CONTROL

At each review, the owner should record:

- Sources added, changed, or retired
- Method steps added, changed, or retired
- Changes to evidence authority or claim boundaries
- Changes to product scope, acceptance, or reliance
- Material feedback from responsible specialists or financing users
- Whether the change affects current public artifacts or proposal language

CURRENT EVIDENCE BOUNDARY

The method has not been represented as calibrated against a complete default
dataset, independently validated, or proven through a public completed customer
transaction. Those states must be documented only when verifiable evidence
exists and permission allows disclosure.

CONTACT

Jorg Doku
Founder, Doku Infrastructure
jorg@dokuinfra.com
https://www.dokuinfra.com/ai-infrastructure-technical-risk
https://calendly.com/jorg-dokuinfra/30min