Commercial Automation

Recovery workflows for missed commercial intent.

HIBS Rescue applies the same control pattern to everyday commercial leakage: missed calls, stale quotes, readiness problems, inspection follow-up, and safe schedule gaps. The goal is recoverable work with evidence, not vague automation.

Products

HIBS Rescue

Umbrella for recovery workflows: detect commercial leakage, choose one safe intervention, dispatch it, and preserve evidence.

Status: MVP portfolio / pilot-stage beyond core Lead Rescue

LicenceDuty

Governance-first multi-site licence-obligation engine: cited email/document ingest, human approval, full point-in-time SHA-256, append-only stream, SQL audit, five-event replay capsule and independently verifiable export bundles.

Status: implemented at 32b6034; 59 statutory tests reported passing; verify and LOI seed green; production and customer qualification remain separate

PRS Ready

Private-rented-sector readiness and compliance operations: portfolio imports, certificate evidence, drift detection, notifications, landlord portal, CRM profiles and listing-field exports.

Status: phases 1–6 implemented at c9e20c1; 27 statutory tests passing; revenue validation remains

Lead Rescue

Missed-call and missed-enquiry recovery with controlled follow-up, operator handoff, proof packs, and pilot diagnostics.

Status: most mature commercial surface; real provider setup required for live use

Quote Rescue

Finds draft, stale, viewed, accepted, declined and expired quotes, then creates the correct customer chase or office task.

Status: implemented lane; pilot needs quote export or provider webhook mapping

Gap Rescue

Capacity recovery lane for pulling ready, movable work forward when consent, schedule, and operational constraints allow it.

Status: pilot-stage lane inside HIBS Rescue

Rescue Broker

Chooses one primary rescue action when a quote, job, visit, inspection or diary event qualifies for multiple lanes.

Status: deterministic routing, conflict suppression and dashboard visibility implemented

Statutory Product Portfolio

Product	Port	Wedge
LandlordDuty	8080	Possession
CreditDuty	8081	CONC reconstruction
PRS Ready	8082 / 8083	PRS registration
LicenceDuty	8084 / 8085	Multi-site licence-obligation evidence

Qualification is product-specific. LicenceDuty 32b6034 (59 tests reported), CreditDuty c34a101 (34 tests reported), LandlordDuty 340388d (73 tests reported) and PRS Ready c9e20c1 (27 tests reported) remain separate qualification claims. Preservation snapshots: mc8h7dxz6t-ui/licence-duty, prs-ready, landlord-duty.

LicenceDuty — Governance-first implementation

The implementation follows an adapter hierarchy: official API, register poll, email forward, then upload. Every extracted field carries provenance and confidence; disagreement creates an exception rather than a silent overwrite; nothing becomes active before human approval; and identity migration across UPRN, company and FSA identifiers creates an exception rather than a duplicate.

Phase	Implemented scope
2 — Ingest	Postmark inbound, SharePoint acquisition watch, optional Textract OCR, approval API and inbox poll job.
3 — Official data	Companies House, FSA FHRS sync with ID migration, local-authority register polling and reconciliation job.
4 — Evidence	SIA rota coverage, minimised POS aggregate, annual-fee receipt, variation-approval stub and assign/resolve exceptions.
5 — Distribution	Consultant heatmap, branded partner report, Stripe consultant-plan route and multi-tenant Postgres SaaS layer.
6 — Discipline	Six hospitality obligation types only; POS evidence minimisation; no council scraping or application submission.

Operational routes

POST /v1/ingest/document — PDF to cited extractions and approval queue.
POST /v1/ingest/email — local-authority email forward.
POST /v1/reconcile/{premises_id} — create an exception on mismatch.
POST /v1/evidence/auto/{premises_id} — rota, POS aggregate and fee evidence.
GET /v1/partner/report — consultant portfolio console.

Boundary: Phase 0 still requires ten group interviews, two consultant LOIs and five real licence PDFs. Production providers require Companies House, Postmark, Clerk, Stripe and optional Textract credentials. The build is not a council scraper, application-submission service, government endorsement or validated revenue claim.

Point-in-time export and audit

