docs/signals.md: how Signals work, with TypeSafe's requests and answers and the API

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-16 17:57:05 +00:00
parent 1ae91170fd
commit f8371f255d
2 changed files with 302 additions and 1 deletions
--- a/docs/architecture.md
+++ b/docs/architecture.md
@@ -101,7 +101,7 @@ signals        id, user_id, name, keywords
 signal_verdicts  signal_id, feed_id, guid, hit           PK (signal_id, feed_id, guid)
 ```

-A Signal (#254) is a feed someone makes from their own subscriptions. `signals::run`, a task of its
+A Signal (#254, [signals.md](signals.md)) is a feed someone makes from their own subscriptions. `signals::run`, a task of its
 own beside DeadAir's, woken by a scan with something new or a Signal made or changed, asks Jev
 about each item of the last 30 days that has no verdict yet for one of its owner's Signals: one
 call an item, a noul question a Signal, on the owner's `users.typesafe_key`. Every answer is kept,