Acquisition Diligence Control Tower

Can we run a reproducible acquisition-diligence control tower from reviewed deal package inputs, evidence coverage, missing-data gaps, data-room inventory, and red-team fact bundle. Compose existing CRUX tools only; preserve each upstream abstention or blocker, then return a non-persisted control-tower result for host-side review. Circulation requires a future custody-bound persistence path plus the metadata-required investment-committee approval? Trigger phrases: acquisition diligence control tower, acquisition diligence control tower. Produces: cited acquisition diligence control tower workpaper and decision flags.

Acquisition Underwriting · Underwriting · v1

Measured quality evidence

Quality lift unmeasured

Registry maturity does not prove response or artifact quality. No qualifying same-model skill-on versus no-skill improvement has been verified.

Required comparison: same model with this skill enabled versus the same model without the skill.

Inputs and output

Required inputs

Data Room Documents
Deal ID
Deal Packages
Diligence Dimensions
Diligence Evidence
Missing Data Gaps
Red Team Fact Bundle
Source Documents

Optional inputs

Deal Name
Human Review Status
Notable Risks
Workflow Status

Required source documents

Data Room Documents
Red Team Fact Bundle
Source Documents
Cim
Environmental Report
Model
Other
Reserve Report
Title Opinion

Expected outputs

A cited work product is selected at runtime.

Buyer-profile access

Policy visibility is not execution proof. Authentication is checked before a run.

Available

Read-only connection

The skill entry point is callable. Any downstream write or external action is checked separately.

Available

Partner workspace

The skill entry point is callable. Any downstream write or external action is checked separately.

External-action review

Review review applies before a consequential external or binding action. Analysis and working artifacts remain available before that review.

No specific external-action review item is declared.

Input gaps and limits

Dependent input gaps

No specific dependent input gap is declared.

Known limitations

Preview capability: useful but incomplete eval or SME coverage; human review required.
Do not use to run first-pass valuation screening (full-screening-pass) or to draft the IC memo itself (dataroom-to-ic-memo); it composes upstream outputs and never re-derives them. Orchestrator ladder — pick the rung by what you have in hand: full-screening-pass (fast go/no-go on a teaser or thin seller case) → comprehensive-deal-evaluation (a VDR is in hand) → deal-evaluation-autopilot (a thin, name- or entity/basin-only ask that must be auto-enriched first) → acquisition-diligence-control-tower (a receipt-backed diligence verdict packet). Use the rung that matches your inputs; do not substitute a neighbor.

Relationships

Outcome agents

acquisition-evaluator

Workflow-registry jobs

No workflow relationship is declared.

Use this skill

Authentication and the required buyer profile are checked before any work runs.