Document the three-layer model, add railiance-rhythm executor install, and point playbooks at rein-aharness fi-research-brief instead of local crontab.
2.5 KiB
2.5 KiB
| id | name | enabled | owner | governance | status | trigger | context_sources | |||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| fi-daily-research-brief | Freedom Intelligence Daily Research Brief | true | custodian-agent | custodian | active |
|
|
Freedom Intelligence Daily Research Brief
Runs weekdays at 07:30 Berlin time. Emits one task when the daily research brief
for freedom-intelligence is due. Execution is out of band: consumer checks
out this repo and follows docs/daily-brief-playbook.md (axes A–D, collection
candidates, template under briefs/).
activity-core only schedules and spawns. It does not call model APIs for the brief body.
Baseline field memory: research/2026-07-24-baseline-field-survey.md. Daily
briefs are deltas from prior briefs + that baseline — not full resurveys.
id: emit-fi-daily-brief-task
for_each: context.fi_brief.items
bind_as: item
condition: 'context.item.due'
action:
task_template: "FI daily research brief ({context.item.kind}) for {context.item.date}"
description: >
Produce briefs/YYYY/MM/YYYY-MM-DD.md per docs/daily-brief-playbook.md and
briefs/_template.md. Cite primary sources. Flag collection candidates.
On completion post State Hub progress event_type=fi_daily_brief with
detail.repo=freedom-intelligence and detail.date.
target_repo: freedom-intelligence
priority: medium
labels: ["freedom-intelligence", "research-brief", "automated"]
Enable checklist
- Resolver
fi_brief_statusin activity-core - ConfigMap projection + Temporal schedule (weekdays 07:30 Europe/Berlin)
- Completion event
fi_daily_briefproven enabled: true/status: active- Executor:
rein-aharness fi-research-brief+scripts/railiance-rhythm/(install on railiance01; not workstation cron)
Layers: activity-core (when/what/where) → rein-aharness (execute) → this repo.
See docs/recurrence-ops.md and activity-core/docs/recurring-automations-playbook.md.