Repository navigation
Insight Contracts
The native Insight service combines content extraction, prompt selection, provider routing, quota accounting, cache identity, and delivery authorization.
About and summary require transcript content. TLDR supports configured aliases, wildcard domain bindings, focus, language, and user prompt overrides.
Cache identity includes the effective content, prompt, model, research mode, and private provider context. A cached result must not cross user or credential boundaries.
Current authority applies to cache reads as well as fresh requests.
Gateway/OpenRouter routing and personal provider settings have separate authority. A personal provider failure does not permit an undisclosed fallback to operator credentials.
Model catalogues are bounded remote data, not evidence of live completion success. Failed probes must not publish unverified replacement credentials.
Credential replacement uses revision checks. A slow probe cannot overwrite a newer credential or restore a revoked grant.
The streaming path consumes actual provider events with bounded input and awaited delivery. It checks cancellation and current authority during processing.
A cached response does not generate synthetic deltas. Buffered HTTP responses remain a separate contract.
Partial external delivery prevents fallback that could repeat content. Unknown send/edit effects stay uncertain until the durable ledger supplies valid recovery evidence.
Research must contain real citations. The source under review cannot serve as its own independent corroboration.
Failure to obtain citations is a research failure, not successful verification.
Device flows handle cancellation, expiry, generation replacement, slow polling, bounded responses, and post-I/O authority checks.
Inbox reuses the same authorized completion/content interfaces. It does not bypass personal provider restrictions or the shared shutdown lifecycle.
See runtime configuration, diagnostics, and focused contracts.
- Native backup and restore
- Configuration
- Deployment and rollback
- PostgreSQL data import
- Installation
- Image publication
- Local releases
- User-mode Telegram session
- YouTube services
- Downloads
- Downloader commands and compatibility
- Cookies and YouTube authentication
- Native deferred private media
- Download history and automatic proxy routing
- Native downloader inline lookup
- Native downloader NSFW policy
- Downloader settings
- Inbox
- Inbox content processing
- Inbox durability and compatibility
- Inbox runtime
- Inbox Telegram delivery
- Access control and identity
- HTTP API
- Frontend architecture
- Runtime architecture
- Persistence and recovery
- Native Music and Stats composition
- Worker protocol
- Documentation and Wiki
- Local GitHub CI
- Media acceptance fixtures
- Development and verification
- Worker development