coulomb/freedom-intelligence
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
freedom-intelligence/docs/recurrence-ops.md

102 lines
3 KiB
Markdown
Raw Normal View History

Align FI recurrence with activity-core + rein-aharness (drop workstation cron). Document the three-layer model, add railiance-rhythm executor install, and point playbooks at rein-aharness fi-research-brief instead of local crontab.
2026-08-03 17:53:07 +02:00
# Freedom Intelligence daily brief — activity-core recurrence
Catch up field brief, catalog Kimi K3, and wire live daily recurrence. Add 2026-08-03 week catch-up brief with Kimi K3 as S1 strategic (collection deferred on ~1454 GiB vs 850 GiB soft quota), document recurrence ops, and add a workstation due-notice consumer cron helper. Production schedule was applied to railiance ConfigMap and Temporal (weekdays 07:30 Europe/Berlin).
2026-08-03 17:37:53 +02:00
Align FI recurrence with activity-core + rein-aharness (drop workstation cron). Document the three-layer model, add railiance-rhythm executor install, and point playbooks at rein-aharness fi-research-brief instead of local crontab.
2026-08-03 17:53:07 +02:00
**Status:** activity-core schedule live; rein-aharness executor on Railiance
**Do not** use workstation crontab as the primary path (retired anti-pattern).
Canonical org playbook: `activity-core/docs/recurring-automations-playbook.md`.
Catch up field brief, catalog Kimi K3, and wire live daily recurrence. Add 2026-08-03 week catch-up brief with Kimi K3 as S1 strategic (collection deferred on ~1454 GiB vs 850 GiB soft quota), document recurrence ops, and add a workstation due-notice consumer cron helper. Production schedule was applied to railiance ConfigMap and Temporal (weekdays 07:30 Europe/Berlin).
2026-08-03 17:37:53 +02:00
---
Align FI recurrence with activity-core + rein-aharness (drop workstation cron). Document the three-layer model, add railiance-rhythm executor install, and point playbooks at rein-aharness fi-research-brief instead of local crontab.
2026-08-03 17:53:07 +02:00
## Design (correct layers)
Catch up field brief, catalog Kimi K3, and wire live daily recurrence. Add 2026-08-03 week catch-up brief with Kimi K3 as S1 strategic (collection deferred on ~1454 GiB vs 850 GiB soft quota), document recurrence ops, and add a workstation due-notice consumer cron helper. Production schedule was applied to railiance ConfigMap and Temporal (weekdays 07:30 Europe/Berlin).
2026-08-03 17:37:53 +02:00
```text
Align FI recurrence with activity-core + rein-aharness (drop workstation cron). Document the three-layer model, add railiance-rhythm executor install, and point playbooks at rein-aharness fi-research-brief instead of local crontab.
2026-08-03 17:53:07 +02:00
activity-core (when / what / where)
Temporal: weekdays 07:30 Europe/Berlin
context: fi_brief_status → due?
rule: emit activity_task_spawn target_repo=freedom-intelligence
│
▼
rein-aharness on railiance01 (does the work)
host timer 07:35 → fi-research-brief
llm-connect drafts brief → commit → fi_daily_brief
│
▼
freedom-intelligence repo
briefs/YYYY/MM/YYYY-MM-DD.md
catalog / RESERVE-STATUS updates as needed
Catch up field brief, catalog Kimi K3, and wire live daily recurrence. Add 2026-08-03 week catch-up brief with Kimi K3 as S1 strategic (collection deferred on ~1454 GiB vs 850 GiB soft quota), document recurrence ops, and add a workstation due-notice consumer cron helper. Production schedule was applied to railiance ConfigMap and Temporal (weekdays 07:30 Europe/Berlin).
2026-08-03 17:37:53 +02:00
```
Align FI recurrence with activity-core + rein-aharness (drop workstation cron). Document the three-layer model, add railiance-rhythm executor install, and point playbooks at rein-aharness fi-research-brief instead of local crontab.
2026-08-03 17:53:07 +02:00
| Piece | Location |
| ----- | -------- |
| Definition (source of truth) | `activity-definitions/fi-daily-research-brief.md` |
| Cluster projection | ConfigMap `actcore-external-activity-definitions` |
| GitOps CM copy | `activity-core/k8s/railiance/20-runtime.yaml` |
Catch up field brief, catalog Kimi K3, and wire live daily recurrence. Add 2026-08-03 week catch-up brief with Kimi K3 as S1 strategic (collection deferred on ~1454 GiB vs 850 GiB soft quota), document recurrence ops, and add a workstation due-notice consumer cron helper. Production schedule was applied to railiance ConfigMap and Temporal (weekdays 07:30 Europe/Berlin).
2026-08-03 17:37:53 +02:00
| Resolver | activity-core `fi_brief_status` |
| Sink | `ISSUE_SINK_TYPE=state-hub` → `activity_task_spawn` |
Align FI recurrence with activity-core + rein-aharness (drop workstation cron). Document the three-layer model, add railiance-rhythm executor install, and point playbooks at rein-aharness fi-research-brief instead of local crontab.
2026-08-03 17:53:07 +02:00
| Executor | `rein-aharness fi-research-brief` |
| Host timer | `scripts/railiance-rhythm/` (interim until spawn poller) |
Catch up field brief, catalog Kimi K3, and wire live daily recurrence. Add 2026-08-03 week catch-up brief with Kimi K3 as S1 strategic (collection deferred on ~1454 GiB vs 850 GiB soft quota), document recurrence ops, and add a workstation due-notice consumer cron helper. Production schedule was applied to railiance ConfigMap and Temporal (weekdays 07:30 Europe/Berlin).
2026-08-03 17:37:53 +02:00
---
Align FI recurrence with activity-core + rein-aharness (drop workstation cron). Document the three-layer model, add railiance-rhythm executor install, and point playbooks at rein-aharness fi-research-brief instead of local crontab.
2026-08-03 17:53:07 +02:00
## Verify activity-core (organizer)
Catch up field brief, catalog Kimi K3, and wire live daily recurrence. Add 2026-08-03 week catch-up brief with Kimi K3 as S1 strategic (collection deferred on ~1454 GiB vs 850 GiB soft quota), document recurrence ops, and add a workstation due-notice consumer cron helper. Production schedule was applied to railiance ConfigMap and Temporal (weekdays 07:30 Europe/Berlin).
2026-08-03 17:37:53 +02:00
```bash
Align FI recurrence with activity-core + rein-aharness (drop workstation cron). Document the three-layer model, add railiance-rhythm executor install, and point playbooks at rein-aharness fi-research-brief instead of local crontab.
2026-08-03 17:53:07 +02:00
# Definition enabled
kubectl -n activity-core exec deploy/actcore-api -- python3 -c \
'import urllib.request,json; d=json.loads(urllib.request.urlopen(
"http://localhost:8010/activity-definitions/").read());
print([x for x in d if "Freedom Intelligence" in (x.get("name") or "")])'
# Schedule (example id — re-check after re-sync)
# activity-schedule-3169ab1f-882b-59c7-9763-d014dc96f4fc
# paused=False, 07:30 Mon–Fri Europe/Berlin
# Ops UI: activity.coulomb.social → automations
# Manual fire: POST /activity-definitions/<id>/trigger
Catch up field brief, catalog Kimi K3, and wire live daily recurrence. Add 2026-08-03 week catch-up brief with Kimi K3 as S1 strategic (collection deferred on ~1454 GiB vs 850 GiB soft quota), document recurrence ops, and add a workstation due-notice consumer cron helper. Production schedule was applied to railiance ConfigMap and Temporal (weekdays 07:30 Europe/Berlin).
2026-08-03 17:37:53 +02:00
```
Align FI recurrence with activity-core + rein-aharness (drop workstation cron). Document the three-layer model, add railiance-rhythm executor install, and point playbooks at rein-aharness fi-research-brief instead of local crontab.
2026-08-03 17:53:07 +02:00
After definition edits:
Catch up field brief, catalog Kimi K3, and wire live daily recurrence. Add 2026-08-03 week catch-up brief with Kimi K3 as S1 strategic (collection deferred on ~1454 GiB vs 850 GiB soft quota), document recurrence ops, and add a workstation due-notice consumer cron helper. Production schedule was applied to railiance ConfigMap and Temporal (weekdays 07:30 Europe/Berlin).
2026-08-03 17:37:53 +02:00
Align FI recurrence with activity-core + rein-aharness (drop workstation cron). Document the three-layer model, add railiance-rhythm executor install, and point playbooks at rein-aharness fi-research-brief instead of local crontab.
2026-08-03 17:53:07 +02:00
1. Update ConfigMap key from this repo’s definition file
2. Wait for volume refresh
3. `POST /admin/sync?definitions=true&schedules=true`
Catch up field brief, catalog Kimi K3, and wire live daily recurrence. Add 2026-08-03 week catch-up brief with Kimi K3 as S1 strategic (collection deferred on ~1454 GiB vs 850 GiB soft quota), document recurrence ops, and add a workstation due-notice consumer cron helper. Production schedule was applied to railiance ConfigMap and Temporal (weekdays 07:30 Europe/Berlin).
2026-08-03 17:37:53 +02:00
---
Align FI recurrence with activity-core + rein-aharness (drop workstation cron). Document the three-layer model, add railiance-rhythm executor install, and point playbooks at rein-aharness fi-research-brief instead of local crontab.
2026-08-03 17:53:07 +02:00
## Install executor on railiance01
Catch up field brief, catalog Kimi K3, and wire live daily recurrence. Add 2026-08-03 week catch-up brief with Kimi K3 as S1 strategic (collection deferred on ~1454 GiB vs 850 GiB soft quota), document recurrence ops, and add a workstation due-notice consumer cron helper. Production schedule was applied to railiance ConfigMap and Temporal (weekdays 07:30 Europe/Berlin).
2026-08-03 17:37:53 +02:00
```bash
Align FI recurrence with activity-core + rein-aharness (drop workstation cron). Document the three-layer model, add railiance-rhythm executor install, and point playbooks at rein-aharness fi-research-brief instead of local crontab.
2026-08-03 17:53:07 +02:00
# On railiance01
git clone forgejo-remote:coulomb/freedom-intelligence.git ~/freedom-intelligence
cd ~/freedom-intelligence && ./scripts/railiance-rhythm/install-on-railiance.sh
Catch up field brief, catalog Kimi K3, and wire live daily recurrence. Add 2026-08-03 week catch-up brief with Kimi K3 as S1 strategic (collection deferred on ~1454 GiB vs 850 GiB soft quota), document recurrence ops, and add a workstation due-notice consumer cron helper. Production schedule was applied to railiance ConfigMap and Temporal (weekdays 07:30 Europe/Berlin).
2026-08-03 17:37:53 +02:00
Align FI recurrence with activity-core + rein-aharness (drop workstation cron). Document the three-layer model, add railiance-rhythm executor install, and point playbooks at rein-aharness fi-research-brief instead of local crontab.
2026-08-03 17:53:07 +02:00
# rein-aharness must expose fi-research-brief (deploy/pull rein-aharness)
# Logs: ~/.cache/freedom-intelligence/rhythm/
```
Catch up field brief, catalog Kimi K3, and wire live daily recurrence. Add 2026-08-03 week catch-up brief with Kimi K3 as S1 strategic (collection deferred on ~1454 GiB vs 850 GiB soft quota), document recurrence ops, and add a workstation due-notice consumer cron helper. Production schedule was applied to railiance ConfigMap and Temporal (weekdays 07:30 Europe/Berlin).
2026-08-03 17:37:53 +02:00
Align FI recurrence with activity-core + rein-aharness (drop workstation cron). Document the three-layer model, add railiance-rhythm executor install, and point playbooks at rein-aharness fi-research-brief instead of local crontab.
2026-08-03 17:53:07 +02:00
Timer is **07:35** Berlin — five minutes after activity-core’s 07:30 schedule.
Catch up field brief, catalog Kimi K3, and wire live daily recurrence. Add 2026-08-03 week catch-up brief with Kimi K3 as S1 strategic (collection deferred on ~1454 GiB vs 850 GiB soft quota), document recurrence ops, and add a workstation due-notice consumer cron helper. Production schedule was applied to railiance ConfigMap and Temporal (weekdays 07:30 Europe/Berlin).
2026-08-03 17:37:53 +02:00
---
Align FI recurrence with activity-core + rein-aharness (drop workstation cron). Document the three-layer model, add railiance-rhythm executor install, and point playbooks at rein-aharness fi-research-brief instead of local crontab.
2026-08-03 17:53:07 +02:00
## Completion event (required for due=false)
Catch up field brief, catalog Kimi K3, and wire live daily recurrence. Add 2026-08-03 week catch-up brief with Kimi K3 as S1 strategic (collection deferred on ~1454 GiB vs 850 GiB soft quota), document recurrence ops, and add a workstation due-notice consumer cron helper. Production schedule was applied to railiance ConfigMap and Temporal (weekdays 07:30 Europe/Berlin).
2026-08-03 17:37:53 +02:00
```yaml
event_type: fi_daily_brief
detail:
repo: freedom-intelligence
date: "YYYY-MM-DD"
path: "briefs/YYYY/MM/YYYY-MM-DD.md"
collection_candidates: <int>
```
Align FI recurrence with activity-core + rein-aharness (drop workstation cron). Document the three-layer model, add railiance-rhythm executor install, and point playbooks at rein-aharness fi-research-brief instead of local crontab.
2026-08-03 17:53:07 +02:00
Posted automatically by `rein-aharness fi-research-brief` on success.
---
## What not to do
- Workstation `crontab` that writes the brief (bypasses activity-core)
- Installing Claude Code / Codex on railiance01 for this rhythm
- Treating host timers as the scheduler of record
- Skipping the completion event (leaves `due=true` forever)
Reference in a new issue Copy permalink