one cron per playbook -> Core Gate -> API Gateway -> producer -> SQS -> consumer -> DynamoDB -> card
Guided views
Explore this system
Step through curated paths without changing the source diagram.
Beat
Next
ReadyChapter 01 / 01
Guided chapter
Diagram guideExplore this system
Inspecting compiled semantics
E ExportT ThemeS Style0 Reset+ Zoom in- Zoom outEsc Close
Find a node
⌕/
No matching nodes
Semantic passport
Verified source
Authored reach
Route probeChoose a start node
Pick two semantic nodes on the diagram
Choose the source, then the destination. Direction matters.
Semantic lensCompare system roles
Choose up to two semantic kinds. One reveals its real traffic; two compare only direct authored relationships.
Choose a kind to inspect its nodes and touching relationships.
Semantic radar
Building overview
Click nodeDrag to pan
Main flow
• One cron per playbook fires the n8n Schedule Trigger on a UTC clock
• Core Gate builds context, runs its checks, then POSTs to /generate with a Bearer HOOK_SECRET
• task_producer enqueues on SQS; task_consumer drafts and writes the task item to DynamoDB
Two doors in
• The n8n Core Gate is the intended front door for each playbook
• Auto Tasks (legacy) still posts directly to /generate twice a day
• Both doors land on the same API, so watch for double-gen
Terminal states
• The card in /tasks-v2 shows pending · needs · held · suppressed
• held reflects a Governor HOLD; suppressed is the DEV-947 drop
• Gabrielle reads Airtable SSOT, HubSpot and the real Gmail thread before Bedrock drafts
Data-flow diagram • Built with Archify • Create yours ↗ • Hover to trace • R route • Click to focus • +/− zoom • M radar • [/] views • P play story • T theme • E export