story:event
story family
One step of a story's life, written as a signal under its origin: told · framed · view · complete · share · convert · retell. The payload carries the block-4 event convention (schema/story.tql), so story_views / story_conversions / story_revenue / story_retells / story_teller start answering from real traffic instead of 0. A convert also marks the two craft trails — tag:<board>:story → tag:<board>:frame:<x> and → tag:<board>:medium:<x> — and a retell marks teller → reteller, the referral edge. told/convert/retell need an attested caller; view/complete/share may be anonymous and are deduped per (origin, viewer, event) for an hour
- Effect
- signal
- Fire-and-forget — the call returns once accepted, not once done.
- Caller
- public
- The class of authority the caller must already hold, decided from the attested context with no round trip.
- Cost
- free
- What one call costs, so you can budget before acting.
- Reversible
- no
- This cannot be undone. Dry-run it first where the contract allows.
- Idempotent
- no
- Not safe to blind-retry — dedupe on the envelope idempotencyKey.