{
  "edition": {
    "edition": "2026-09-06-draft-01",
    "language": "en",
    "publicationState": "published",
    "sourceRevision": "a7e788eb4b151fd92c1f58153e015773e3a829af",
    "projectCount": 67,
    "documentCount": 94,
    "skillCount": 10,
    "archivePath": "library.zip",
    "archiveBytes": 181812,
    "releasedAt": "2026-09-08T05:03:11.129+00:00"
  },
  "access": {
    "released": true,
    "rehearsal": false
  },
  "project": "background-services/event-follow-up.md",
  "markdown": "https://legion.tw/api/projects/packet.md/background-services/event-follow-up.md?edition=2026-09-06-draft-01",
  "documents": [
    {
      "path": "background-services/README.md",
      "text": "# Background automation and services\n\n[All project types](../README.md) · [Shared launch](../shared/launch.md)\n\nGive recurring work a dependable trigger, an understandable result, and a way for the person to inspect or control it.\n\n## Projects to build\n\n- [Watched-folder preparation](watched-folder.md)\n- [Recoverable backups](recoverable-backups.md)\n- [Meaningful change monitoring](change-monitor.md)\n- [Prepare tomorrow's information](tomorrow-briefing.md)\n- [Event-triggered follow-up administration](event-follow-up.md)\n- [Give the computer a batch of work](batch-work-queue.md)\n- [A personal overnight researcher](overnight-researcher.md)\n\nThese are instructions for projects you can build with your coding agent.\n"
    },
    {
      "path": "background-services/event-follow-up.md",
      "text": "# Handle the paperwork after the work is done\n\nBuild an automation that performs the recurring administration following a meaningful event in the person's work. Build it extremely well around a routine they already understand. Follow the [shared launch](../shared/launch.md).\n\nChoose one complete follow-up with the person: prepare records after a club session, assemble the supplier order after a [group order](../shared-web/group-order.md) closes, or prepare the delivery material for a completed [report](../desktop/ai-photo-report-desk.md). Use the existing application and its actual records.\n\n## Learn what starts the follow-up\n\nAsk the person to show what they do when this part of the job finishes. Learn what information is ready, what still needs judgment, and what the follow-up produces.\n\nGive the trigger a clear meaning in that workflow. A session's scheduled end, confirmed attendance, and completion of its administration are different events. Start the routine from the state that actually supplies the information it needs.\n\nUse the source application's own record of that event. Keep the follow-up associated with the session, order, or job it belongs to, so the person can see why it ran and find its result from the work itself.\n\n## Complete the usual administration\n\nPrepare the records, lists, or delivery material the person normally creates. Use actual recorded information and preserve the distinctions needed for the next activity. A supplier needs item quantities; the organizer may also need each person's collection details.\n\nKeep reusable instructions or layouts separate from the current event's information. Apply the existing formatting and preparation rules where the person already has a working routine.\n\nAgree which actions run automatically and which prepare material for the person to inspect or send. For an authorized automatic delivery, use the agreed recipients and communication method and show its outcome. For preparation-only work, leave the result clearly ready for the person's next action.\n\n## Let the person understand what happened\n\nShow the originating event, the follow-up's current state, and its completed result. Make a missing input or failed action visible with enough context to resolve it. Let the person retry or invoke the routine manually when useful.\n\nRecognize an event that has already been handled so a repeated signal or retry preserves the completed work and any delivery already made. If the underlying event is corrected afterward, make the revised follow-up an explicit update with the earlier result still understandable.\n\nKeep the person's direct edits to prepared material intact according to the workflow you establish together. Give them a clear choice when refreshing a result would affect those edits.\n\n## Run it from the real application\n\nInstall the automation where the work actually runs and explain its availability, startup, and external service requirements. Give the person a way to inspect, pause, or stop the routine. Keep its setup and useful history under the shared launch's ownership and recovery guidance.\n\nDeliver the complete follow-up and exercise it from a representative event in the source application. Inspect the generated result, handle a correction, and confirm that repeating the event does the right thing with existing output. Where delivery is authorized, verify the chosen delivery result.\n\nJudge whether the person can finish the original job and find the administration ready in the form they need. Explain how a recorded change in work can start another useful action.\n\nLater, add another follow-up routine with its own trigger and authority. Preserve the existing routine as new actions are added.\n"
    },
    {
      "path": "shared-web/group-order.md",
      "text": "# Build a group-order app\n\nBuild a shared web application where people enter their own choices for a group order and the organizer gets a clear combined result. Build it extremely well for the group's actual routine. Follow the [shared launch](../shared/launch.md).\n\nUse an ordinary link on participants' phones and computers, with suitable free cloud hosting where available. Explain current hosting limits and keep the account and records under the builder's ownership. The group should be able to use it while that person's computer is off.\n\n## Make it easy to choose\n\nLearn what the group orders: workplace lunch, club supplies, or a bulk purchase among friends. Use the menu or item list the organizer supplies, including current prices and the choices relevant to that order.\n\nLet each person select items and quantities, specify available options, and leave a relevant note. Show their total and make it clear when their choice has been saved. They can return and change it while the order is open.\n\nKeep variations meaningful in the combined result. Two lunches with different options may share a base item but need separate preparation. The organizer should be able to see both the quantities to order and what belongs to each person.\n\nIf the group shares fees or discounts, use the arrangement they agree on and show its effect on individual totals. Preserve the price and options used for this order when the menu changes for a later one.\n\n## Close an order clearly\n\nGive the organizer a clear deadline and control of when the order closes. Show participants whether they can still change their choices. Handle a last-minute submission and closure so the person receives an accurate answer about whether their change was included.\n\nProduce a consolidated order in a form the organizer can use with the supplier, together with a per-person breakdown. Let them copy, export, or print the information needed for their usual ordering method.\n\nDistinguish closing the group's choices from placing the order with the supplier. Keep the submitted order available as the record of what was requested. If a late correction or unavailable item changes it, make that amendment and its effect on the relevant person's order understandable.\n\n## Finish the group administration\n\nLet the organizer record payments received through the methods the group already uses. Show who has paid and what remains, keeping payment status distinct from an order's inclusion or delivery. Use the person's existing way of handling adjustments and refunds if these occur.\n\nProvide enough information to distribute the order correctly when it arrives. The organizer should be able to find a person's items and notes without rebuilding the list from messages.\n\nChoose a joining and identification method suited to the actual group. Explain who can edit a participant's choices and who can manage the combined order. Keep the current shared information consistent when people return from different devices.\n\n## Run one order\n\nDeliver the hosted application and use separate participant sessions to enter choices, edit one, close the order, and inspect the combined result. Record a payment and an ordinary correction. Judge whether the organizer has what they need to place and distribute the order.\n\nExplain where the records live and provide a practical export and recovery path under the shared launch's ownership guidance. Keep any maintenance required by the chosen free hosting understandable.\n\nUse the experience to teach how individual choices become a shared commitment, and why an editable selection differs from an order already sent. Later projects can reuse menus for recurring orders or add pickup coordination while retaining the history of each completed round.\n"
    },
    {
      "path": "desktop/ai-photo-report-desk.md",
      "text": "# Build a photo-to-report desk with an AI colleague\n\nBuild a native desktop application with Tauri for turning photographs and field notes into reports. Build it extremely well, as a shared workplace where you and the person can organize the material, discuss what it shows, and prepare something useful to send. Tauri is the default; an explicit framework preference from the person takes precedence.\n\nRead this brief and follow the [shared launch](../shared/launch.md), which supplies setup, working skills, ownership, continuity, and learning guidance. Then build this project, carrying forward any setup the person already has.\n\n## Understand the report they actually make\n\nSomeone returns from a visit with photographs and observations. They need to identify the useful images, explain them, and assemble a report for a particular recipient. The work might involve documenting repairs, completed work, a property, or a delivery. Learn which reports the person makes and look at an example they choose to share. Use that understanding to shape the application.\n\nSomeone reading the report may need to understand a problem, confirm completed work, or decide what happens next. Let that purpose determine the arrangement of photographs and explanation. Start with a complete example report whose layout the person can change as they discover what works.\n\n## A place to work on the report\n\nPhotographs and notes belong to a job. The person can browse the images at useful sizes, compare similar shots, choose what to include, and arrange sections and captions in an editable report. Keep the original material available as the report develops. They can save their work, return to it, and export a readable document for the recipient in the format the job calls for.\n\nGive particular care to the movement between examining a photograph and working on its place in the report. The person should be able to see the relevant image while deciding what to say about it. The report's final layout should support the recipient's understanding of the work.\n\n## Work directly in the application\n\nBuild yourself first-class access to the job's photographs, notes, and current report, together with useful tools for operating them. Use your existing coding-agent installation, sign-in, and model access for this collaboration. They can discuss the work with you in their usual conversation and see your changes in the application.\n\nProvide an appropriate local integration, such as MCP tools, so you can compare images, group related material, draft captions, choose a useful sequence, and assemble the actual report in the editor. Make that connection part of the delivered application.\n\nMake the person's current job, report, and image selection available through that connection. A reference to “this photograph” should have the same meaning for both of you. Your changes should appear in their working view, and your next action should use the current report, including their direct edits.\n\nFor example, the person might say, “These three show the same damaged hinge. Use the clearest one and include my note about replacing it.” You inspect the images, select one, and make that change in the report. The person can then edit the caption themselves.\n\nTreat the photographs and field observations as the basis for factual descriptions. Keep visible evidence distinguishable from the person's explanation of what happened. Ask about a genuinely unclear image or suggest wording that accurately reflects the information available. Let ordinary discussion, direct editing, and your actions work together naturally, with useful ways to inspect and undo changes.\n\n## Make it theirs\n\nSet up Tauri and the agent connection for the person's computer. Make clear which material reaches the model provider during collaboration and which stays local. The person retains access to their photographs and reports independently of an AI session.\n\nWork in focused steps and carry the project through a real report-making experience. Judge image selection, captions, editing, and the exported report together. Help the person recognize what you can handle and where their knowledge of the visit changes the result.\n\nLeave them able to open the installed application, prepare a report with you, close it, and return to the saved job. Use that experience to explain the difference between discussing an application and giving an agent tools to work in it. Their next improvement can begin from the report they just made.\n\nA later phone companion could capture photographs with their job and notes already attached. Build a foundation that can receive that material while preserving the reports and working habits established here. This desktop application should be useful with the photographs the person already takes.\n"
    }
  ]
}