CRE Approval Gate
Purpose
Use when an action might be external, financial, sensitive, destructive, or client-facing and needs explicit approval.
Use when
- The user is working on a commercial real estate acquisition, underwriting, diligence, financing, legal/PSA, or IC memo workflow.
- The user needs a durable OpenClaw workpad rather than a one-off chat answer.
- The action should preserve assumptions, missing data, risks, approvals, and an audit log.
Operating rules
- Treat user-provided facts and extracted facts as candidates until reviewed.
- Mark unknown values as
unknown; do not guess financial or legal inputs.
- Write durable state under
state/cre-openclaw-agent/ when operating inside an OpenClaw workspace.
- Use workpads for visible reasoning, task state, risks, missing data, and logs.
- Require approval before external, financial, destructive, sensitive, or client-facing actions.
- Include disclaimers when drafting investment, legal, financing, or IC-facing material.
Approval-gated actions
Ask for explicit approval before:
- Sending emails, texts, LOIs, term sheets, diligence requests, or lender packages.
- Changing deal terms, recommendations, or approved assumptions.
- Sharing confidential deal materials externally.
- Deleting or overwriting state.
- Representing output as final professional advice.
CLI support
When the CLI is available, prefer verified local operations:
npx cre-openclaw-agent validate --workspace <workspace>
npx cre-openclaw-agent status --workspace <workspace>
npx cre-openclaw-agent sample --workspace <workspace>
Output standard
Return:
- Current workflow state
- Deal facts used and missing facts
- Risks or blockers
- Approval needed, if any
- Files created or updated
- Next recommended action
1---2name: cre-approval-gate3description: Use when an action might be external, financial, sensitive, destructive, or client-facing and needs explicit approval.4license: Apache-2.05---67# CRE Approval Gate89## Purpose1011Use when an action might be external, financial, sensitive, destructive, or client-facing and needs explicit approval.1213## Use when1415- The user is working on a commercial real estate acquisition, underwriting, diligence, financing, legal/PSA, or IC memo workflow.16- The user needs a durable OpenClaw workpad rather than a one-off chat answer.17- The action should preserve assumptions, missing data, risks, approvals, and an audit log.1819## Operating rules20211. Treat user-provided facts and extracted facts as candidates until reviewed.222. Mark unknown values as `unknown`; do not guess financial or legal inputs.233. Write durable state under `state/cre-openclaw-agent/` when operating inside an OpenClaw workspace.244. Use workpads for visible reasoning, task state, risks, missing data, and logs.255. Require approval before external, financial, destructive, sensitive, or client-facing actions.266. Include disclaimers when drafting investment, legal, financing, or IC-facing material.2728## Approval-gated actions2930Ask for explicit approval before:3132- Sending emails, texts, LOIs, term sheets, diligence requests, or lender packages.33- Changing deal terms, recommendations, or approved assumptions.34- Sharing confidential deal materials externally.35- Deleting or overwriting state.36- Representing output as final professional advice.3738## CLI support3940When the CLI is available, prefer verified local operations:4142```bash43npx cre-openclaw-agent validate --workspace <workspace>44npx cre-openclaw-agent status --workspace <workspace>45npx cre-openclaw-agent sample --workspace <workspace>46```4748## Output standard4950Return:5152- Current workflow state53- Deal facts used and missing facts54- Risks or blockers55- Approval needed, if any56- Files created or updated57- Next recommended action
ahacker-1