How Evan selects the news

Who Evan is

Evan (@evangalize) is the byline on every story in Feason’s News channel. Evan is an AI system, not a person: not a reporter, not a pastor, not an eyewitness to anything described on this site. Evan does no original reporting whatsoever. Every item is a summary of a report published by someone else, and every item links to that report so you can read the source rather than take the summary’s word for it.

Feason’s long-form articles are a different pipeline with a different byline and different guarantees — see how Ezra articles are made. Articles by human members are posted under their own accounts and pass through neither pipeline.

Where the stories come from

Feason polls a fixed list of Christian news feeds on a schedule, taking the least-recently-checked ones first so no single outlet dominates a run. Items older than ten days are ignored, and an item Feason has already seen is never proposed twice — including one that was previously rejected.

Nothing is scraped beyond the feed. Evan reads the headline and the summary the publisher chose to syndicate, and writes from that alone.

What the channel carries, and what it rejects

The beat is constructive Christian news in six areas: faith, service, community, creation, science, and culture. An item is rejected outright if it is about war or violence reported as atrocity, partisan politics, disaster or crime reported as the event itself, shame- or guilt-driven framing, contempt toward any group, or one tradition’s disputed position presented as universal Christianity. Opinion columns, devotionals, advertisements, event listings, and press releases without reported substance are not news and are rejected too.

The filter is instructed to reject whenever it is uncertain. A skipped story costs nothing; a wrong one costs a reader’s trust. Anything that survives must then clear the same edification-versus-reactivity scoring the rest of Feason uses — a second, independent gate that has rejected items the first one passed.

Feason is non-denominational. A story specific to one tradition is welcome and is labeled as such; a story that treats one tradition’s disputed doctrine as all of Christianity is not.

How a summary is written

• Evan’s own headline. The source’s headline is not reused. Feason publishes alongside the original report, and copying its headline would put the two in competition on identical words while helping no reader.
• Facts only from the item. Names, numbers, places, and dates must appear in the syndicated item. Evan may not add context, background, or detail from anywhere else — including from the model’s own knowledge.
• Reported substance or nothing. An item that does not carry enough reported detail to summarize is rejected rather than padded out with generalities.
• No exhortation. Plain declarative prose. No application, no rhetorical questions, no scripture quotation, no addressing the reader.
• Attribution in the body. Every item carries an inline disclosure that Evan summarized it, and a link to the original report, in the text itself rather than only in metadata.

Review, and what it does and does not promise

The channel runs in one of two modes, and the difference matters enough to state plainly.

• Filed for review. The default. An accepted item becomes a draft that no reader can see until a Feason editor approves it.
• Published on the filter alone. An accepted item goes live without a person having read it. What reaches you is then only as good as the editorial filter’s worst call of the day, which is why the filter fails closed, the scoring gate runs independently, and the number of unreviewed items that may go live in any 24-hour period is capped.

Feason records which of the two applied to each item. An earlier version of the inline disclosure said every story had been “reviewed by a Feason editor before publication”; that was true of the first mode and false of the second, and it has been corrected to describe the screening that actually applies to both.

Limits and corrections

A summary can be faithful to a source that was itself wrong, and an automated filter can misjudge a story. Evan’s summaries are not reporting, not verification, and not endorsement of the outlet that published the original. Read the linked report before relying on anything here.

If you find a factual, framing, or attribution problem — or a story that should not have run — please use the contact form and include the page URL. Feason may correct, update, or withdraw the item, and retracted items are removed from the channel rather than edited silently.