Update to OloLand DD

{
  "description": "Use before any OloLand deal artifact leaves the platform under the firm's name — IC memo, regulator export, RWI underwriter packet, LP-bound deal dossier, or any signed PDF that carries deterministic valuation numbers. Enforces an explicit partner approval step before the artifact is finalized.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 453
    }
  ],
  "name": "ololand-dd-partner-signoff",
  "skill_md_contents": "---\nname: ololand-dd-partner-signoff\ndescription: \"Use before any OloLand deal artifact leaves the platform under the firm's\\\n  \\ name \\u2014 IC memo, regulator export, RWI underwriter packet, LP-bound deal dossier,\\\n  \\ or any signed PDF that carries deterministic valuation numbers. Enforces an explicit\\\n  \\ partner approval step before the artifact is finalized.\"\n---\n\n# Partner sign-off gate\n\nA deal output that leaves OloLand with the firm's name attached is no longer an AI artifact — it is the firm's work product. Before any such artifact is finalized, the agent MUST surface a structured sign-off prompt and refuse to mark the artifact \"final\" until a human with partner-or-above role has approved.\n\nThis is the M&A analog of the legal-tech rule that \"agents do not operate without lawyer agreement.\" Translated to private equity, investment banking, and M&A advisory: **agents do not commit a number under the firm's letterhead without partner-or-above approval.**\n\n## When this skill applies\n\nTrigger the sign-off gate when the user requests, or the agent is about to produce, any of:\n\n- An IC memo intended for committee distribution\n- A regulator export via `request_regulator_export` / `get_regulator_export`\n- An RWI (representations & warranties insurance) underwriter packet\n- A final deal dossier intended for LPs, lenders, or insurance counterparties\n- A signed PDF that includes a deterministic valuation number (DCF, LBO IRR, MOIC, accretion/dilution figure) under the firm's name\n- A merger-readiness sign-off (`get_merger_readiness` → committed export)\n\nSkip the gate for in-platform exploratory artifacts: draft memos still being edited, scratch valuations, internal-only risk reviews, and anything labeled \"draft\" or \"preview\".\n\n## The sign-off contract\n\nBefore finalizing, emit a structured sign-off prompt with four elements:\n\n1. **Artifact summary** — one sentence describing what is about to be finalized\n2. **Load-bearing numbers** — every dollar figure, multiple, IRR, MOIC, or ratio that appears in the artifact, each with its `[N]` citation\n3. **Open items** — any reconciliation gap, missing source, estimated input, or unverified assumption (cite from `check_citation_coverage` and `reconcile_documents` if available)\n4. **Partner ask** — an explicit request: \"Partner approval required before this artifact is committed. Reply APPROVE, REJECT, or REQUEST CHANGES.\"\n\n## Discipline\n\n- **Do not auto-approve.** Synthesized acknowledgments (\"ok looks good\", \"fine\") are not sign-off — the user must type the approval token explicitly.\n- **Do not silently downgrade severity.** If the artifact carries a Beneish or JE finding at severity ≥ 7, the sign-off prompt MUST name it.\n- **Do not finalize on partial reconciliation.** If `check_citation_coverage` reports any claim without a source, OR if `reconcile_documents` flags an unresolved cross-document conflict, the sign-off prompt MUST list each open item before asking for approval.\n- **Re-prompt on material change.** A previously-approved artifact whose numbers, sections, or assumptions changed needs a new sign-off.\n\n\n## OpenAI execution requirements\n\nUse the connected MCP server's current tool schemas. Do not invent tool arguments, job-status endpoints, inputs, or outputs. If a referenced tool is unavailable, explain the limitation and request the needed connection or data. Invoke writes only when the user has requested the corresponding action. Do not initiate purchases or payments. An unrun, unsupported, or unavailable procedure is a gap, never a passing result.\n\n\nOpenAI cannot execute local lifecycle hooks. Use the packaged explicit setup/review workflow when requested. Server-side MCP auditing remains authoritative; preserve evidence blockers and human-only approval gates.\n\nClaim-correction submission is unsupported in this OpenAI upload because the current handler records surface=cowork. Do not invoke submit_agent_claim_correction from OpenAI. Explain the limitation and retain proposed correction text for human review without claiming submission. See unsupported-workflows.json for the excluded canonical workflow.\n"
}