← Project archive
SYS-08 / Automation · continuous learning

Daily Learning Mission

Turn continuous-learning goals into grounded weekly missions without repeating topics, duplicating deliveries or relying on opaque model decisions.

STATUSSource published; E2E pending
ROLEn8n workflows, integrations, tests and security
FLOW / SYS-08
  1. 01Agenda
  2. 02Histórico
  3. 03Pesquisa
  4. 04Grounding
  5. 05Plano
  6. 06Telegram
  7. 07Feedback
EXECUTIVE SUMMARY

An n8n automation that researches real sources with SerpAPI, uses Groq for structured synthesis, accounts for Google Calendar holidays, persists plans in Data Tables and delivers missions through Telegram. Deterministic rules control idempotency, grounding, dates, states and feedback.

  • n8n
  • JavaScript
  • Groq
  • SerpAPI
  • Google Calendar
  • Telegram
  • Docker
SYS-08.01

Context and problem #

Daily learning requires choosing useful topics, finding trustworthy sources, fitting activities into a schedule and preserving history. The project automates that cycle without delegating critical rules to the model.

SYS-08.02

My contribution #

The repository combines data modelling, deterministic generation of four n8n workflows, reusable JavaScript logic, OAuth and HTTP integrations, tests, operational documentation and secret scanning.

SYS-08.03

Architecture #

The weekly planner researches and validates sources before materializing topics and missions. A daily workflow delivers the eligible mission; another resolves callbacks and updates only the addressed item. Five Data Tables store categories, topics, plans, missions and destinations.

  • ✓ 4 workflows / 149 nodes
  • ✓ 5 Data Tables / 48 fields
  • ✓ Grounding by exact source URL
  • ✓ Idempotent state transitions
SYS-08.04

Evaluation and quality #

The suite records 25 functional tests and 1,021 structural and security checks. Groq, SerpAPI, Calendar and Telegram's /start command were validated against real services.

SYS-08.05

Limitations #

The corrected Planner still needs a real end-to-end retest, followed by the Dispatcher and a mission callback. Production schedules therefore remain inactive.

SYS-08.06

Next steps #

Reimport the corrected exports, prove idempotency across two runs, validate real delivery and feedback, and only then enable schedules.