1. Discover where demand becomes visible
The scan starts from the company's customer segments and named accounts. It proposes relevant association, regulator, and trade-news sources, then resolves public company, jobs, investor, and news pages where customer, regulatory, economic, technology, and talent pressure may appear.
2. Capture pressure with provenance
Every signal must retain its headline, exact source URL, observation date, affected segment or account, direction, and implied demand. Signals expire when they become stale. A source-less assertion cannot enter the demand view.
3. Review before anything counts
Discovered sources and extracted signals enter review queues. Accepted, unexpired evidence can contribute downstream; rejected or expired evidence cannot. The public teaser auto-accepts only inside an isolated throwaway scope so it can produce a preview without changing a customer's real workspace.
4. Form likely-priority hypotheses
The system groups accepted signals into likely internal priorities and preserves the source chain behind each one. These remain hypotheses. They are compared with the known company model and classified as:
- Confirmed — the likely priority lands on a known offering, workflow, pain, asset, or constraint.
- Blind spot — public pressure suggests a priority, but the current company evidence does not show where it lands.
- Zombie — an internally important area has little current public-demand support and deserves review rather than automatic removal.
5. Turn uncertainty into discovery
Missing internal support becomes a focused interview agenda: who owns this pressure, what process handles it today, what evidence would confirm it, and what would refute it? Public evidence starts the conversation; employees, systems, and operating records establish what is true.
6. Influence ranking within strict bounds
An accepted priority can apply a visible, capped ranking adjustment to an AI opportunity already grounded in internal evidence. It never creates an ordinary candidate by itself. Three dedicated operators cover exceptional cases: Mandate Gap for a missing capability suggested by demand, Demand Bottleneck for pressure on a known workflow, and Zombie Audit for an internally important area that may need revalidation.
7. Carry only validated opportunities into build gates
Selected opportunities still have to clear feasibility, safety, evaluation, pilot, and production-handoff gates. External urgency cannot override missing data, unclear ownership, unsafe actions, or weak evaluation coverage.
The result is a traceable chain from dated public evidence → likely business priority → internal validation → grounded opportunity → gated agent package.