DOKU INFRASTRUCTURE
AI INFRASTRUCTURE TECHNICAL UNDERWRITING
ENGAGEMENT PROTOCOL

Version: 1.0
Date: July 24, 2026
Public, non-reliance planning aid

PURPOSE

This protocol explains how a prospective financing user can evaluate fit,
establish the engagement boundary, and authorize a bounded technical
underwriting scope. It is not a proposal, contract, assurance report, customer
reference, engineering opinion, rating, or investment recommendation.

1. FIRST CONTACT

Share high-level context only:

- Financing or asset type
- Approximate exposure
- Decision timing
- Intended workload
- The unresolved technical assumption that may change the credit decision

Do not send project files, CEII, privileged information, export-controlled
information, critical-infrastructure information, personal data, or other
restricted evidence.

2. FOUNDER FIT RESPONSE

Jorg Doku reviews the first request directly and targets a response within two
business days.

The response should state:

- Fit or no fit
- The financing decision Doku could support
- The smallest useful evidence request
- The responsible expert boundary
- Whether a paid rapid screen is a credible next step

A no-fit answer does not create a paid engagement.

3. PRE-EVIDENCE CONTROL LOCK

Before any restricted evidence is transferred, the parties should agree:

- Contracting party and authorized signatory
- Conflicts and participating organizations
- Scope, exclusions, fee, timing, and acceptance
- Permitted use, distribution, reliance, and liability
- Required insurance evidence
- Named specialists required by the accepted evidence scope
- Data classification and prohibited information
- Approved transfer channel and access list
- Retention, export, deletion, and revocation
- Permitted AI use, if any
- Incident and escalation contacts

If an item is unavailable, it remains explicitly open. It is not implied by
the website or by this protocol.

4. WRITTEN AUTHORIZATION

Paid work begins only after written authorization identifies:

- The single financing decision and accountable owner
- In-scope technical questions
- Evidence sources and source authority
- Buyer participation and technical contacts
- Deliverables and delivery timing
- Finding, action, owner, deadline, and closure-evidence convention
- Acceptance standard and factual-correction process
- Commercial and legal terms

There is no automatic expansion. Any deeper assessment or surveillance scope
requires a separate written decision.

5. DELIVERY AND DECISION RECORD

Every in-scope conclusion should:

- Cite the supporting evidence
- Preserve source authority, date, version, and provenance
- State confidence, assumptions, and missing evidence
- Explain the workload, commercial, and financial consequence
- Identify any proposed mitigant or credit action
- Name the accountable decision owner
- Define deadline and closure evidence where action is required
- State residual risk

Lender credit retains the financing decision. Responsible engineers, counsel,
and specialists retain authority for their source conclusions.

6. CURRENT PUBLIC PROOF BOUNDARY

Doku does not currently claim through this public protocol:

- A customer logo, testimonial, endorsement, or reference
- A completed transaction outcome
- A customer-approved redacted artifact
- A calibrated default model
- SOC 2, ISO 27001, or similar independent assurance
- A secure restricted-evidence channel unless the live intake explicitly says
  secure first-party delivery is available

Those states should be represented 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