πΊοΈ The workflow map: Crypto L2 Daily
flowchart LR
A["β° Input: 6 PM, X posts from the last 24 hours"] --> B["π 1 Β· Collect the posts"]
B --> C["π§Ή 2 Β· Check the posts, remove junk"]
C --> D["π¬ 3 Β· Make the 70-second video"]
D --> E{"π§ββοΈ 4 Β· Human check (first video only)"}
E -->|yes| F["π 5 Β· Put it on the website"]
E -->|no| C
F --> G["β
Output: video + cards + course + archive note"]
π’ The same map in words
- β° Input: at 6 PM, the robot gets X posts from the last 24 hours.
- π Step 1: collect the posts.
- π§Ή Step 2: check the posts. Remove the junk.
- π¬ Step 3: make the 70-second video.
- π§ββοΈ Step 4: I check it. Yes β go to step 5. No β go back to step 2.
- π Step 5: put it on the website.
- β Output: the video, the cards, the course pages and the archive note.
π§© Open the canvas
process-map.canvas shows the same 5 steps in the same order. Open it in Obsidian.
Approval interpretation
Step 4 is an operator gate when human_approval_default is true. When the switch is false, standing approval permits the daily run to continue. The rejection arrow represents the operator's repair and rerun action, not an automatic retry loop.