31°46′40.7″N 35°14′07.7″E
Top Stories
The Wire
Editorial Standards

Editorial Standards & The Zioneer Signal

How The Zioneer reports: the five-level Signal credibility rating, the rules we enforce in code, open-source sourcing, and a plain account of how AI and human oversight work together.

⁦31°46′40.7″N 35°14′07.7″E⁩
01

How we report

The Zioneer is an AI-native intelligence desk. We monitor open, public sources around the clock, draft and edit every story through a structured pipeline, and attach to each one a visible credibility rating — the Zioneer Signal — so you can see how well-supported a claim is at a glance.

This page is the full account of that method. It is not a statement of intentions; the most important rules described here are written into the system as code, not advice. Where a constraint is enforced automatically, we say so and explain exactly what it does. We would rather under-claim and be trusted than over-claim and be caught short.

A note on where we are: The Zioneer is early in its life, and we are bringing the automated pipeline described on this page online in stages. Where a check is not yet applied to every story we say so, rather than imply otherwise. The Signal is deliberately conservative: it rises above Developing only when a story is corroborated by genuinely independent sources, and a single-source story is never shown above Developing, no matter how plausible. Nothing on this page is a capability we only hope to have; it is either live, or marked as being brought online.

Our standard is simple to state and hard to keep: report quickly, show our confidence honestly, separate what is corroborated from what is merely reported, and never present a generated claim as if it carried more certainty than its sources allow.

02

The Zioneer Signal

Every story we publish carries the Zioneer Signal — a five-level rating of how well the central claim is supported by the sources we have. The Signal is shown as a five-tick scale with a glyph and the level word, so the rating never depends on color alone. Read the live specimen below.

Confirmed — corroborated by multiple independent sources; high confidence.

Strong — multiple sources; well-supported, but short of fully confirmed.

Developing — single-source or early; reported, but not yet corroborated.

Doubtful — questionable; conflicting or weak sourcing.

False — assessed as untrue or debunked.

The Signal is not static. As corroboration arrives a story can climb from Developing to Strong to Confirmed; as a claim weakens it can fall. When that happens the story is updated in place and the change is recorded — it is not quietly swapped out. The Signal answers one question and only that question: how confident should you be in this claim, right now, given what we can see.

SPECIMEN · THE ZIONEER SIGNAL
  • Confirmed

    Corroborated by multiple independent sources; high confidence.

  • Strong

    Multiple sources; well-supported, but short of fully confirmed.

  • Developing

    Single-source or early; reported, but not yet corroborated.

  • Developing

    Questionable; conflicting or weak sourcing.

  • False

    Assessed as untrue or debunked.

Developing· 3/51 source · cannot be Confirmed

Live example — a single-source story can never read as Confirmed. The instrument clamps it to Developing and shows why.

03

What the Signal is — and is not

The Zioneer Signal is our own desk's credibility assessment. It is not third-party fact-checking. We are not certified by, and do not claim membership in, any external fact-checking network; the Signal is not a ClaimReview verdict and should not be read as one. It is the judgment of this desk about the state of the evidence, made visible.

That distinction matters. A Confirmed rating means our process found multiple independent signals that corroborate the central claim — not that an outside authority has audited the story. We show the corroboration count alongside the Signal precisely so the rating can be weighed, not just trusted.

We hold ourselves to the discipline of the rating. The honesty of the Signal depends on the rules in the next section, which are enforced automatically rather than left to good intentions.

04

Rules we enforce in code

Some standards are too important to leave to judgment under deadline pressure, so we built them into the pipeline itself. These are not editorial preferences; they are hard constraints the system cannot route around. As we bring each stage of the pipeline online, these are the rules it runs under.

Fewer than two sources can never be Confirmed or Strong. If a story has only one source, the system clamps its rating down to Developing automatically and shows a visible note — "1 source · cannot be Confirmed." There is no override. (This clamp is live today.)

