Supplier corrective actions
Assemble inspection results, lot history and supplier reports, and find what evidence is missing or conflicting. Quality staff approve closure.
Knowledge packs
One core. A knowledge pack per domain.
A pack brings the vocabulary, document types, connector mappings, letter skeletons and test cases for one field. The law or policy you upload supplies the rules, deadlines and checks.
- Lemon law first pack Westland, drafted from the statute
- Banking product launch · BIAN core second pack Personal-loan review on a banking core
- Supplier corrective actions candidate Manufacturing quality
- Freight-charge disputes candidate
- Warranty recovery candidate
- Construction changes candidate
- Commercial fit-out candidate
Lemon law: what the pack brings
From the statute you upload
8 steps11 rules6 deadlines9 automation points5 letter templates
The test set was approved by Lena (control owner) on 11 Nov 2026.
The core stays the same
Cases and their deadlines, readable rule tables, the clause registry and its checks, and test cases that run before any release.
So does the authority
Everything sent by or checked through ai4bp passes the same gateway, and a person approves the exact action wherever an approval is needed. The AI can stop, but cannot release. When something new comes up, it proposes a step from the approved menu. New situations, never new powers.
Only the field changes
A pack swaps the words, the documents, the connectors and the letters. A new field starts from its rule book, not from a new product.
Pack 1 · Lemon law
The first pack drafts a case process from the statute.
A consumer's new vehicle has a defect the dealer could not fix. Give ai4bp the Westland Lemon Law and the firm's practice sheet, and it drafts eight steps from intake to close.
- Every step names its owner. A lawyer owns the notice, the arbitration choice and the settlement.
- Every step lists the clauses it must satisfy.
- The first release is synthetic: made-up cases in the fictional state of Westland.
- IntakeRecord the client, the vehicle and the delivery date, and get the fee agreement signed.Paralegal · WLL §2
- Collect documentsAsk the dealer for every repair order, read each with Vyxlo, and chase the dealer and the client.Paralegal · WLL §4(a) WLL §4(b)
- Decide eligibilityRun the period and repair-count rules. Maya confirms any case the rules cannot settle.Paralegal, then Maya · WLL §2 WLL §3(a) WLL §3(b) WLL §3(c)◉Acting aslawyer
- Send written noticeDraft the notice from the case facts and send it to the manufacturer's designated address, after the outbound gate and Maya's approval.Maya (lawyer) · WLL §5(a) WLL §5(b) WLL §5(c) WLL §6(a)◉Acting aslawyer
- Final repair attemptIf the manufacturer asks for one final repair attempt, tell the client and watch the window.Paralegal · WLL §6(b)
- Arbitration or demandExplain the state arbitration program and record whether the client chooses it or a demand.Maya (lawyer) · WLL §7(a) WLL §7(b)◉Acting aslawyer
- Settlement or suitWork out the refund or replacement, claim fees, and check any release before the client signs.Maya (lawyer) · WLL §8(a) WLL §8(b) WLL §9 WLL §11 WLL §12◉Acting aslawyer
- CloseConfirm payment, archive the file in Vyxlo and keep the limitation date on the calendar until the case is closed.Paralegal · WLL §10
Rule is_lemon: is the vehicle presumed a lemon? First matching row wins.
| When | Result | Clause |
|---|---|---|
| Same defect repaired 3 or more times | Presumed lemon | WLL §3(a) |
| 30 or more days out of service in total | Presumed lemon | WLL §3(b) |
| Serious safety defect repaired 2 or more times | Presumed lemon | WLL §3(c) |
| None of the above | Not yet presumed: keep collecting repair orders | WLL §3(a) |
Rule notice_recipient: is the notice going to the right address?
| When | Result | Clause |
|---|---|---|
| Recipient is the manufacturer's designated address from the owner's manual, sent by email or certified mail | Pass | WLL §5(b) |
| Recipient is anyone else, the dealer included | Hold the letter and propose the designated address | WLL §5(a) |
Deadlines 6 in the draft
Pack 1 · Rules
Rules a lawyer can read.
Each rule is a table: when this, then that, with the clause beside it. The draft has 11 rules and 6 deadlines, and the same tables decide every case.
- WLL §3 creates a presumption, so the rule says “Presumed lemon”, never “Lemon”.
- A notice addressed to the dealer is held, because WLL §5(a) requires the manufacturer's designated address.
Pack 1 · Review
Two checklists check the draft before anyone relies on it.
Does it match your design, and is it compliant? On the Harbor Legal draft, 4 items block release, and each has a named approver. The four fixes make v0.2 to v0.5, and then v1.0 is released.
- The AI can stop, but cannot release.
- No approval is ever made by the AI alone: the designer, the control owner or the lawyer decides.
Matches your design
✓9match
✕1conflict
✦1added by AI
Regulated and compliant
◆17enforced
○1referenced only
!1missing
The 4 items that block release, one per fix.
Your sheet accepts older vehicles than the law covers
WLL §2 sets 18 months or 18,000 miles; sheet line 3 says 24 months.
✦AI fix
Change practice sheet line 3 to 18 months or 18,000 miles.
◉Acting asdesignerChange the sheet⊘Ask for an exception
Ask for an exception: not available, statutory clause.
The AI added a dealer follow-up that is not on your sheet
Deadline d2, WLL §4(b): chase every 5 business days.
✦Your call
◉Acting asdesignerKeep itRemove it
The arbitration program is mentioned, but nothing checks it
WLL §7(a) The client is told before any suit.
✦AI fix
Add a check to step 6 that the client was told about the arbitration program.
◉Acting ascontrol owner
The notice letter lacks a sentence that the law requires
WLL §5(c) The client's choice of refund or replacement.
✦AI fix
Template t1 gains the client's choice sentence, and the outbound gate gains the disclosure check.
◉Acting ascontrol owner
Release is locked. 4 items to resolve.
◉Acting asdesigner
⊘Release v1.0: locked
Pack 2 · Banking product launch on a BIAN core
Launch a loan the way your own policies say.
A new personal loan is checked against the bank's credit, affordability and consumer-protection policies, and built on the service operations your core exposes. It needs a BIAN core, or a mock of one, and your policies. The policy numbers here are made up.
Matches your design
✓1match
✕1conflict
Regulated and compliant
◆1enforced
!1missing
Matches your design2 lines of your sheet
Check the credit rating before every offer
BIAN service domain Customer Credit Rating
Send loans above 25,000 to the credit committee
Policy CR-4 refers every loan above 20,000
✦AI fix
Change the sheet to 20,000, or ask the policy's owner for an exception.
◉Acting asdesignerChange the sheetAsk for an exception
Regulated and compliant2 policies apply
Policy AF-2 Affordability is checked before approval
Rule affordability, tested on 5 clients
Policy CP-7 The offer states the total cost of credit
The offer template lacks it.
✦AI fix
Add the total cost of credit to the offer template. The check before any offer goes out is a new control, so the control owner approves it.
◉Acting ascontrol ownerApprove the template change and the check
Release is locked. 2 items to resolve.
◉Acting asdesigner
⊘Release v1.0: locked
Same two checklists as the lemon-law pack. The sheet says 25,000 and the bank's own policy CR-4 says 20,000, so the draft is stopped until someone decides.
Pack 2 · Call trace
A held offer, then the loan booked against it.
The first offer was drafted outside the released template and left out the total cost of credit, so the gateway held it before it went to the customer. The offer was reissued from the template with the total cost of credit, and the customer accepted it. Then the loan was booked against that accepted offer, and a credit officer approved it. The trace shows each check, in order. It runs after the pack’s release, and the review above it still shows the release locked.
customer_offer.initiate
the first offer, drafted outside the template
‖held
JSON in
{
"tool": "customer_offer.initiate",
"case": "PL-3081",
"service_domain": "Customer Offer",
"offer_id": "OF-4417",
"party_id": "PR-20418",
"amount": 18500,
"term_months": 36,
"interest_rate": 9.4,
"monthly_payment": 591.75,
"total_cost_of_credit": null
}
Gate checks
- ✓On the approved action menupass
- ✓Rules, affordability and CR‑4 limitpass
- ‖Clause check, CP-7: the offer states the total cost of creditheld
- –Approval, credit officernot run
- –Executednot run
- –Verifiednot run
JSON out
{
"status": "held",
"reason": "the offer does not state the total cost of credit",
"policy": "CP-7",
"next": "reissue the offer from the released template"
}
Approved menu for this pack
Party Reference Data DirectoryCustomer Credit RatingCustomer OfferConsumer LoanPayment Execution
consumer_loan.initiate
the loan, booked against the accepted offer
✓approved
◉Acting ascredit officer
JSON in
{
"tool": "consumer_loan.initiate",
"case": "PL-3081",
"service_domain": "Consumer Loan",
"offer_id": "OF-4418",
"party_id": "PR-20418",
"amount": 18500,
"term_months": 36,
"interest_rate": 9.4,
"monthly_payment": 591.75,
"total_cost_of_credit": 2803.00,
"total_amount_payable": 21303.00,
"approval": { "by": "Nadia", "role": "credit officer", "at": "2026-11-11 11:20" }
}
Gate checks
- ✓On the approved action menupass
- ✓Rules, affordability and CR‑4 limitpass
- ✓Clause check, CP-7: the accepted offer states the total cost of creditpass
- ✓Approval, credit officerpass
- ✓Executedpass
- ✓Verifiedpass
JSON out
{
"status": "initiated",
"facility_id": "CL-77120",
"offer_id": "OF-4418",
"verified": true,
"evidence": "ev_3c18"
}
- The gateway can stop a call. It cannot release one that a rule or a person has not allowed.
- A loan above 20,000 would meet policy CR‑4 and go to the credit committee, not to a credit officer.
Candidates for later packs
More domains, from the same core.
None of these is built. Each is a field where evidence arrives from several parties, written rules apply, and a person approves the action. They come from ai4bp's cross-industry list of use cases.
Freight-charge disputes
Rebuild the timeline from invoices, free-time terms and gate events, and draft a dispute package with its sources. Specialists decide entitlement.
Warranty recovery
Reconcile repair notes, serial numbers, invoices and warranty terms, ask for missing proof, and assemble a supplier-recovery package. Warranty staff approve each claim.
Construction changes
Connect revised drawings, site instructions and cost evidence into a source-linked change package. Contract administrators approve changes.
Commercial fit-out
Reconcile authority comments, revisions and completion certificates across landlord, tenant and contractor. Each party keeps its own approval.
Try it
Start with the lemon-law pack.
Review the draft, run a case, handle an exception, approve a letter. The demo runs lemon law; its start screen shows two of the other packs.