Clients
Each client is a company Sensory watches the outside world for. Pick one to configure what's sensed and benchmarked, or add a new one.
Client profile
Enter everything you already know — the client's own channels and each competitor's social handles — so Sensory tracks the right accounts instead of guessing. Multi-value fields are comma-separated. Editable any time.
Generate a research prompt, paste it into Claude.ai (deep research), then dump the returned JSON back here. It fills the client's own channels + competitor handles below — which you then review and edit. Only verified, brand-owned official accounts; never fan/reseller/parody pages.
One card per competitor. Save upserts by name; Remove deletes. The blank card at the bottom is for a new competitor — fill it and Save.
Configure
Edits this client's overrides — competitors, tracked metrics and exposure map — applied only to this client. (Shared industry definitions live in Taxonomy.)
—
Each dimension is a relation in the client's exposure ontology. Edit the watched entities and weight; saving replaces that dimension. This drives both what we crawl and how news is scored.
Core asks. Sensory gathers.
Sensory is the nose: Core asks for the external context around a moved metric (or a window), and Sensory returns all relevant evidence — macro, calendar, competitor, benchmark — structured and source-stamped. Core (the brain) decides how much each factor influenced the signal. Sensory never attributes.
request payload Core sends
request payload Core sends
API tester
Compose a request exactly as Precision Core would send it, and see Sensory's raw JSON response. Pick an endpoint, edit the request, send. Requests run against the currently selected client.
Send a request to see the response.
Benchmark ops
Generate a Deep Research prompt, import the cited result, run an autonomous refresh, and approve pending benchmarks into production. (See the runbook.)
Taxonomy
Manage industries, sub-industries and the industry→vertical routing as data — no code change. Routing decides which exposure ontology and benchmark catalog a client gets from its industry text; the resolver under Routing lets you verify it live.
Higher priority wins on a tie. keyword matches if the pattern appears anywhere in the client's industry text; exact matches the whole string. Falls through to the defaults below when nothing matches.
Pick a base industry to edit its exposure template. Sub-industries inherit their parent's template, so only base industries appear here.
The building blocks of the benchmark catalog. Adding a metric spawns empty benchmark cells across every vertical immediately — acquire their figures from Benchmark ops. A global sanity band is required (the acquisition gauntlet rejects out-of-band candidates). Retiring drops a metric's cells from the live catalog but keeps its published history.
Channels apply to channel-group metrics (e.g. ROAS, CPM) — each live channel spawns a cell per channel-metric per vertical.
Each metric carries a global band (shown in the table above). A per-vertical override narrows the acquisition gauntlet for one vertical only — leave the metric's global band untouched.
Signals, and the evidence around them.
For each signal Core detected, Sensory gathers the relevant external evidence — macro, calendar, competitor, benchmark — structured and source-stamped. Core decides how much each factor influenced the signal; Sensory never attributes.
Review → Core
Nothing reaches Precision Core until an OpenMinds analyst approves it. Sensory proposes; a human signs off; only then is it delivered.
Feeding Precision Core
Sensory pushes external context into Core via its APIs — signals, covariates, context artifacts. Outbound only.
External context, sensed.
Loading…
| Time | Stage | Client | Model | Tokens | Cost (USD) |
|---|
| Time | Endpoint | Input | Output | Credits |
|---|
| Time | Source | Op | Detail | Units |
|---|
Calendar management
The shared forward calendar — known-future demand drivers used for ranking and relevance (never a causal claim). Public holidays and the major mega-sales/commercial dates are computed automatically; operator events are added below. Hide a computed event to drop it from clients' calendars for a year; retire or delete an operator event you added.
Operator events repeat every year on the chosen month/day and appear in the calendar after the next refresh.
Draft a set with deep research, then import
Add commercial/cultural demand-driver events without code. Public holidays and the major festivals are handled automatically — only add what's missing. Generate a research prompt, run it, then paste the JSON result here to import.
Scheduler
The auto-run board — what each kind runs on, when it last ran, when it's next due, and its current state. Paid kinds pause automatically when their monthly budget cap is reached. Use Run now to trigger a kind on demand (the monthly cap still applies).
—
| Kind | Cadence | Last run | Next run | State |
|---|
Sources
What Macro Watch crawls — RSS feeds are editable here; targeted & structural sources are managed elsewhere. Each source shows when it was last ingested.
These feeds are read on every macro refresh. Add, edit, disable or retire them — changes flow into the next crawl. RSS feeds report collectively under the rss connector, so per-feed counts aren't tracked; the collective freshness is shown below the table.
| Label | URL | Limit | Enabled | Actions |
|---|
The rest of what Sensory grabs. These aren't edited on this page — they're driven by client config, the taxonomy, or code — but their freshness is shown so you see the full picture.
| Source | What it is | Managed by | Records | Last ingested |
|---|
Live crawls only reach back a few months. To backfill the archive, generate a deep-research prompt for a client + date window, paste it into Claude.ai (deep research), then dump the returned JSON here. Imported events are shared dated facts (no causation), queryable by any client whose window overlaps.
Macro Watch
Tiered external news & events that could affect demand or costs — ranked by relevance to this client. The period you pick is the window Core would request.
Calendar
Known-future demand drivers — public holidays, mega-sales and commercial/cultural events (Mother's Day, Ramadan, 11.11…). These are the windows Core can plan around.
Industry Benchmark
The industry "normal band" for each metric this client tracks — scoped to their industry & channel. Each figure carries a geographic scope (🇲🇾 Malaysia · 🌏 SEA · 🌐 global) and a confidence tier (🟢 verified · 🟡 partial · 🔴 proxy), and a citation.
Competitor Movement
Social listening on this client's rivals — promos, launches, share-of-voice — in chronological order, unranked. Sensory reports the moves; Core weighs them.