Every claim must map to a source. A critic stage checks that each factual claim in a story is anchored to a source. An unsupported claim is a hard publish block — the story does not go out until the gap is closed.

Unproven allegations against named people are routed to human review. A story that levels an unproven allegation at a named individual is taken out of the automated path and held in human review, where it surfaces in an "under review" state rather than publishing on its own.

We never fabricate sources or quotes. The desk does not invent citations, attributions, or quotations to fill a gap. A claim without a real source is treated as unsupported — see the rule above.

Every published article exists in both Hebrew and English. Neither language is an afterthought; a story is not complete until both versions exist.

The system fails closed. On any error, or on hitting a budget limit, the pipeline does not publish. The safe default is silence, never an unreviewed story.

If any of these rules conflicts with speed, the rule wins.

05

Sourcing: open intake, Desk accountability

We report from open-source material that is publicly available: public channels, RSS and news feeds, and public reporting. We do not present ourselves as having private intelligence, exclusive access, or confidential informants we cannot describe.

The public publisher of routine bulletins is The Zioneer Intelligence Desk. Raw intake channels are operational provenance, not co-bylines or endorsements. We name an outside outlet, channel, document, or public authority when naming it materially helps readers evaluate a specific claim; otherwise the Desk takes responsibility for the published account.

Because our sourcing is open, it can be examined. A Confirmed or Strong rating reflects multiple independent open signals converging on the same claim; a Developing rating reflects a single signal or an account still settling. We weigh independence, not volume — ten outlets repeating one origin are still one source, and our process is built to recognize that rather than be fooled by an echo.

This is the honest boundary of what we do. We surface, corroborate, and rate what the open record shows. We are explicit about that scope so you can read our work for exactly what it is.

06

AI and human oversight, plainly

The Zioneer is AI-native. Our stories are generated and assembled by AI under human editorial oversight. We are telling you this directly because you deserve to know how the work is made, and because honesty about it is part of our standard.

Here is what that means. AI systems read the open sources, draft a candidate story, compare it against what we have already published to avoid duplicating coverage, decide whether it is new, an update, or not worth running, assign the Zioneer Signal, and check that every claim maps to a source. The integrity rules in the section above govern this whole chain, and we are bringing its stages online in sequence.

We are honest about the limits, too. AI can misread, misattribute, or overstate. The value of our model is not that the machine is infallible — it is not — but that the same disciplined process runs on every story, at speed, with the credibility instrumentation built in and visible. The strengths are consistency, speed, and the Signal; the safeguard against the weaknesses is the code-enforced rules and the human gate described next. We will not dress AI up as something it is not, and we will not pretend a traditional human newsroom we do not have.

07

The human gate

Autonomous publishing is off by default. A human gate sits at the end of the pipeline, and it is on until a person explicitly turns it off. Until then, the desk runs human-in-the-loop: the AI prepares the work, a person stands at the door.

Two categories never depend on that switch. Unproven allegations against named individuals are always routed to human review, and any story that trips an integrity rule is always blocked, regardless of the gate's setting. Those are absolute.

We are describing the current posture honestly rather than promising a fixed end-state forever. If and when autonomous publishing is enabled for routine, well-corroborated stories, the integrity rules and the named-allegation review stay in force — those do not switch off. Speed never overrides the safeguards.

08

Allegations, errors, and the record

Naming a person carries a higher burden, and we treat it that way. An unproven allegation against a named individual cannot publish on its own; it is held in human review and surfaces in an "under review" state until a person decides. We do not let an algorithm be the first and only judge of a claim against a real person's name.

When we get something wrong, we correct it openly. We version the story, mark what changed, and keep the record — we do not silently delete or rewrite history. A retraction stays on the page as a retraction. Our full corrections and retractions policy, including how to report an error, is set out on its own page.

The through-line of every standard here is the same: show our confidence, show our sourcing discipline, show our changes, and never let speed buy a claim more certainty than it has earned.

⁦EOF · 31°46′40.7″N 35°14′07.7″E⁩