leedab 0.5.3 → 0.6.1

package/context/use-cases/construction.md

@@ -0,0 +1,97 @@
+---
+created: 2026-05-03
+updated: 2026-05-03
+type: wiki
+topic: customer-use-cases
+industry: trades
+maturity: stub
+tags: [wiki, customer-use-case, trades, construction, building, plumbing, electrical, roofing]
+---
+
+# Trades / construction — customer use cases
+
+> Residential builders, plumbers, electricians, roofers, tilers, tradies. Coastal Built (residential builder) + Hawkesbury Roofing are demo prospects. Pillarix-adjacent for partnership conversations — relevant when LeedAB talks to vertical AI players in this space.
+
+## Common shape — trades SMB
+
+- **Director-led** — a licensed builder / electrician / etc. + 1-3 site supervisors + a roster of regular subbies (5-15)
+- **Bookings come from referrals + Google + neighbour-word-of-mouth** — almost never paid acquisition
+- **Quoting is bottlenecked on the director** — every quote requires their touch; that's the daily-operations chokepoint
+- **Job sites are mobile** — director drives between 2-5 active jobs/day; admin time is in the ute, in evenings, in the kitchen at 22:00
+- **Subbies are paid per-job, not salaried** — relationship management matters more than HR processes
+- **Materials delivery is a daily fire** — stockouts at site, suppliers running late, swap-in substitutions on engineered specs
+- **Compliance burden** — NSW Home Building Compensation Fund (HBCF), engineer sign-offs, council inspections, electrical certs, plumbing certs, asbestos protocols
+- **Cashflow is brutal** — progress payments lag job spend; one bad month wipes the year
+
+## Where LeedAB helps
+
+| Pain | Agent | Action |
+|---|---|---|
+| Quote backlog | Sales + Ops | Pre-fill quote templates from job notes, route to director for approval, send via email |
+| Subbie coordination | Ops + People | Maintain WhatsApp groups, coordinate site visits, track availability |
+| Material orders | Procurement + Ops | Standing supplier accounts, exception flags ("Bunnings out of 90×35 — substitute approved?") |
+| Site reports | Ops + CX | Daily 10-line site report from photos + voice memos, share with client |
+| Council / engineer sign-offs | Compliance + Legal | Track inspection schedule, flag overdue, draft RFIs |
+| Variations / change-orders | Sales + Legal + Finance | Formalise verbal "yeah she'll be right" into written variation + revised quote |
+| Progress invoicing | Finance | Auto-draft progress claims at milestones, send to client + bookkeeper |
+| Customer comms | CX + Concierge | "Is the demo still on Tuesday?" — proactive client updates, photos, ETAs |
+| Compliance evidence | Compliance | Maintain folder of cert pics, sign-offs, inspection records (audit-ready) |
+| Wet-weather / delay impact | Ops + CX | When a slip is happening, surface to client BEFORE it becomes a missed PCD |
+
+## Likely licensed agent subset
+
+For most trades / construction SMBs:
+- **Always:** coo, concierge, sales, ops, procurement, finance, cx, compliance
+- **Optional:** people (when they have admin staff or apprentices), marketing (when they want pipeline beyond word-of-mouth), legal (variations / disputes)
+- **Drop:** engineering / build / devops, content / brand / video, automation, investor, research
+- **Tier:** typically tier-less; per-customer manifest carries customisation
+
+## Industry-specific knowledge to bake in
+
+### Tone
+- **Plain, direct, blue-collar professional.** No corporate fluff. "Done" beats "executed."
+- **Subbie-first.** Comms via WhatsApp groups, not email. Voice notes acceptable.
+- **Time-zoned to AEST/AEDT.** "Tomorrow" means tomorrow on this coast.
+- **Money in writing.** Variations get formal change-orders. Verbal "she'll be right" never holds in a dispute.
+
+### Operations
+- **Buildxact / single-source-of-truth** is sacred. If the system says X, X is the truth, not the verbal report from site.
+- **Engineered spec substitutions** require structural engineer sign-off. Never substitute on the builder's call alone (LVL, joist hangers, pier caps, structural fixings).
+- **HBCF certificate** must be active before site work in NSW residential.
+- **Subbie pay** is per-job, on-time. Late pay = subbie quits = job stops. Critical relationship.
+- **Practical Completion Date (PCD)** slips trigger client comms BEFORE they're a slip — never let a missed PCD be the first the client hears about it.
+
+### Marketing
+- **Most trades don't run paid acquisition.** Referrals + Google Business Profile + neighbour word-of-mouth.
+- **Content / social media is light** unless they're chasing premium positioning.
+- **Reviews are the #1 acquisition lever** — most trades neglect review-solicitation.
+
+### Compliance
+- **Council inspections** at frame, lock-up, completion. Schedule, attend, evidence.
+- **Engineer sign-offs** for any variation on engineered work.
+- **HBCF + builder's licence** must be current — clients can demand evidence.
+- **Asbestos protocols** for pre-2000 demolition / renovation. Hard rules, no shortcuts.
+- **Electrical / plumbing certs** delivered on completion of any electrical / plumbing work.
+
+### Channels
+- **WhatsApp groups per site** — primary subbie comm.
+- **Phone calls + voicemail** — primary client comm.
+- **Email** for quotes, variations, invoices (formal record).
+- **SMS** for "running 30 late" updates.
+
+## Demo prospects in this industry
+
+- **[[../../01_Customers/_demos/coastal-built]]** — residential builder, NSW Central Coast + Northern Beaches, 3-5 active builds
+- **[[../../01_Customers/_demos/hawkesbury-roofing]]** — roofer, parser-built, sales pipeline + finance focus
+
+## Adjacent — Pillarix conversation
+
+This wiki is **highly relevant** to the Pillarix licensing conversation. Pillarix builds vertical AI for construction PM. LeedAB serves construction without being construction-specific — per-customer manifest + this wiki carry the vertical depth. The conversation framing: "vertical depth × horizontal substrate" — Pillarix nails the vertical, LeedAB provides the substrate.
+
+## Cross-references
+
+- LeedAB-OS demo manifests: `clients/coastal-built/`, `clients/hawkesbury-roofing/`
+- Companion playbooks: `context/customers/{coastal-built,hawkesbury-roofing}/playbook.md`
+- Pillarix licensing inbound: `[[../../02_Sales/inbound/pillarix]]`
+- Adjacent wiki: [[supply-chain]] (overlap on materials delivery, supplier management)
+- Sales pipeline: [[../../02_Sales/pipeline]]

