Define the star-discord-watch adapter and durable handoff contract #9

New issue

Open

opened 2026-08-03 07:48:06 +00:00 by lost-rob0t · 0 comments

lost-rob0t commented

2026-08-03 07:48:06 +00:00

(Migrated from github.com)

Depends on

Goal

Define the downstream adapter boundary without importing StarIntel policy into this repository.

Scope

document the account-session lifecycle contract
document typed dispatch-event delivery to the downstream actor
define checkpoint candidate handoff semantics
define cancellation behavior for expired scopes and revoked credential leases
define duplicate-event and deterministic-identifier expectations
provide fixture adapters or protocol mocks for downstream integration tests
link the corresponding star-discord-watch implementation issue when created

Constraints

this repository does not import RabbitMQ, CouchDB, StarIntel document packages, target authorization, dataset manifests, or publication code
Gateway sequence advancement is distinct from durable StarIntel cursor advancement
a successful socket write is never treated as durable downstream publication
duplicate replays must produce identical library event identifiers

Exit gate

downstream integration can be tested with fixtures and mocks
the adapter contract is versioned
credential revocation and scope cancellation have explicit terminal behavior
no downstream storage or policy dependency enters the library closure

## Depends on - #8 ## Goal Define the downstream adapter boundary without importing StarIntel policy into this repository. ## Scope - document the account-session lifecycle contract - document typed dispatch-event delivery to the downstream actor - define checkpoint candidate handoff semantics - define cancellation behavior for expired scopes and revoked credential leases - define duplicate-event and deterministic-identifier expectations - provide fixture adapters or protocol mocks for downstream integration tests - link the corresponding `star-discord-watch` implementation issue when created ## Constraints - this repository does not import RabbitMQ, CouchDB, StarIntel document packages, target authorization, dataset manifests, or publication code - Gateway sequence advancement is distinct from durable StarIntel cursor advancement - a successful socket write is never treated as durable downstream publication - duplicate replays must produce identical library event identifiers ## Exit gate - downstream integration can be tested with fixtures and mocks - the adapter contract is versioned - credential revocation and scope cancellation have explicit terminal behavior - no downstream storage or policy dependency enters the library closure