Loop INV-4 · Inventory & purchasing · reports to Lerris (+ leadership)

The buying desk's outside eyes, twice a month.

Researches our key material suppliers and world commodity prices on the 1st and 15th, and files a short brief that also lands in the company knowledge base — rebuilding the intelligence habit we lost when the old agent was retired.

Built & tested — pilotWave 3🕐 1st & 15th monthly⚙️ Claude research harness
Part 1 — the plain-english view

Wool, foam, Tencel — someone should be reading the market for us.

What it watches
  • A standing supplier watchlist — wool, cellulosic fibre, foam and cashmere suppliers we depend on
  • Commodity prices — strong wool first, the input that moves our costs most
  • Certification validity and capacity/expansion news that changes our negotiating position
When & how it speaks

A short brief on the 1st and 15th: what changed, why it matters to us, and a source per claim. The brief files itself into the company wiki inbox, so the knowledge brain learns it too.

Why it exists

The old supplier-intelligence job was retired in May with its prompts lost. Rebuilt fresh — and the first brief immediately earned its keep: it caught a 15-year-high wool price (≈2× year-over-year), a key supplier expanding into our region, and debunked a stale certification claim against the official register.

15-yr high
strong wool price caught in the first brief — ~2× year-over-year
2×/month
cadence — the 1st and the 15th, matching how fast this market actually moves
1 debunk
first run: a supplier-certification claim checked against the official register and corrected

1st & 15th

Twice-monthly rhythm

🔎

Researches the watchlist

Suppliers, prices, certifications, capacity news

⚖️

Verifies claims

Primary sources; registers over rumours

💬

Short brief

What changed + why it matters + sources

📚

Files itself

Into the wiki inbox → the company brain learns it

What it will never doNever contacts a supplier.
Where it stands today · July 2026Harness built, watchlist codified, first researched brief delivered — verified findings on wool prices, supplier expansion (a market-entry window narrowing), certification validity to 2029, and one supplier with no B2B terms. Opus reviews every brief before it enters the company brain.
Part 2 — under the hood

How it's wired: systems, models, and the path a number takes.

For implementers and the technically curious. The full build sheet — verified queries, thresholds, and build notes — lives on the specs page.

ReadsPublic web + registers
Supplier news, commodity prices, certification registers
StepResearch harness
Watchlist-driven sweep, claim verification
StepOpus review
It enters the company brain — so it ships-quality
DeliversBrief to Lerris
Email on the 1st & 15th
StateWiki inbox
Auto-ingested into the knowledge base next morning
System we read Automated step State / memory Human decision
SystemRole in this loop
Web researchwith source disciplineEvery claim carries a source; official registers outrank news posts.
Company wiki + GBrainknowledge baseThe brief drops into the wiki's inbox folder; the overnight router ingests it, so the company AI brain can answer from it.
Hermesagent runtime on our serverThe scheduler that wakes the loop up. Each loop is a cron job under a Hermes profile; the planned bizops profile will host the business digests (IT loops run under vpsops).
Email renderer + gwsrender_email.pyAll digests pass through one shared renderer: Huxberry-branded HTML, tables for repeated rows, a coral 'needs your response' box when the loop has questions, and an arrow link on every record. Sent from the loops mailbox via the Google Workspace CLI.
Agent Vaultcredential storeWhere API keys live. Loops get read-only credentials from the vault; nothing is hardcoded in scripts.
Model / brainWhat it does here
GPT-5.5 via Codexthe bulk-work modelWrote and maintains the mechanical parts — SQL, diffing, digest assembly. Effectively free on our existing subscription, so routine cycles cost almost nothing.
Claude Opusthe judgment modelReviews alert wording, thresholds, and anything a human will read and act on. Post-Fable, Opus owns everything that ships.
State & memory

The watchlist file (suppliers, topics, standing questions) plus prior briefs in the wiki — each new brief builds on what's already known.

Delivery

Email brief + wiki ingestion. Telegram summary optional later.

Safety rails

Read-only research; a human-reviewable brief is the only output. Anything entering the knowledge base is Opus-reviewed first.

Full build sheet →