Week 3 · new connections

She keeps every rule from week 2. What we added:

• The list of owners (config/owners.json). Now she also writes the text for the owner's deck: three headlines and the email. A script turns it into slides, and a person sends the email.
• Her schedule, as routines: the report at 6:07, the insights at 7:07, the deck at 8:07 and the rate review. In this test we started her by hand.
• Stricter rules, enforced in code: she never opens the raw export (only the scripts read it, so guest data never reaches her), and she never deletes or moves a file.
• A parser agent that only reads the export, with a small and cheap model.

What she did: the report and the insights pass the check, and every number matches the reference. She wrote the owner's deck text, and she warned that Sunday's 85% has to be confirmed in OPERA before the owner sees it. She also saw three old exports in the folder and left them alone.

What is still missing: the deck text has no check yet, and she said so. That is our next step.

Cost of this run: about 0.90 dollars.