Diligence
Upload a diligence request list (DDQ) and Claude turns each item into a data product to track and answer — from your model where it can, from your team where it can’t.
{phase === 'drop' && (/* ============================================================ Diligence hub — a Project/Diligence template, created from a DDQ. PHASE 1: the checklist becomes a collection of EMPTY data products — one card per request, grouped by the workbook's sections. Each is a placeholder to be filled by a human, drafted by AI from the model, or marked N/A. Filling one is how information gets INTO the model. Content: window.DILIGENCE (tabs/diligence_content.js). ============================================================ */ /* Artifacts page — the SAME stacked-card framework as Finance/Contracts (CX_DASH: card → openDrawer → drawer). The only difference is the collection is grouped into the DDQ's sections. Content: window.DIL_DASH. */ function DiligenceDashboard() { const D = window.DIL_DASH || { sections: [], cardsBySection: {}, statHtml: '' }; const [sel, setSel] = React.useState((D.sections[0] && D.sections[0].key) || 'all'); const hostRef = React.useRef(null); // Boot the CX framework + register the pack once (records are global). React.useEffect(() => { if (window.ensureFinCxGlobal && window.ensureFinCxGlobal() && window.registerCxPack) { window.registerCxPack(D); } return () => { try { if (window.closeFull) window.closeFull(); } catch (e) {} try { if (window.closeDrawer) window.closeDrawer(); } catch (e) {} document.body.style.overflow = ''; }; }, []); // Re-render just the selected section's cards into the host on change. React.useEffect(() => { const host = hostRef.current; if (!host) return; host.innerHTML = '
Created from a Pre-LOI diligence request list (DDQ). Claude turned each of the {total || '85'} requests into a tracked data product, grouped by the checklist’s sections. Each one starts empty.
You resolve a request three ways — provide a document, let Claude draft it from the model, or mark it N/A. Where the answer already lives in the encoded org (Finance, Contracts…) it links straight to the source; where it doesn’t, the gap is your build list. Every answer is encoded into the model — so the room stays current and useful after the deal, not a pile of static files.
Upload a diligence request list (DDQ) and Claude turns each item into a data product to track and answer — from your model where it can, from your team where it can’t.
{phase === 'drop' && (