package/context/use-cases/hospitality.md

@@ -0,0 +1,76 @@
+---
+created: 2026-05-03
+updated: 2026-05-03
+type: wiki
+topic: customer-use-cases
+industry: hospitality
+maturity: stub
+tags: [wiki, customer-use-case, hospitality, cafe, restaurant, hotel, fitness]
+---
+
+# Hospitality / wellness — customer use cases
+
+> Service-led SMBs where the experience IS the product. Sunset Cafe and Element Pilates are demo prospects in this vertical. Promote real customer learnings upward as we land paying customers.
+
+## Common shape — hospitality SMB
+
+- **Single owner-operator or 2-3 partners** make all decisions; no formal management layer
+- **Front-of-house team** is part-time + casual; high turnover (annual ~80% in hospitality, ~30-40% in fitness)
+- **Customer relationships are first-name basis** — the founder knows half the regulars personally
+- **Word-of-mouth + Instagram drive acquisition** — not paid search, not cold outbound
+- **Retention is the business model** — hospitality + wellness are subscription-shaped (memberships, regulars, repeat dining); a churn-fix beats a new-customer-acquisition every time
+- **Ops are physical-world** — booking systems (MindBody, ResDiary, OpenTable), POS (Square, Tyro), rostering (Tanda, Deputy)
+- **Operating hours are non-business-hours** — staff messages fly at 06:00 (kitchen prep) and 22:30 (close-out)
+
+## Where LeedAB helps
+
+| Pain | Agent | Action |
+|---|---|---|
+| Customer questions ("are you open Sunday?", "do you do gluten-free?") | CX | Auto-reply via Instagram DM / Telegram bot, escalate the unusual ones |
+| Staff rostering shift-swaps | People + Ops | Coordinate WhatsApp rosters group, find covers, update Tanda |
+| Customer health / churn signals | CX | Surface "Sarah hasn't been in 3 weeks" patterns to the founder |
+| Content cadence (IG, email newsletter) | Content + Marketing | Maintain pillar/timely-content split, monthly community email |
+| New-member nurture | Email + CX | 30-day welcome + Day 7 / Day 21 check-in |
+| Reviews | CX + Marketing | Solicit reviews from happy customers, route negatives to the founder before they hit Google |
+| Stocktake / supplier orders | Procurement + Ops | Standing weekly orders, exception handling |
+| Local PR / community events | Marketing + Brand | Pitch to local press, organise events |
+
+## Likely licensed agent subset
+
+For most hospitality / wellness SMBs:
+- **Always:** coo, concierge, cx, marketing, content, campaigns, email, people, ops, finance
+- **Drop:** sales, engineering / build, devops, automation, investor, video (unless content-heavy)
+- **Tier:** typically tier-less (no `logistics-pro` equivalent yet); per-customer manifest carries the customisation
+
+## Industry-specific knowledge to bake in
+
+### Tone
+- **Warm, never transactional.** "We'd love to see you" beats "Book now."
+- **First-name, low-corporate.** No "team" pronoun; if the founder talks, the agent talks like the founder.
+- **Aspirational without pressure.** Wellness especially: "building strength" not "transform your body in 8 weeks."
+
+### Operations
+- **Class / table capacity is sacred.** Waitlist priority is the trust layer; never random-discount fill.
+- **Brunch / dinner / class rush windows** are the high-stakes moments — agents shouldn't message customers during them.
+- **Stockouts in food** are end-of-world for a 12-cover restaurant; signal-early-not-late.
+- **Roster legality** matters: minimum break, 18+ for late-night alcohol service, RSA / RSG certs.
+
+### Marketing
+- **Discount-led promotions cheapen premium positioning.** Boutique fitness / fine dining / specialty retail: avoid except acquisition (e.g. "first class free").
+- **Influencer collabs** are a minefield — must align with brand or do more harm than good. Default no.
+- **Local search** matters way more than global. Google Business Profile is the #1 marketing surface for most hospitality SMBs.
+
+### Channels
+- **Instagram DM is the primary inbound** for most. Email is secondary. Phone tertiary (and dying).
+- **WhatsApp groups** for staff comms (already entrenched, don't try to migrate).
+
+## Demo prospects in this industry
+
+- **[[../../01_Customers/_demos/sunset-cafe]]** — 3 venues, premium cafe group, Bondi/Surry Hills/Newtown
+- **[[../../01_Customers/_demos/element-pilates]]** — 2 boutique Pilates studios, Mosman/Manly
+
+## Cross-references
+
+- LeedAB-OS demo manifests: `clients/sunset-cafe/`, `clients/element-pilates/`
+- Companion playbooks: `context/customers/{sunset-cafe,element-pilates}/playbook.md`
+- Sales pipeline: [[../../02_Sales/pipeline]]

package/context/use-cases/logistics.md

@@ -0,0 +1,57 @@
+---
+created: 2026-04-30
+updated: 2026-04-30
+type: wiki
+topic: customer-use-cases
+industry: supply-chain
+maturity: stub
+tags: [wiki, customer-use-case, supply-chain, logistics]
+editing:
+---
+
+# Supply chain / logistics — customer use cases
+
+> Stub. To be populated as we onboard supply-chain customers (Tarheel is the first; this becomes the playbook). The OS already has a `supply-chain` vertical template (`muiez/LeedAB-OS:src/templates/verticals/supply-chain/`).
+
+## Common shape — supply-chain SMB
+
+- **Operations team** receives dispatches by phone / email / WhatsApp, manually creates jobs in TMS
+- **Drivers** report status via SMS or driver app; status flows are fragile
+- **Compliance** burden in AU: Heavy Vehicle National Law (HVNL), Chain of Responsibility, Fatigue Management
+- **Customer service** answers "where's my freight?" all day
+- **Finance** reconciles invoices vs jobs vs proof-of-delivery
+
+## Where LeedAB helps
+
+| Pain | Agent | Action |
+|---|---|---|
+| Inbound dispatch triage | COO + Email + Ops | Triage email + WhatsApp inbound, classify, escalate or auto-handle |
+| Job creation in TMS | Automation + Ops | Computer-use into the TMS to create job from inbound message |
+| Driver-status nudges | Concierge + Email | Polite "any update on job 1234?" loops |
+| Customer "where's my freight?" | CX + Concierge | Answer from TMS state without bothering ops |
+| Compliance reminders | Compliance + Ops | HVNL/CoR/fatigue check-ins, document trail |
+| Invoice reconciliation | Finance + Ops | Match POD → invoice → payment, flag mismatches |
+
+## Likely licensed agent subset for a supply-chain customer
+
+**Minimum (small operator):** COO, Onboarding, Delivery, Email, Ops, Concierge — ~6 agents
+
+**Standard (medium operator):** + Compliance, Procurement, CX — ~9 agents
+
+**Enterprise (multi-depot):** + Automation, Data, Finance, Legal — ~13 agents
+
+## Industry-specific knowledge to bake into agent context
+
+- HVNL + CoR — what's the agent's awareness level? Don't give legal advice; surface obligations + escalate to human
+- Common TMS systems (TransVirtual, MachShip, Cartage Australia, in-house) — for computer-use integrations
+- Common terminology: PUD (pickup-and-delivery), LTL, FTL, lashings, manifest, EDR (electronic document return), POD (proof-of-delivery)
+- ANZSIC code for filtering targeting: 4610 (Road freight transport)
+
+## Tarheel as the first paying customer
+- See [[../../01_Customers/Tarheel/overview]] for customer-specific details
+- Specifics they teach us → promote here as industry-level patterns
+
+## Cross-references
+- LeedAB-OS canonical vertical template: `muiez/LeedAB-OS:src/templates/verticals/supply-chain/`
+- Email agent (newly added): `~/code/leedab-workspace/agents/email-agent.md`
+- COO orchestrator: [[../../03_Product/ADRs/ADR-001-single-bot-per-customer]]

package/context/use-cases/professional.md

@@ -0,0 +1,61 @@
+---
+created: 2026-04-30
+updated: 2026-04-30
+type: wiki
+topic: customer-use-cases
+industry: professional-services
+maturity: stub
+tags: [wiki, customer-use-case, professional-services, agencies, consulting, legal]
+editing:
+---
+
+# Professional services — customer use cases
+
+> Stub. To be populated as we onboard consultancies, agencies, law firms, accountancies. Currently no LeedAB-OS vertical template exists — when we get our first professional-services customer, we extract one.
+
+## Common shape — professional services SMB
+
+- **Engagement management** — proposals, SOWs, time tracking, deliverables review
+- **Client communication** — email-heavy, with sensitive financial / legal / strategic content
+- **Knowledge management** — past client work as IP, often poorly indexed
+- **Billing** — milestone-based or hour-based, reconciliation pain
+- **Compliance** — varies by sub-vertical (legal: client confidentiality, conflicts checks; accounting: BAS / tax obligations; consulting: NDAs / IP)
+
+## Where LeedAB helps
+
+| Pain | Agent | Action |
+|---|---|---|
+| Email triage with sensitivity | Email + Compliance | Triage + draft, escalate sensitive (privileged / IP / financial) |
+| Proposal drafting | Solutions + Marketing | Draft from past similar proposals + customer brief |
+| Client meeting prep | Concierge + Research | Day-before brief: who they are, last conversation, open items |
+| Time tracking / billing | Finance + Ops | Reconcile calendar / dispatches → billable units → invoice draft |
+| Knowledge retrieval | Research + Data | "What did we tell ClientCo about retention strategy in 2023?" — answer from vault history |
+| Conflicts check (legal) | Legal + Compliance | Cross-check new prospect against existing clients for conflict |
+
+## Likely licensed agent subset
+
+**Minimum (solo practitioner):** COO, Onboarding, Email, Concierge, Compliance — ~5 agents
+
+**Standard (small firm 5-15 people):** + Research, Marketing, Finance, People — ~9 agents
+
+**Enterprise (mid-size firm):** + Legal, Data, Automation, Investor — ~13 agents
+
+## Industry-specific knowledge to bake in (per sub-vertical)
+
+### Legal
+- Privilege: agent-drafted communications must be reviewable for privilege classification
+- Conflicts check workflow against vault contact graph
+- Australian: Solicitors' Conduct Rules, AML/CTF obligations
+
+### Accounting
+- BAS, IAS, FBT, payroll tax — reminders + draft prep
+- Australian: Tax Practitioners Board, ATO digital partner if integrating
+
+### Consulting / agencies
+- IP retention clauses in client agreements
+- Project profitability analysis (revenue vs delivered hours)
+
+## Cross-references
+- (No LeedAB-OS vertical template exists for this yet — extract one when first customer onboards)
+- Email agent (likely most important for this vertical): `~/code/leedab-workspace/agents/email-agent.md`
+- Customer use case overview: [[supply-chain]] (the only vertical with template currently)

package/context/use-cases/retail.md

@@ -0,0 +1,80 @@
+---
+created: 2026-05-03
+updated: 2026-05-03
+type: wiki
+topic: customer-use-cases
+industry: retail
+maturity: stub
+tags: [wiki, customer-use-case, retail, ecommerce, maker, dtc]
+---
+
+# Retail / e-commerce — customer use cases
+
+> Direct-to-consumer brands, makers, online stores. Bondi Bloom Ceramics is a demo prospect. Spans solo-founder Shopify shops up to 10-person teams running Klaviyo + Meta ads + 3PL fulfilment.
+
+## Common shape — retail SMB
+
+- **Single-channel or multi-channel** — Shopify-primary, Instagram + farmers markets + wholesale stockists
+- **Founder wears every hat** below ~5 staff: marketing, ops, customer service, fulfilment
+- **Inventory is the constraint** — overstock kills cashflow; stockouts kill momentum
+- **Margin pressure is constant** — everyone in retail thinks they're undersold; most are
+- **Acquisition cost matters more than ever** — Meta CPMs up YoY; organic Instagram reach down
+- **Returns / exchanges are trust signals** — generous policy converts more than it costs (but founders fear it)
+- **Influencer + UGC drive content velocity** — paid alone doesn't work for makers / handcrafted goods
+- **Stockists / wholesale are 30-50% of revenue** for established makers — never undercut them with site-direct discounts
+
+## Where LeedAB helps
+
+| Pain | Agent | Action |
+|---|---|---|
+| Order status DMs ("where's my parcel?") | CX | Auto-respond with tracking, escalate the 3% that need a human |
+| Inventory replenishment | Procurement + Ops | Compute reorder points, place POs to suppliers, flag stock-outs before they happen |
+| Content cadence (IG, email, blog) | Content + Marketing + Brand | Maintain pillar content schedule, brand-voice consistency, drop alerts |
+| Drop / launch coordination | Marketing + Campaigns + Email | Coordinate Insta + email + paid for product drops |
+| Paid acquisition | Campaigns | Run Meta + Google + Pinterest, A/B test creative, optimise CAC |
+| Email lifecycle (welcome, abandoned cart, post-purchase) | Email | Maintain Klaviyo flows, segment, win-back |
+| Wholesale outreach | Sales + CX | Cold pitch to potential stockists, manage existing wholesale relationships |
+| Returns / exchanges | CX + Finance | Handle return requests, refund / exchange / store credit decisions, restocking flow |
+| Reviews + UGC | Marketing + CX | Solicit reviews, repost UGC with permission, build social proof |
+
+## Likely licensed agent subset
+
+For most retail / e-commerce SMBs:
+- **Always:** coo, concierge, cx, marketing, content, campaigns, brand, email, ops, procurement, finance
+- **Drop:** sales (unless wholesale-heavy), engineering / build, devops, automation, investor, video (unless content-heavy)
+- **Optional:** sales (wholesale lead-gen), people (when they have actual staff)
+- **Tier:** typically tier-less; per-customer manifest carries customisation
+
+## Industry-specific knowledge to bake in
+
+### Tone
+- **Brand voice is everything.** Maker brands have a distinct tone — "studio diary" not "store newsletter." Never genericise.
+- **Imperfection is on-brand for handmade.** Glaze pooling, kiln kisses, slight asymmetries are features, never apologies.
+- **Avoid sale-y language** for premium / artisan brands. "Drop alert" beats "shop now"; "sold out" is a flex, not a failure.
+
+### Operations
+- **Inventory accuracy is the trust layer.** Every "we'll let you know when it's back" is a customer who never returns.
+- **Drop schedule is the trust layer + #2.** Monthly cadences ("first Sunday kiln drop") build anticipation; missed drops break it.
+- **Pack-out time per order** is the constraint for handmade makers; the agent should never promise sub-3-day shipping if average pack-out is 7.
+
+### Marketing
+- **Stockists first, site second.** Never run a site discount that undercuts wholesale margin — that breaks the most important business relationship.
+- **Email > Instagram for revenue.** Instagram drives discovery; email closes. Build the list aggressively.
+- **Avoid hashtag spam.** One pillar word per post (e.g. #handmade, #ceramicart, #bondi); algorithmic returns on volume have collapsed.
+- **UGC > brand-shot photography.** Real customers in real homes converts better.
+
+### Channels
+- **Instagram DM is the #1 inbound** — questions, custom requests, wholesale enquiries.
+- **Email** is the brand's voice in the customer's pocket. Don't waste it on transactional-only.
+- **SMS** is rising but has a much lower trust ceiling — use sparingly.
+
+## Demo prospects in this industry
+
+- **[[../../01_Customers/_demos/bondi-bloom]]** — handmade ceramics, Sydney maker, Shopify + farmers markets
+
+## Cross-references
+
+- LeedAB-OS demo manifest: `clients/bondi-bloom/manifest.json`
+- Companion playbook: `context/customers/bondi-bloom/playbook.md`
+- Adjacent wiki: [[hospitality]] (overlap on local cafe + market vendors)
+- Sales pipeline: [[../../02_Sales/pipeline]]

package/context/use-cases/trades.md

@@ -0,0 +1,97 @@
+---
+created: 2026-05-03
+updated: 2026-05-03
+type: wiki
+topic: customer-use-cases
+industry: trades
+maturity: stub
+tags: [wiki, customer-use-case, trades, construction, building, plumbing, electrical, roofing]
+---
+
+# Trades / construction — customer use cases
+
+> Residential builders, plumbers, electricians, roofers, tilers, tradies. Coastal Built (residential builder) + Hawkesbury Roofing are demo prospects. Pillarix-adjacent for partnership conversations — relevant when LeedAB talks to vertical AI players in this space.
+
+## Common shape — trades SMB
+
+- **Director-led** — a licensed builder / electrician / etc. + 1-3 site supervisors + a roster of regular subbies (5-15)
+- **Bookings come from referrals + Google + neighbour-word-of-mouth** — almost never paid acquisition
+- **Quoting is bottlenecked on the director** — every quote requires their touch; that's the daily-operations chokepoint
+- **Job sites are mobile** — director drives between 2-5 active jobs/day; admin time is in the ute, in evenings, in the kitchen at 22:00
+- **Subbies are paid per-job, not salaried** — relationship management matters more than HR processes
+- **Materials delivery is a daily fire** — stockouts at site, suppliers running late, swap-in substitutions on engineered specs
+- **Compliance burden** — NSW Home Building Compensation Fund (HBCF), engineer sign-offs, council inspections, electrical certs, plumbing certs, asbestos protocols
+- **Cashflow is brutal** — progress payments lag job spend; one bad month wipes the year
+
+## Where LeedAB helps
+
+| Pain | Agent | Action |
+|---|---|---|
+| Quote backlog | Sales + Ops | Pre-fill quote templates from job notes, route to director for approval, send via email |
+| Subbie coordination | Ops + People | Maintain WhatsApp groups, coordinate site visits, track availability |
+| Material orders | Procurement + Ops | Standing supplier accounts, exception flags ("Bunnings out of 90×35 — substitute approved?") |
+| Site reports | Ops + CX | Daily 10-line site report from photos + voice memos, share with client |
+| Council / engineer sign-offs | Compliance + Legal | Track inspection schedule, flag overdue, draft RFIs |
+| Variations / change-orders | Sales + Legal + Finance | Formalise verbal "yeah she'll be right" into written variation + revised quote |
+| Progress invoicing | Finance | Auto-draft progress claims at milestones, send to client + bookkeeper |
+| Customer comms | CX + Concierge | "Is the demo still on Tuesday?" — proactive client updates, photos, ETAs |
+| Compliance evidence | Compliance | Maintain folder of cert pics, sign-offs, inspection records (audit-ready) |
+| Wet-weather / delay impact | Ops + CX | When a slip is happening, surface to client BEFORE it becomes a missed PCD |
+
+## Likely licensed agent subset
+
+For most trades / construction SMBs:
+- **Always:** coo, concierge, sales, ops, procurement, finance, cx, compliance
+- **Optional:** people (when they have admin staff or apprentices), marketing (when they want pipeline beyond word-of-mouth), legal (variations / disputes)
+- **Drop:** engineering / build / devops, content / brand / video, automation, investor, research
+- **Tier:** typically tier-less; per-customer manifest carries customisation
+
+## Industry-specific knowledge to bake in
+
+### Tone
+- **Plain, direct, blue-collar professional.** No corporate fluff. "Done" beats "executed."
+- **Subbie-first.** Comms via WhatsApp groups, not email. Voice notes acceptable.
+- **Time-zoned to AEST/AEDT.** "Tomorrow" means tomorrow on this coast.
+- **Money in writing.** Variations get formal change-orders. Verbal "she'll be right" never holds in a dispute.
+
+### Operations
+- **Buildxact / single-source-of-truth** is sacred. If the system says X, X is the truth, not the verbal report from site.
+- **Engineered spec substitutions** require structural engineer sign-off. Never substitute on the builder's call alone (LVL, joist hangers, pier caps, structural fixings).
+- **HBCF certificate** must be active before site work in NSW residential.
+- **Subbie pay** is per-job, on-time. Late pay = subbie quits = job stops. Critical relationship.
+- **Practical Completion Date (PCD)** slips trigger client comms BEFORE they're a slip — never let a missed PCD be the first the client hears about it.
+
+### Marketing
+- **Most trades don't run paid acquisition.** Referrals + Google Business Profile + neighbour word-of-mouth.
+- **Content / social media is light** unless they're chasing premium positioning.
+- **Reviews are the #1 acquisition lever** — most trades neglect review-solicitation.
+
+### Compliance
+- **Council inspections** at frame, lock-up, completion. Schedule, attend, evidence.
+- **Engineer sign-offs** for any variation on engineered work.
+- **HBCF + builder's licence** must be current — clients can demand evidence.
+- **Asbestos protocols** for pre-2000 demolition / renovation. Hard rules, no shortcuts.
+- **Electrical / plumbing certs** delivered on completion of any electrical / plumbing work.
+
+### Channels
+- **WhatsApp groups per site** — primary subbie comm.
+- **Phone calls + voicemail** — primary client comm.
+- **Email** for quotes, variations, invoices (formal record).
+- **SMS** for "running 30 late" updates.
+
+## Demo prospects in this industry
+
+- **[[../../01_Customers/_demos/coastal-built]]** — residential builder, NSW Central Coast + Northern Beaches, 3-5 active builds
+- **[[../../01_Customers/_demos/hawkesbury-roofing]]** — roofer, parser-built, sales pipeline + finance focus
+
+## Adjacent — Pillarix conversation
+
+This wiki is **highly relevant** to the Pillarix licensing conversation. Pillarix builds vertical AI for construction PM. LeedAB serves construction without being construction-specific — per-customer manifest + this wiki carry the vertical depth. The conversation framing: "vertical depth × horizontal substrate" — Pillarix nails the vertical, LeedAB provides the substrate.
+
+## Cross-references
+
+- LeedAB-OS demo manifests: `clients/coastal-built/`, `clients/hawkesbury-roofing/`
+- Companion playbooks: `context/customers/{coastal-built,hawkesbury-roofing}/playbook.md`
+- Pillarix licensing inbound: `[[../../02_Sales/inbound/pillarix]]`
+- Adjacent wiki: [[supply-chain]] (overlap on materials delivery, supplier management)
+- Sales pipeline: [[../../02_Sales/pipeline]]

package/dist/console-launcher.js

@@ -125,11 +125,20 @@ export async function startConsole(port = 3000) {
     // Next.js standalone reads HOSTNAME and PORT from the environment.
     // We launch with the current node binary so the customer doesn't need
     // a `next` CLI or a populated node_modules at runtime.
+    //
+    // Workspace root: respect whatever the CLI (bin/leedab.js) already
+    // set via ensureWorkspace(). On a fresh npm install that points at
+    // ~/.leedab/workspace/ (writable copy of the bundled templates); on
+    // a dev-tree checkout it points at the repo root. Fall back to
+    // findRepoRoot() when the env is unset — happens when the console is
+    // spawned without going through the CLI.
+    const workspaceRoot = process.env.LEEDAB_WORKSPACE_ROOT ?? findRepoRoot();
     consoleProcess = spawn(process.execPath, [serverEntry], {
         cwd: standaloneDir,
         env: {
             ...process.env,
             LEEDAB_STATE_DIR: STATE_DIR,
+            LEEDAB_WORKSPACE_ROOT: workspaceRoot,
             NODE_ENV: "production",
             HOSTNAME: "127.0.0.1",
             PORT: String(port),

package/dist/gateway.js

@@ -86,7 +86,10 @@ async function registerChannels(bin, stateDir, config) {
     let secrets = {};
     try {
         const raw = await readFile(resolve(stateDir, "secrets.json"), "utf-8");
-        secrets = JSON.parse(raw);
+        const parsed = JSON.parse(raw);
+        if (parsed && typeof parsed === "object") {
+            secrets = parsed;
+        }
     }
     catch {
         // No secrets file yet

package/dist/gtm/templates.js

@@ -1,7 +1,21 @@
 import { readFile, writeFile, readdir } from "node:fs/promises";
-import { resolve } from "node:path";
+import { resolve, sep } from "node:path";
 import { TEMPLATES_DIR, ensureGtmDirs } from "./paths.js";
 const FRONTMATTER_RE = /^---\n([\s\S]*?)\n---\n([\s\S]*)$/;
+// Mirrors apps/console/lib/gtm-store.ts:SAFE_TEMPLATE_NAME_RE. Template
+// names go onto the filesystem; reject traversal + shell metacharacters.
+const SAFE_TEMPLATE_NAME_RE = /^[a-z0-9](?:[a-z0-9-_]{0,58}[a-z0-9])?$/;
+function safeTemplatePath(name) {
+    const base = name.endsWith(".md") ? name.slice(0, -3) : name;
+    if (!SAFE_TEMPLATE_NAME_RE.test(base)) {
+        throw new Error(`Invalid template name "${name}" — must match ${SAFE_TEMPLATE_NAME_RE}`);
+    }
+    const candidate = resolve(TEMPLATES_DIR, `${base}.md`);
+    if (!candidate.startsWith(TEMPLATES_DIR + sep)) {
+        throw new Error(`Template name "${name}" resolves outside TEMPLATES_DIR`);
+    }
+    return candidate;
+}
 function parseFrontmatter(raw) {
     const m = raw.match(FRONTMATTER_RE);
     if (!m)
@@ -20,7 +34,7 @@ function parseFrontmatter(raw) {
 }
 export async function loadTemplate(name) {
     await ensureGtmDirs();
-    const path = resolve(TEMPLATES_DIR, name.endsWith(".md") ? name : `${name}.md`);
+    const path = safeTemplatePath(name);
     const raw = await readFile(path, "utf-8");
     const { meta, body } = parseFrontmatter(raw);
     const subject = meta.subject;
@@ -41,7 +55,7 @@ export async function listTemplateNames() {
 }
 export async function writeTemplate(name, subject, body) {
     await ensureGtmDirs();
-    const path = resolve(TEMPLATES_DIR, `${name}.md`);
+    const path = safeTemplatePath(name);
     const content = `---\nsubject: ${JSON.stringify(subject).slice(1, -1)}\n---\n${body.trim()}\n`;
     await writeFile(path, content, "utf-8");
     return path;

package/dist/license.d.ts

@@ -14,6 +14,12 @@ export interface LicenseInfo {
 }
 /**
  * Validate a license key against the API.
+ *
+ * Throws on transient upstream failure (5xx, network error, timeout) so
+ * the caller can fall back to the cached license. ONLY synthesizes an
+ * "invalid" payload when the upstream explicitly rejects the key with a
+ * 4xx — anything else is treated as "we couldn't reach a verdict" and
+ * must not corrupt the cache.
  */
 export declare function validateLicenseKey(key: string): Promise<LicenseInfo>;
 /**

package/dist/license.js

@@ -8,6 +8,12 @@ const REVALIDATE_DAYS = 7;
 const REVALIDATE_DAYS_TRIAL = 1;
 /**
  * Validate a license key against the API.
+ *
+ * Throws on transient upstream failure (5xx, network error, timeout) so
+ * the caller can fall back to the cached license. ONLY synthesizes an
+ * "invalid" payload when the upstream explicitly rejects the key with a
+ * 4xx — anything else is treated as "we couldn't reach a verdict" and
+ * must not corrupt the cache.
  */
 export async function validateLicenseKey(key) {
     const res = await fetch(VERIFY_URL, {
@@ -18,7 +24,11 @@ export async function validateLicenseKey(key) {
         },
         signal: AbortSignal.timeout(8000),
     });
+    if (res.status >= 500) {
+        throw new Error(`upstream unavailable (HTTP ${res.status})`);
+    }
     if (!res.ok) {
+        // 4xx — upstream definitively rejected the key.
         return {
             key,
             valid: false,

package/package.json

@@ -1,8 +1,8 @@
 {
   "name": "leedab",
-  "version": "0.5.3",
-  "description": "The AI operating system for companies. A brain that learns your business, Artificial Beings that run it. Local-first.",
-  "license": "SEE LICENSE IN LICENSE",
+  "version": "0.6.1",
+  "description": "The AI operating system for logistics. A brain that learns how your business operates, Artificial Beings that execute on the apps your team already use. Local-first.",
+  "license": "UNLICENSED",
   "author": "LeedAB <hello@leedab.com>",
   "type": "module",
   "bin": {
@@ -16,6 +16,12 @@
     "apps/console/.next/standalone/",
     "apps/console/.next/static/",
     "apps/console/public/",
+    "agents/",
+    "context/",
+    "clients/",
+    "wiki/",
+    "_schema/",
+    "README.md",
     "LICENSE"
   ],
   "scripts": {
@@ -26,20 +32,24 @@
     "prepublishOnly": "npm run build && npm --prefix apps/console install && npm --prefix apps/console run build"
   },
   "dependencies": {
+    "@anthropic-ai/sdk": "^0.92.0",
     "@aws-sdk/client-bedrock": "^3.1021.0",
     "@grammyjs/runner": "^2.0.3",
     "@grammyjs/transformer-throttler": "^1.2.1",
     "chalk": "^5.4.0",
     "commander": "^13.0.0",
     "conf": "^13.0.0",
+    "csv-parse": "^6.2.1",
     "grammy": "^1.41.1",
     "inquirer": "^12.11.1",
+    "nodemailer": "^8.0.7",
     "openclaw": "2026.4.15",
     "ora": "^8.1.0"
   },
   "devDependencies": {
     "@types/inquirer": "^9.0.9",
     "@types/node": "^22.0.0",
+    "@types/nodemailer": "^8.0.0",
     "eslint": "^9.0.0",
     "typescript": "^5.7.0"
   },