← OloLand DDCONTENT HISTORY

Update to OloLand DD

Snapshot Nov 2, 2026 · 18:12 UTC · version 1.26.7

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save OloLand DD and check future changes in Following.

Up to 10 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Use when the OloLand deal target is a commercial real estate asset, portfolio, or operating company (CRE, multifamily, industrial RE, retail, office, hospitality, healthcare RE). Loads NOI / cap rate / DSCR / debt yield / rent-roll discipline and the verifier checklist for property-level diligence.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 448
    }
  ],
  "name": "ololand-dd-real-estate-diligence",
  "skill_md_contents": "---\nname: ololand-dd-real-estate-diligence\ndescription: Use when the OloLand deal target is a commercial real estate asset, portfolio,\n  or operating company (CRE, multifamily, industrial RE, retail, office, hospitality,\n  healthcare RE). Loads NOI / cap rate / DSCR / debt yield / rent-roll discipline\n  and the verifier checklist for property-level diligence.\n---\n\n# Real estate diligence\n\nCRE deals are valued off NOI and cap rate, not EBITDA and multiples. The KPI discipline, verifier checklist, and red flags differ from operating-company DD.\n\n## Canonical KPIs\n\n| KPI | Definition | Mistake to avoid |\n|---|---|---|\n| **NOI** | Effective gross revenue − operating expenses, **before** debt service, depreciation, capex | Including capex or debt service |\n| **Cap rate** | NOI ÷ Property value | Using trailing NOI when projections are stronger |\n| **DSCR** | NOI ÷ Annual debt service | Using EBITDA instead of NOI |\n| **Debt yield** | NOI ÷ Loan amount | Confused with cap rate |\n| **Occupancy** | Occupied units ÷ total OR occupied SF ÷ rentable SF | Mixing physical and economic |\n| **Economic occupancy** | Effective gross revenue ÷ gross potential rent | Reporting physical when economic is lower |\n| **T-12 NOI** | Trailing-12-month actual NOI from operating statements | Using underwriting NOI as \"trailing\" |\n\n## Verifier checklist\n\n- [ ] Rent roll × 12 reconciles to T-12 revenue\n- [ ] T-12 from GL or tax return, not sponsor pro-forma\n- [ ] OpEx normalized (taxes, insurance current quotes, mgmt fee 3-5% market not affiliated rate)\n- [ ] CapEx reserve included in underwriting NOI\n- [ ] Top-10 lease abstracts reviewed (term, escalations, options, exclusives, kick-out, co-tenancy)\n- [ ] WALT by SF and by revenue\n- [ ] Title commitment exceptions reviewed; survey + ALTA current\n- [ ] Phase I (and Phase II if recommended); PCA immediate repairs\n- [ ] Zoning compliance; tax history + appeal/reassessment exposure\n- [ ] Insurance loss runs 5-year; service contract cancellability at close\n\n## Debt + capital stack\n\nSenior loan terms (fixed/floating, IO, prepayment via yield maintenance / defeasance / open), mezz/pref equity intercreditor, refinance scenario at exit, DSCR + debt-yield headroom on 10% NOI drop.\n\n## Common red flags\n\n- Rent roll × 12 ≠ T-12 revenue → unstated concessions\n- \"Pro forma NOI\" used as cap-rate denominator\n- Replacement reserves excluded\n- Tenant concentration > 25% without IG credit\n- Mgmt fee 1-2% (affiliated subsidy) vs market 3-5%\n- Floating-rate bridge loan near cap with extension caveats\n\nEvery NOI cited MUST disclose basis (T-12 actual / T-3 annualized / underwriting) and cite source with `[N]`. Every cap rate MUST state the NOI basis.\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"
}

SHA-256 of public snapshot: eab2f3562cd1348a50745976b61f5bea05f1887e0058db03783dea51b08b07d3