Full bundle, obligation-pack, replay-capsule, PDF, SQL-audit and NDJSON-stream APIs.
Every active obligation binds page citation, approver ID, rules version and full 64-character SHA-256.
licence_duty_replay_capsule_v1 records five hash-chained events; this is governance-capsule replay, not a claim of universal engine re-execution.
verify_export.py checks pack, bundle, capsule, AI-safe manifest and hash length.

Evidence: commit 32b6034; 59 statutory tests reported passing; verify and LOI demo seed reported green.

PRS Ready — Implemented Scope

The code roadmap is complete through Phase 6. Phase 0 is intentionally a commercial-validation playbook rather than a software-completion claim.

Phase	Status	Implemented scope
0	Playbook	Interview, LOI and TEST_C validation process in `demo/PHASE0_VALIDATION.md`.
1	Done	Core engine, pilot UI on :8082 and compliance stamp.
2	Done	CSV import, certificate OCR, local/S3 storage and drift job.
3	Done	Postmark T-60/30/14 notifications, HMAC webhooks with retry and portfolio heatmap.
4	Done	FastAPI on :8083, Clerk/Stripe mocks, Postgres/SQLite, audit log and landlord portal.
5	Done	Reapit, Apex27 and street-CSV import profiles plus Zapier trigger.
6	Done	Flagged LivePortalAdapter, LR/PRN sync, Rightmove/Zoopla export and filing fee.

Operational surface

POST /v1/portfolio/import/csv — bulk portfolio import.
POST /v1/portfolio/import/reapit_v1 — CRM-profile import.
GET /v1/dashboard/heatmap — portfolio readiness.
POST /v1/drift/scan — alerts and webhook dispatch.
POST /v1/portal/submit — government portal adapter; mock unless explicitly enabled.
GET /v1/marketing-gate/{id} — listing-fields export.

Production boundary

Clerk, Stripe, Postmark, S3 and government-portal integrations auto-select live providers only when their production keys and flags are supplied. The remaining gate is commercial evidence: ten agent interviews, TEST_C competitor scoring and two LOIs at £200–500 per month. “Code complete” does not mean revenue validated, government endorsed or deployed to live customer portfolios.

Evidence: commit c9e20c1; pytest tests/statutory -q reported 27 passing tests.

Included Recovery Lanes

Missed-call and missed-enquiry capture.
Quote follow-up where no clear customer outcome exists.
Start readiness checks before booked work begins.
Visit readiness checks for access, contact, travel, and parts issues.
Inspection follow-up for findings, remedial evidence, and sign-off.
Gap filling when work can be moved safely and rules allow it.

Integration Depth

Input	Implemented mapping	What a pilot still needs
Quotes	HubSpot/Jobber/garage/generic-shaped quote records plus customer-specific field aliases map into Quote Rescue and Broker decisions.	Customer confirmation of quote ID, customer, phone, status, value and sent-date fields.
Jobs / starts	Job records map into Start Rescue readiness checks: deposit, materials, access, crew, customer readiness.	Customer-specific start date, value, readiness fields and booked/closed/cancelled status rules.
Visits / schedules	Visit records map into Visit Ready checks: appointment, access, contact, parts/tools and travel.	Live schedule export, API endpoint or webhook from the customer's diary system.
Inspection forms/photos/documents	Inspection records accept form, photo and document evidence hashes without exposing raw files in proof packs.	Actual inspection form/photo/document source and agreed evidence identifiers.
Diary gaps	Capacity gaps plus ready/movable candidates map into Gap Rescue.	Real diary availability, open-work candidate export and capacity-value assumptions.
Broker decisions	Dashboard shows selected action, suppressed alternatives and review cases from the event chain.	Real event volume from the pilot customer.

These lanes should not be sold as fully deployed SaaS without real Twilio/provider setup, CRM/job-system mapping, consent handling, customer onboarding, and operational monitoring. They are now suitable for a controlled pilot using CSV exports, signed webhooks, or one lightweight CRM/job-system adapter. Each pilot can now carry an adapter profile for field aliases, credential state, webhook signature shape, diary source, inspection evidence source and CRM/job-system rules.