# CLAUDE — 2631 Solutions Plus Field of Play Hornsby

> Per-job AI context. Inherits from `_System/CLAUDE.md` + `11_OpsMan_LFCS/_Brain/CLAUDE.md`. v5 orientation layer added 2026-05-06.

## Quick Links

| What | Where |
|---|---|
| Job overview / brief | `00-brief.md` (TBC — pending intake) |
| Drawings | `03 - Plans and Specifications/03a - Issued for Construction/2631_*` |
| BOQ | `02 - Scope and Pricing/02b - BOQ and Rate Schedules/` (TBC) |
| RFQ email | `06 - Correspondence/06a - Emails/` (TBC) |
| Earlier zips (Apr 28/29 — same project? different round?) | Rocky's `Downloads/Solutions Field of Play Hornsby-*` |

## Status

**Stage:** Intake · **Bid due:** TBC · **Active Bid:** None yet
**Source files:** Drawings filed (renamed to `2631_*` convention 2026-05-05). BOQ + RFQ pending.

## What I Know

- Client: Solutions Plus (head contractor — confirm with Rocky)
- End client: Hornsby Council TBC
- Site: Field of Play Hornsby
- Provisional scope: pavement / concrete paving finishes per HPE-TEN-CI-OMV FTL pack and earlier LFCS quotes (19-3-26)
- **Cross-reference (mate's vault):** Hasibul's `01 - Jobs/01-2275 Solutions Field of Play Hornsby/_Job Overview` — subcontract S01-2275-011 already SIGNED with Solutions Plus Built Pty Ltd at $95,000 ex-GST. Site starts 18 May 2026, PC01 due 25 May 2026, 5% retention, $500/day LD. **Confirm with Rocky whether 2631 is a NEW bid round / different sub-package OR the same scope as 01-2275** (the "earlier zips" notes from Apr 28/29 suggest different rounds).

## Documents Completed

- [x] Job folder scaffolded (11-section per `folder-spec`)
- [x] Drawings filed in `03a` and renamed to `2631_*` convention (2026-05-05)

## What's Pending

- [ ] **Confirm with Rocky:** is 2631 the same scope as Hasibul's signed 01-2275 (S01-2275-011), or a separate bid? ⚠
- [ ] Confirm Solutions Plus = head contractor (or is HPE the head?)
- [ ] Confirm bid due date
- [ ] Source files completion: BOQ + RFQ email
- [ ] Run `lfcs-drawing-extract-text` against drawings in 03a
- [ ] Run `lfcs-spec-summarise` on spec/TDS sheets in pack
- [ ] Once scope confirmed: `lfcs-bid-prep-doc` + `lfcs-incl-excl-draft`

## Site Team

LFCS leads on this job (post-award). Hasibul's 01-2275 memory lists Steve / Donal / Ertugrul / Joel / James / Mahdi / Amaan as the FRP team for the Hornsby site — likely overlap.

## Job snapshot
- **Job number:** 2631
- **Client:** Solutions Plus (head contractor — confirm with Rocky)
- **Site:** Field of Play Hornsby (Hornsby Council end-client TBC)
- **Status:** intake — drawings filed, scope confirmation pending
- **Bid due:** TBC
- **Vault path:** `Operations/Jobs/Upcoming/2631 - Solutions Plus - Field of Play Hornsby/`

## Scope (provisional)
Pavement / concrete paving finishes work per HPE-TEN-CI-OMV FTL pack and earlier LFCS quotes (19-3-26). Confirm with Rocky.

## Drawings filed in 03a (2026-05-05)
Renamed to `2631_*` convention — see `03 - Plans and Specifications/03a - Issued for Construction/`.

## Patterns
- `[[lfcs-standards/pricing-checklist]]` — cross-cutting, applies to all jobs
- `[[lfcs-standards/concepts/Defensible-for-variations-posture]]` — private commercial / field-of-play work, decision tree applies

## Skill routing
- Drawings already in 03a → run `lfcs-drawing-extract-text` next
- Spec/TDS sheets in pack → `lfcs-spec-summarise`
- Once scope confirmed → `lfcs-bid-prep-doc` + `lfcs-incl-excl-draft`

## Open items
- Confirm Solutions Plus = head contractor (or is HPE the head?)
- Confirm bid due date
- Earlier zips `Solutions Field of Play Hornsby-...` from Apr 28/29 still sitting in Downloads — same project, file in here too? Different bid round?
- Scope boundary: pavement-only vs wider concrete works