E6 · A real routine
20 minTurn one of the tasks from E1 into a standing request in AGENTS.md. Use it for a week and take notes in the table.
Done when: you used it 5 days in a row and noted what to improve.
Lesson 8 · 15 min
A real routine and Jarvis up and running
An assistant you don’t use is no use. In this lesson, you turn a weekly task into a standing request, use it five days in a row, and note what to improve. Then you see the steps to keep it running: on your computer, with automatic restarts, and on a rented server, up 24/7.
Start lesson
In this lesson, you will
- 1Turn a task into a standing request
- 2The weekly improvement cycle
- 3Laptop, automatic restart, or server
- 4The task list that gets you to step 3
Goal: use a standing request for five days in a row and choose where the assistant will run, from your laptop to a 24/7 server.
01Where your Jarvis lives
Four steps, from testing to 24/7. Click each one.
Click each block in the diagram to see what it does.
One at a time: Telegram, then automatic restart, then server. Move to each step only when the previous one is stable.
02The routine and improvement
Click each step.
1. Choose the task
Choose one of the three things it should do every week, from the plan in lesson 2.
Pick one thing you’d do anyway. That’s how you build a week of use.
Example
Start the day with your top three priorities.
2. Make it a standing request
Write the request in AGENTS.md: when you send a short word, it does the task the same way each time.
Scheduling it to run on its own (without you asking) is planned for the next phase. For now, you trigger it.
Standing request
Every morning, when I send "day," list my top three priorities based on what I told you yesterday.
3. Use it for 5 days
Use it for five days in a row. Write one line each day: what worked and what was missing.
Got the tone wrong? SOUL. Forgot something? Memory. Did something it shouldn’t? AGENTS.
Note
Day 3: listed 5 priorities instead of 3. Update AGENTS.
4. Weekly cycle
Once a week, review your notes and the log, then change just one thing. Run the tests again.
There’s no ready-made assistant. There’s one that gets better with real use.
Rule
One change a week, with tests passing before and after.
03Routine templates
Copy these into your AGENTS.md and meu-jarvis.md.
workspace/AGENTS.md · standing request
## Standing requests - When I send "day": list my top three priorities based on what I told you yesterday. No more than three, in short bullet points. - When I send "end": ask what I finished today and save it to memory.
rotina-5-dias.md
# Routine: "day" | Day | Worked | Missing / wrong | File to change | |-----|--------|-----------------|----------------| | 1 | | | | | 2 | | | | | 3 | | | | | 4 | | | | | 5 | | | | Change for the week:
meu-jarvis.md · extra challenge
## Tasks I’d like to send and then go to bed 1. 2. 3. 4. 5. (This list is the starting point for step 3: queues.)
Simulation: illustrative example
You: day
Jarvis:
- Finish the sales report (it’s Monday).
- Reply to the client about the timeline.
- Prepare the agenda for Thursday’s meeting.
The three come from what you told it yesterday and from memory.
- Week 1: the core running on your main channel.
- Week 2: memory really saving things and one or two tools.
- Week 3: always on (automatic restart or a server).
- Week 4: your first round of improvements based on the log and notes.
04Practice: a week of use
Exercise E6 and the extra challenge from sequence 2.
E6b · One change
15 minChoose one row in the table, change just one file, and run the tests.
Done when: the tests pass and, the next day, the noted problem doesn’t happen again.
Challenge · The list for bedtime
10 minIn meu-jarvis.md, write down the tasks you’d like to send and then go to bed.
Done when: the list has at least five specific tasks. It’s the starting point for step 3.
05Step 2 in video
A recap of the sequence: INTELECTO on Telegram, with memory and personality.
Create your Jarvis · 1 min 33 secVideo page with script →
06Test what you learned
The explanation appears after your answer.
Question 1 of 3
What makes a good standing request?competency
Correct
There’s a trigger (the word), a task, a limit (three), and a source (what you told it). You can check whether it did the job right.Not this one
There’s a trigger (the word), a task, a limit (three), and a source (what you told it). You can check whether it did the job right.Review: The routine and improvementQuestion 2 of 3
You close your laptop, and the assistant stops responding. What fixes that?
Correct
On your laptop, it sleeps when you do. On a server, it stays on day and night; Docker is the recommended way to package it for a server.Not this one
On your laptop, it sleeps when you do. On a server, it stays on day and night; Docker is the recommended way to package it for a server.Review: Where your Jarvis livesQuestion 3 of 3
On day 3, it listed five priorities instead of three. Where should you adjust that?
Correct
It’s a work rule, so it belongs in AGENTS.md. Make one change, test again, and check the next day.Not this one
It’s a work rule, so it belongs in AGENTS.md. Make one change, test again, and check the next day.Review: Routine templatesTest complete
You got {a} out of {n} right. Get them all right to mark the lesson as complete.Choose an option. The explanation appears after your attempt.
07Step 2 in four sentences
Seven piecesChannel, loop with a brake, identity, brain, memory, tools, and vault. Once you understand the pieces, you can choose better and make changes without fear.
It’s yours in the filesSOUL, AGENTS, USER, and MEMORY are text. Change the text, and you change the assistant.
You decide, the agent buildsBrief + plan + request with tests. The test confirms it works; the promise doesn’t.
Real useOne owner, limits in the vault, one fixed request for a week, and one improvement at a time.