---
name: lfcs-pre-pour-check
description: Walk Rocky through the 8-item pre-pour checklist for LFCS concrete pours. Logs result to the inspection register.
version: 0.1.0
metadata:
  hermes:
    tags: [lfcs, construction, pour, safety, inspection]
    category: domain
    requires_toolsets: [terminal]
    config:
      - key: lfcs.jobs_root
        description: Root directory holding active LFCS job folders.
        default: "/home/ccuser/opsman-work/Jobs/Ongoing Jobs"
---

# LFCS Pre-Pour Check

## When to use

Rocky says any of: "pre-pour check", "ready to pour", "pour today", "checking the pour", or invokes `/lfcs-pre-pour-check [zone]`.

## Procedure

1. Identify the active job. Default: the only folder in `lfcs.jobs_root` (or scan `Jobs/Upcoming/` if Ongoing is empty). Ask Rocky if there are multiple.
2. Read the inspection log: `<job>/07 - Site Documents/07c - Inspection Records/_inspection-log.md`
3. Walk through these 8 checks ONE AT A TIME. For each, ask Rocky a yes/no question. Wait for his answer before moving on.

   1. Formwork inspected — edge support, thickened edges, expansion joints?
   2. Reo placed, cover verified, chairs in place?
   3. Levels checked with laser?
   4. Mix design confirmed in writing for THIS pour?
   5. Pump confirmed for this morning?
   6. Solutions Plus rep on site to sign off?
   7. Pre-pour photo taken?
   8. Will the pre-pour be logged today (this register)?

4. If ALL 8 = yes → reply: "✅ Pre-pour check passed. Logged. POUR APPROVED." Then append a row to `_inspection-log.md` with type=pre-pour, today's date, zone (asked or inferred), inspector=Rocky, outcome=approved.

5. If ANY = no → reply: "🛑 STOP — pour blocked. [List of unchecked items]. Resolve before proceeding." Do NOT log the inspection until all green. Capture the blockers in the daily diary.

## Output format

Two-line replies preferred. Lead with ✅ or 🛑. Examples:
- "✅ Pre-pour check passed Zone 1. Logged in 07c. Pour approved."
- "🛑 STOP — items 4 (mix design) and 6 (SP rep) not confirmed. Pour BLOCKED. Resolve before mobilising pump."

## Pitfalls

- If Rocky says "skip the checks, just pour" — REFUSE. Reply: "Pre-pour log is contractual evidence. If pour proceeds without it and the panel fails, no defence. Run the check or accept the contractual risk in writing."
- If the active job has `type: dayworks` (rare for pour days) — same checklist still applies, plus check the dayworks docket has client signatory confirmed.

## Verification

After replying:
1. On the green path, re-read the last row of `_inspection-log.md` and confirm date, zone, inspector=Rocky, outcome=approved are all present. If any field missing, do NOT confirm "POUR APPROVED" — flag the log write failure.
2. On the blocked path, confirm a diary entry was created in `<job>/07 - Site Documents/07d - Daily Diary/YYYY-MM-DD.md` capturing the blockers.
3. Never send "POUR APPROVED" without a successful append to the inspection log — the log IS the contractual evidence.