inbound-library/SCOPE.md
tegwick 2fcaa1aaeb Add INTENT, refine SCOPE and plan ILIB-WP-0002 infrastructure.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 1170398@bnt-lap001
Assistant-Session: 622cd705-cb31-4322-ba08-dd42e44fa583
2026-10-05 11:01:11 +02:00

38 lines
1.4 KiB
Markdown

# SCOPE
## One-liner
Keeps material delivered to the ecosystem and routes it by topic to the repositories that asked to see it.
## Core Idea
See INTENT.md. Email and registered sources go into an append-only, content-addressed
item store. File-backed registries of topics, sources and subscriptions decide
who is told about each item. Notices reach consumers as State Hub agent messages,
through a pull CLI, and in periodic digest files.
## In Scope
- Read-only IMAP intake from one dedicated mailbox.
- Items with original bytes, provenance and derived text; integrity checking.
- Registries of topics, sources (including sources contributed by consumers) and subscriptions.
- Matching, idempotent notices, pull access, digest files.
- Scheduling, health reporting and quarantine on the workstation, later in the cluster.
## Out of Scope
- Sending mail other than notices. email-connect owns email delivery and its evidence.
- Scraping signed-in websites, or any intake that breaks a provider's terms of service.
- Judging whether material is relevant or credible. Consumers review it.
- Replacing a consumer's own evidence store.
## Current State
- Status: inception. INTENT drafted 2026-10-05, no code yet.
- First consumer: intelligence-radar (Grok and ChatGPT daily and weekly briefs).
## Getting Oriented
- Start with: INTENT.md
- Agent instructions: AGENTS.md
- Workplans: workplans/