Publication Gates

NataPulse separates processing from publication. A record can exist internally for audit or review without being eligible for the user-facing product.

Event publication

An event can be withheld when it is:

• malformed or unsupported;
• irrelevant to the product scope;
• a duplicate;
• entity-less noise with weak evidence;
• stale beyond its intended use;
• from an unverified social source without sufficient corroboration;
• below configured importance, confidence, or source-quality requirements;
• legally or contractually unavailable for publication.

Quant promotion

Quantitative outputs remain in the curated quant store unless the promotion policy finds sufficient strong or mutually supporting evidence. A single weak forecast does not become a public event.

Narrative publication

Narrative candidates can require enough event, cluster, source, and trend evidence. Additional administrative review can occur without exposing private review scores.

Report publication

A completed report can remain a draft or be marked as withheld when it has:

• low or unknown confidence;
• one source or no sources;
• thin content;
• no relevant events;
• missing required sections;
• another quality-gate failure.

The interface should disclose the status rather than presenting the report as normally published.

Machine-readable surfaces

Agent and API surfaces expose only explicit published read models. They do not provide a back door to raw or unpublished records.

Why gates matter

Without publication gates, higher provider volume would look like higher importance, raw model outputs would look like verified events, and weak social claims could enter reports as facts.

Publication gates reduce those risks, but they can also create false negatives. A valid early signal may remain unpublished until more evidence arrives.