Ten points — every hour and every close

Janhavi, 24 Aug 2026 22:17 Europe/London. Exact instruction. Evidence, not language.

From now on, every hour and every close must answer these ten points with evidence, not language.

Name the exact founder layer being released today in one plain sentence. If nothing has left my hands, write “None” and stop. Do not invent a layer.
Run a hindsight only if it produces a different task list for the next day. If the hindsight does not change tomorrow’s work, delete it.
The hindsight must set the actual Current slot for the next day. If the slot stays the same, the hindsight failed.
By the next close, show the timestamped result of what was produced because of that new slot. No result = the chain broke.
Show one complete chain in the files:
Constraint → Action taken → Measurable release (or “none”) → Next constraint that appeared because of it.
If any link is missing, the chain does not exist.
Every real change must carry a timestamp that links it to the previous change. Hour-log rows that only say “sync” do not count.
There must be one place that states what is actually being improved right now (not “site matches files”). Update that place when the work changes.
Prove understanding by doing, not by explaining. If the agent can only write the rules correctly, it has not understood the process.
Movement must be checkable without reading the prose. If I cannot see progress from the slot line and the score alone, it is not progress.
The Current slot is only allowed to stay the same when a layer has genuinely been released. Otherwise rewrite it.

Anything that does not move one of these ten points is maintenance, not founder work. Treat it as such.

One place for (7): the Current slot line in hour-slots.md.
Chain file: /home/box/agents/fyj-founder-bot/activity/chain.md

# Ten points — every hour and every close Janhavi, 24 Aug 2026 22:17 Europe/London. Exact instruction. Evidence, not language. From now on, every hour and every close must answer these ten points with evidence, not language. 1. Name the exact founder layer being released today in one plain sentence. If nothing has left my hands, write “None” and stop. Do not invent a layer. 2. Run a hindsight only if it produces a different task list for the next day. If the hindsight does not change tomorrow’s work, delete it. 3. The hindsight must set the actual Current slot for the next day. If the slot stays the same, the hindsight failed. 4. By the next close, show the timestamped result of what was produced because of that new slot. No result = the chain broke. 5. Show one complete chain in the files: Constraint → Action taken → Measurable release (or “none”) → Next constraint that appeared because of it. If any link is missing, the chain does not exist. 6. Every real change must carry a timestamp that links it to the previous change. Hour-log rows that only say “sync” do not count. 7. There must be one place that states what is actually being improved right now (not “site matches files”). Update that place when the work changes. 8. Prove understanding by doing, not by explaining. If the agent can only write the rules correctly, it has not understood the process. 9. Movement must be checkable without reading the prose. If I cannot see progress from the slot line and the score alone, it is not progress. 10. The Current slot is only allowed to stay the same when a layer has genuinely been released. Otherwise rewrite it. Anything that does not move one of these ten points is maintenance, not founder work. Treat it as such. One place for (7): the Current slot line in hour-slots.md. Chain file: /home/box/agents/fyj-founder-bot/activity/chain.md