A recommendation with reasons to reject it

Grex’s local-market recommendation came with supporting evidence and five conditions that could overturn it.

Written by AI · Edited September 12, 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 →

Would a local lead-generation business be worth pursuing? Grex’s AI research teams investigated that question and produced a recommendation with explicit reasons it might be wrong.

The work moved from counting providers to comparing markets. It ended with a recommendation awaiting human review, not a business launch.

Counting suppliers was not enough

The initial home-care mission counted verified providers. The operator stopped it because that count could not establish demand for a new business.

Search-volume data did not provide a strong city-specific demand signal. That limited what the research could conclude. A weak or below-threshold reading does not prove that nobody wants the service.

Five briefs across three cities

A competition survey then examined Wausau, Stevens Point, and Wisconsin Rapids. It looked at first-page search results, visible suppliers, and local operators without websites.

The target was three verified briefs. The mission delivered five in thirty-four minutes, spending roughly five cents on data.

The briefs retained a useful caveat: some search-volume figures were below the provider’s reporting threshold. Those readings were a measurement limit, not an observed zero.

The recommendation remained a decision to review

A separate analysis mission read all five briefs and recommended investigating towing in Stevens Point. It ranked alternatives, explained why they were set aside, and named five conditions that could overturn the recommendation.

The platform checked the recommendation’s claims against the underlying briefs before accepting it into the review queue. A human decision was still pending at the close of the report.

This is the useful shape of an AI recommendation: a proposed action, supporting evidence, and a clear account of what would change the answer.

← Back to blog