docs: decision 70, the host's boot config for S3 trackers (sage)

Co-Authored-By: Claude Opus 5.5 <[email protected]>
2026-10-08 17:31:45 -05:00
parent 020b2c17b3
commit d68aa20f27
1 changed files with 9 additions and 0 deletions
@@ -1350,3 +1350,12 @@ which stay with him. Each item names who decided it and what happened.
      exists, so S4 can build and test now. Its `after` becomes row 37
      alone. Its live run still follows S3's, because the task view is
      empty until S3's sync fills it.
    - Host and S3 interface (Darkwing, same day). S3 has no host of its
      own. Its poller and reconcile run inside the broker runtime. The
      host puts plain data in the boot config: `config.trackers`, keyed
      by business, with `baseUrl`, `project`, `pollSeconds` and
      `reconcileMinutes` taken from the business vars `tracker.*`. A
      business without an entry gets no task verbs. Startup runs S3's
      fail-closed Vikunja checks, about 15 requests, before the boot
      reply, so the host waits 30 s for `{ok: true}`. A refusal comes
      back as `{ok: false, error}`.