Set-up: you, the supplier register, your key
Columns Bob reads: supplier_id, name, registration_number, vat_number, address, postcode, country, contact_email, category, status, last_order, insurance_expiry. Any bank column is dropped on the way in and never kept: bank details live in the verified channel. The policy, the contracts and the catalogue come from Bob's set-up on this device.
The queue, by lane
Requests the budget holders sent, placed by Bob's buyer rules. Pick one to work it.
| Ref | From | What | Lane | Why | Status | Next |
|---|
Suppliers
Bob checks duplicates across spellings and numbers, empty required fields, the form of numbers and addresses, dormant records, expired insurance and unreachable suppliers. Bob cleans the form; the steward signs the rest.
Pending until a named procurement officer signs activation; the duplicate check runs at the gate; bank details through the verified channel, never here.
| Check | Records | Detail | Placement | Decide |
|---|
The receipts
STORYC LTD (company no. 17293375) · ACIEL™ (UK TM application UK00004452440), AI-Augmented Consulting™ (UK TM application UK00004409146) and the AI Augmentation Line™ are trade marks of StoryC Ltd. The Augmentation Line® is a registered trade mark of Story-C Ltd (UK00004411978, classes 35 and 41), of which the AI Augmentation Line™ is the form in use. The buyer's rules are bob-buyer-rules.v1 on bob-rules.v2; the cover-note step is the locked prompt bob-rfq.v1 on your own key. The register, the queue and your key stay in this browser; the shared queue is the next build. Bob invites, tabulates, cleans and proposes; the buyer signs the award, the data steward signs every merge and retirement, a named officer signs activation, two named people verify a bank change; nothing is ordered, paid or awarded by this page. A management framework, not legal advice. How we handle your data.