​

Feed Intelligence

Feed Intelligence connects recurring outlet feeds with PressChain publication workflows. The goal is to make verified syndication and ingestion practical while preserving outlet authority and non-custodial publishing rules.

​

Feed registration

Current V3 action policy classifies rss.feed.register as an elevated economic action. It requires an Editor role plus outlet administration or Enterprise project authority. That makes feed registration an intentional organizational action, not something any connected wallet can perform for an outlet.

​

Delegated feed publishing

rss.feed.publish is modeled as a delegated non-public economic action for Author, Journalist or Editor roles with standard fee semantics and authorized non-custodial publisher delegation. The important phrase is authorized non-custodial delegation. A feed worker should not solve automation by storing an unrestricted newsroom private key on a server.

​

Suggested ingestion pipeline

​

Verify the outlet binding

Before processing items, confirm that the feed is still bound to the expected outlet authority. A valid XML document at a familiar URL is not enough to establish publication authority. Treat feed ownership and protocol authorization as separate checks.

​

Duplicate prevention

Feeds frequently repeat recent items, change ordering or update an existing entry. Use stable source identity and content commitments to prevent accidental duplicate Capsules. A useful deduplication key can combine verified feed identity, canonical source URI and the feed item’s stable identifier. The exact policy should remain deterministic and versioned.

​

Updates versus new publications

An updated RSS item is not automatically a new Capsule. If it refers to the same canonical article and content changed materially, route the change through the applicable revision policy. This preserves publication history instead of creating several unrelated Capsules for one evolving story.

​

Media handling

Feed images can seed Capsule cover metadata, but fetch and verify the actual media bytes before treating a remote image as canonical. Preserve a durable media URI and content hash where the metadata schema supports it.

​

Harden before mainnet

Feed Intelligence is explicitly part of the mainnet readiness gate. That means production launch should include robust duplicate handling, feed authority checks, replay protection, delegation review and failure recovery. An importer that works only while a single worker stays online is not launch-ready infrastructure.