Weekly brief
Orchard: design review is ready.
Fieldwork: kickoff is booked.
Open question: Who approves the final copy?
Keep the software
your agent builds.
Turn a useful one-off into a package you own. Run it again, change it, or give someone access to the work.
Illustrative package workbench
◇ weekly-briefPublished
Collect the project updates I choose and turn them into a weekly brief.
Current published codeTry a source change ↓
Change the source.
Choose when it runs.
Your package has a repo. Your agent can edit the source and check the result. Publishing makes that change the code your package runs.
Example package. The published brief has no open questions.
How packages are built ↗Weekly brief
Orchard: design review is ready.
Fieldwork: kickoff is booked.
Open question: Who approves the final copy?
Share the work.
Or hand over a copy.
Give someone access to one live package. Fork a public package when they should own and change their own copy.
Package sharing and access ↗Start with work you already repeat.
Keep a reporting tool, a recurring check, or a small app as software you can use again.