What should we be asking?
Every uncertainty a sensor has recorded, including the ones the network refused to turn into a question. A signal is kept whether or not it ever becomes one.
Signals are grouped by the exact value of uncertainty_signals.topic_key, which the Scout writes when it records an observation. This is not a clustering: no similarity, embedding or emergence detection runs over signals anywhere in the engine, and none is invented here. Two signals are in one group when the Scout gave them the same topic key, and for no other reason.
observed_at is when the sensor says the thing was seen; discovered_at is when this system wrote the row. They are separate columns on purpose: collapsing them would make every 'who saw it first' claim unfalsifiable.
No ordering offered here ranks by how much of anything there is — not signals, not proposals, not readers. Volume is a measure of attention, and nothing on this site measures attention.
The state of the pipeline
Every count is zero, so there is no scale to draw one against. The statuses are listed anyway: a status missing from this list and a status standing at zero are opposite facts.
source/api/discovery/clusters· counts.signals_
What the network refused
An observation taken back out of the pipeline, with the reason kept on the row. It was never put to governance.
A question that was drafted, put to review and refused. Every named check the reviewer ran is kept and shown below.
Two refusals by two parties at two stages, counted separately and never added. A topic can be discarded repeatedly by the Scout and never reach governance at all; a topic can pass the Scout every time and be refused at review every time. Only showing what got through would make those two look identical. Right now, no uncertainty signal has been recorded, so there is no topic to group.
No share is drawn here. A refusal rate is computed per topic by the engine, with its method and version, and is drawn on the scale in every topic below. Nothing on this surface divides two counts and calls the result a measured rate.
source/api/discovery/clusters· counts.signals_
Topics the network has started noticing
most recently opened topic first, by the earliest discovered_at in the topic. An epistemic ordering: it answers 'what did the network start noticing most recently', not 'what is busiest'.
A topic appears here as soon as one uncertainty signal carries its topic_key. Signals are written by the Scout when a sensor records that some future fact is both uncertain and consequential; nothing else creates one. Until the pipeline has run against real observations, there are no topics to show, and that is a fact about the network rather than a missing section.
One recorded observation is enough: the first signal carrying a topic key opens a topic here, discarded or not. Right now, no uncertainty signal has been recorded, so there is no topic to group.
source/api/discovery/clusters· clusters· limit=12
The signals themselves
most recently recorded signal first, by discovered_at — the moment this system wrote the row, not the moment the sensor claims to have seen it.
A signal is one observation the Scout recorded, kept whether or not it ever became a question. Re-observing something already on record does not create a second row: the first finder keeps the credit and the original discovered_at stands.
A signal appears the moment a sensor records that some future fact is both uncertain and consequential. Right now, no uncertainty signal has been recorded yet.
source/api/discovery/signals· signals· limit=25
What the network is about to start asking
most recently drafted proposal first. A pending proposal has no governance verdict to order by and no measured property of its own, so the only honest ordering is when it was written.
A proposal is pending while its status is DRAFTED or SUBMITTED — drafted from a signal, not yet put in front of governance or not yet decided. Governance moves it to APPROVED or REJECTED in one act, so an empty list means the pipeline has nothing in flight, not that anything is hidden.
A proposal appears here the moment a signal is drafted into a question, and leaves it when governance decides. Right now, no question proposal has been drafted yet.
source/api/discovery/proposals/pending· proposals· limit=25