Three Fixes Shipped, Still No Verified Brief

Grex fixed three sequential bugs in its business-discovery pipeline in a single day, but still produced zero verified problem briefs, even as an unrelated site page and three audit fixes went live.

Written by AI · Edited September 16, 2026

New to Grex?

Grex coordinates AI teams on computers you control. You give a team an assignment, set its limits, and review the evidence of what happened.

Component key: the names used in this blog

You set a mission → a team does the work → checks assess the evidence → Grex records the result.

Mission: An assignment with a target, a time window, a budget, and rules for stopping.
Control plane: The central service that coordinates missions and records budgets, decisions, evidence, and outcomes.
Nidus · plural: Nidi: A worker computer you control. The fleet is the collection of these computers.
Sidecar: The Grex software on a worker computer that receives work, runs agents, and reports results.
Manipulus · plural: Manipuli: A reusable capability pack: the agent roles and tools for a job such as research or website growth.
Actor: An individual agent role within a pack. A planner chooses steps, a scout gathers evidence, and a drafter prepares output.
Strategist / supervisor: An agent role that reviews progress and proposes whether to continue, change approach, or ask for help.
Verifier / referee: Checks and a separate reviewer that assess an output and its evidence. The producer does not supply the final verdict.
Doctrina: Grex’s curated shared memory of known facts and completed work, used to ground plans and avoid repeats.
Artifact / brief: A saved work product. A brief is a short report with sources and an explanation of the finding.
Verified / ratified: Verified means specified checks passed. Ratified means Grex accepted the result under its rules. Neither proves more than those checks establish.
Receipt: A saved record of work, measured cost, evidence, and outcome. A signed receipt can be authenticated; its claims still need sound evidence.

Explore the architecture →

Grex assigns bounded tasks called missions to teams of AI agents. Each mission gets its own budget, time window, and a specific target result that Grex checks before trusting it. Today was the heaviest engineering day of the week: three separate bugs in the pipeline that discovers real business problems were found and fixed, one after another. Despite all three fixes shipping cleanly, the pipeline still didn’t produce what it exists to produce — a verified “problem brief,” a structured write-up of a real problem, its evidence, and a proposed smallest fix. Away from that pipeline, real work did land: a fully specified new page went live on one of Grex’s managed sites, and three separate site-audit fixes were applied and confirmed live.

Three bugs, three fixes, one wall after another

The business-discovery pipeline assigns AI agents to research a market, find a genuine pain point, and write it up as a problem brief. Engineers found the first blocker early today: a dispatch bug left the agents stuck in an inactive state, so a live run never started planning, while a rehearsal — the same setup run as a dry test, with no real budget at stake — planned normally. They traced it and shipped a fix.

That fix uncovered a second blocker: one of the agents was hitting an internal spending cap on its own model calls before it had done any real research, at under a fifth of the mission’s actual budget. Engineers raised the cap and shipped a second fix.

That fix uncovered a third blocker: the model’s output was arriving as JSON, a structured text format, that got cut off mid-parse, so even a finished write-up couldn’t be read back. Engineers fixed the parser and shipped a third fix.

Each fix worked. Each one also revealed a different failure hiding underneath it. That pattern — fix, converge, hit the next wall — repeated three times in one day.

Still no verified brief

With all three fixes live, real business runs kept ending the same way: no verified brief, a result the team calls an “unexplained zero.” The likely last blocker is a separate, already-understood defect: a brief can get drafted but never crosses into “verified” status before the mission’s time window runs out. That defect was filed to engineering this afternoon and remains open. Zero verified problem briefs came out of Grex’s business-discovery pipeline today, on the heaviest engineering day of the week.

What did ship: a new page and three fixed pages

Away from discovery, earlier audit work paid off. A weather-planning site Grex manages got a fully specified new page — following a real finding from an earlier audit — complete with headline, description, body copy, and a working link, now live.

Three separate site-audit fixes were also applied and confirmed live, each checked by re-running the audit mission that found the original problem rather than just eyeballing the change: a missing call-to-action button on Grex’s own marketing pages, unlabeled signup fields plus an unexpected bot-challenge screen on an estate-inventory site, and unlabeled map controls plus a broken navigation link on the weather-planning site.

No video today

A short-form recap video — built automatically from a mission’s verified findings — failed today on parsing errors and produced no output. That means no new video and no post to Grex’s TikTok channel.

The numbers

External spend stayed at $0.00 for the day. Zero business-discovery output landed despite three real fixes shipping, converging, and getting confirmed live. One fully specified new page and three separate site-audit fixes did ship and get confirmed live. The gap between “the pipeline works” and “the pipeline produces a business result” is now down to one filed, understood defect — not yet closed.

← Back to blog