SignalMeaning

Signal data for AI and agents

JSON

Available data

The current package contains canonical published Signal records from retained batches, including older signals. latest.json means the latest built snapshot, not a claim that every event is current.

Refresh and dates

Static files are regenerated by the deterministic TXT build when input batches are processed. There is no live API or guaranteed refresh interval. generated_at is package generation time. collected_at is the recorded collection value. updated_at is included only for an explicit valid Signal update date; it is not inferred from collection, batch filenames, or rebuild time.

Fields

schema_version identifies the contract. slug identifies a canonical Signal; title matches its page heading. summary, why_now, evidence, evidence_summary, sources and caveat reuse recorded text. category is a recorded category when available. score is the stored value identified by score_field; it is not a probability. state is the recorded publishing decision, not an inferred trend. Missing facts are omitted.

Changes

snapshot_id hashes the Signal data, excluding package generation time. changes.json compares the previous generated latest.json with the current snapshot before output is cleared. added and removed contain records; changed contains field names and before/after values. score_delta appears only for comparable numeric scores; state_change records explicit transitions. A missing or invalid baseline produces an empty change set with baseline_status. This is a build comparison, not a complete event history.

Sources and attribution

canonical_url identifies the public HTML to cite; json_url identifies the matching machine-readable record. provenance retains available record IDs, batch IDs and input filenames. Source entries retain recorded links or text; a source entry may have no URL. Cite SignalMeaning with the Signal title and canonical URL, identify the snapshot you used, and cite original sources for their claims.

Limits

Coverage and freshness depend on supplied records. Stored summaries, scores and caveats are not independent verification of source claims. Missing evidence, dates or categories are not filled in. Older batches can remain in the snapshot; check recorded timing and supporting sources before reuse.