Independent GPU technical due diligence

Selected illustrative report pages

These five representative outputs show how technical evidence can be organized for a lender or credit committee. The downloadable ten-page specimen adds test specifications, assumptions, evidence provenance, monitoring triggers, and reliance boundaries. All transaction details and results are illustrative.

Download the ten-page specimen PDF Scope a live transaction

Doku Assurance01

Executive technical opinion

Technical assumptions supportable subject to conditions

The financed technical assumptions are supportable if three material conditions are satisfied and evidenced before the applicable funding milestones.

C-01
Performance and orchestration acceptance
Complete and evidence the formal multi-node and orchestration acceptance suite at the contracted scale.
Open: preliminary results demonstrated; formal acceptance package pending.
C-02
Billable-capacity substantiation
Substantiate underwritten billable capacity through telemetry, allocation records, and contracted demand evidence.
Conditional: evidence incomplete.
C-03
Incident and SLA controls
Approve incident response, escalation, monitoring, and reporting controls.
In review: procedure submitted.

Technical opinion only. This is not a credit approval and does not replace lender judgment.

01 · Executive technical opinion

Doku Assurance02

Source-linked claim review

Claim-by-Claim Evidence Matrix

Each material claim mapped to a source reference, confidence level, materiality, lender-relevant conclusion, and financing condition.

Claims mappedSources linkedExceptions visible

ClaimSource referenceConfidenceMaterialityConclusionCondition

Cluster performanceE-014 benchmark logs; E-019 topologyHighMaterialPreliminary result demonstrated; formal acceptance evidence pendingC-01

Orchestration readinessE-024 scheduler logs; E-026 runbookMediumMaterial11 of 12 scenarios reproduced; one exception remainsC-01

Billable capacityE-031 telemetry; E-034 allocation; E-037 demandMediumCriticalUnderwritten capacity not fully substantiatedC-02

Incident and SLA controlsE-041 incident history; E-045 runbook; E-047 baselineMediumMaterialProcedure submitted; approval and exercise evidence pendingC-03

02 · Claim-by-claim evidence matrix

Doku Assurance03

Decision-gated verification

Acceptance Test Plan and Results

Tests tie financed claims to reproducible methods, thresholds, evidence, and funding conditions.

Illustrative outcomeCritical technical criteria demonstrated; three financing conditions remain subject to evidence and closure.

TestMethodThresholdObservedEvidenceStatus

Multi-node performanceThree representative runs after thermal stabilization>=95% contracted throughput; latency within tolerance97.2% throughput; latency within thresholdE-014, E-019, E-021Preliminary pass; C-01 open

Workload orchestrationQueue, placement, preemption, and autoscaling scenarios12 of 12 required scenarios; no unresolved Sev-1 or Sev-211 of 12 reproduced; autoscaling exception openE-024, E-026Conditional; C-01 open

Billable-capacity reconciliationTelemetry-to-allocation-to-demand reconciliation100% eligible capacity mapped within agreed tolerance86% mapped; source gaps remainE-031, E-034, E-037Conditional; C-02

Incident and SLA control exerciseAlert, escalation, and lender-notice tabletopAll material events routed within agreed response timesDraft procedure passed; owner approval pendingE-041, E-045, E-047In review; C-03

03 · Acceptance-test plan and results

Doku Assurance04

Credit translation

Funding Conditions, Holdbacks & Covenants

Material technical findings translated into specific protections, required evidence, and release criteria.

ConditionCredit protectionEvidence requiredStatus

C-01Holdback sized to cost-to-cure and performance-shortfall exposureSigned acceptance suite, telemetry, exception log, and closure noteOpen: formal package pending
C-02Subsequent draw limited to independently evidenced eligible capacityTelemetry, allocation records, and contracted demand evidenceConditional: evidence incomplete
C-03Covenant to maintain approved procedures and lender reportingApproved runbook, monitoring baseline, owners, and exercise recordIn review: procedure submitted

Illustrative terms only. Final credit structure and approval remain with the lender.

04 · Funding conditions, holdbacks, and covenants

Doku Assurance05

Conditions and continuing assurance

Closure Evidence & Optional Monitoring Schedule

Open conditions identify the evidence required for closure. Any post-close monitoring scope is optional and separately agreed.

Condition-closure register

IDRequired evidenceResponsibleDueStatus

C-01Signed acceptance package, raw telemetry, exception log, and Doku closure noteBorrower + DokuBefore initial drawOpen

C-02Capacity reconciliation tied to eligible contracted demandBorrower + lenderBefore subsequent drawConditional

C-03Approved runbook, owner roster, monitoring baseline, and tabletop recordBorrower operationsBefore service commencementIn review

Optional post-close monitoring schedule

Metric or controlEvidence sourceCadenceTriggerEscalation

Availability and SLA eventsMonitoring export + incident registerMonthly + breach noticeBelow agreed SLANotify lender; RCA and remediation plan

Billable-capacity reconciliationTelemetry + allocation + contracted demandMonthlyVariance above toleranceException log; model or draw review

Allocation and scheduler controlsScheduler configuration + scenario resultsQuarterly or material changeControl drift or failed scenarioRe-test and remediation

05 · Closure evidence and optional monitoring schedule

Need a decision-specific review?

Scope a live transaction