{
  "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": "desktop/booking-session-desk.md",
  "markdown": "https://legion.tw/api/projects/packet.md/desktop/booking-session-desk.md?edition=2026-09-06-draft-01",
  "documents": [
    {
      "path": "desktop/README.md",
      "text": "# Native desktop applications\n\n[All project types](../README.md) · [Shared launch](../shared/launch.md)\n\nBuild a native Tauri application around the person's work or interests. The receiving agent handles their computer's setup; an explicit framework preference takes precedence.\n\n## Projects to build\n\n- [Calling and follow-up desk](calling-follow-up-desk.md)\n- [Quote and estimate builder](quote-estimate-builder.md)\n- [Photo-to-report desk with an AI colleague](ai-photo-report-desk.md)\n- [Orders and production board](orders-production-board.md)\n- [Equipment checkout and maintenance book](equipment-checkout-book.md)\n- [Booking and session desk](booking-session-desk.md)\n- [Meme and GIF studio](meme-gif-studio.md)\n- [Soundboard](soundboard.md)\n- [Game-show host](game-show-host.md)\n- [Music playground](music-playground.md)\n- [Animated desktop pet](desktop-pet.md)\n- [Tabletop atmosphere controller](tabletop-atmosphere.md)\n- [Ridiculous tournament simulator](ridiculous-tournament.md)\n- [Personal AI chat app with bring-your-own-key access](byok-chat.md)\n\nThese are instructions for projects you can build with your coding agent.\n"
    },
    {
      "path": "desktop/booking-session-desk.md",
      "text": "# Build a booking and session desk\n\nBuild a native Tauri application that brings appointments, preparation, session notes, and payment records together. Build it extremely well around the person's actual sessions. Use another framework if they have an explicit preference, and follow the [shared launch](../shared/launch.md) for setup and working practice.\n\n## Start with what happens at the appointment\n\nFind out whom the person meets and what the meeting involves. A tutor prepares teaching material and follows a learner's progress. A repair technician needs the item's problem, access arrangements, parts, and work completed. Choose the person's real activity and give it an appropriate application.\n\nFor someone trying the project without an existing practice, use a private tutor as the example. The tutor should be able to open tomorrow's lesson, see what happened last time, prepare material, and know what to bring. After the lesson, they can record what the student understood and what deserves another look.\n\nLearn which people belong to the work. The student attending a lesson, the parent arranging it, and the person paying can be different people. Make those relationships clear when they matter to the actual practice.\n\n## Make preparation and notes useful\n\nGive appointments a calendar view and enough room for the work associated with them. Support substantial editable notes and relevant files or links. A tutor may want a full lesson plan, a passage to discuss, and notes about particular mistakes. Let them work with that material comfortably while preparing or teaching.\n\nKeep planned work distinguishable from what actually happened. A lesson may spend forty minutes on an unexpected difficulty and leave most of the plan unused. The tutor should be able to record that outcome and carry suitable material into the next session.\n\nMake the participant's history easy to consult from the current appointment. The person should find the relevant previous notes without searching through unrelated meetings. Reusable material can save preparation time while each session retains its own plan and record.\n\n## Let appointments change\n\nSupport creating, rescheduling, cancelling, and recording the outcome of appointments. Changing the time should retain the associated preparation and contact information. If there is a recurring series, make the difference between changing one appointment and changing the series understandable.\n\nShow conflicts in the terms that matter to the person, including travel or preparation time when their activity requires it. Give them a practical way to decide what fits. An appointment whose time has passed still needs an accurate outcome: held, cancelled, missed, or another status their practice uses.\n\nKeep payment records connected to the appropriate work. Find out whether the person charges per session, takes a deposit, or sells a block of sessions. Apply their rules for cancellations and credits, and make any remaining balance understandable. Record actual payments separately from amounts expected.\n\n## Use it before and after a session\n\nDeliver an installed application with persistent records and the ownership and recovery arrangements from the shared launch. Give the person useful exports when they need to share a schedule, session summary, or payment statement, choosing the relevant information for that recipient.\n\nWork through a representative sequence together: book a session, prepare it, move its time, record what happened, and arrange the next one. Include a payment example that matches their practice. Judge whether the application makes preparation easier and whether the next session begins with the information they need.\n\nExplain how an appointment, a plan, an actual meeting, and a payment relate. The person should understand why changing the calendar need not scatter their notes or lose track of money already paid.\n\nA later phone companion can show the next appointment and accept notes immediately afterward. Shared scheduling can be added where it helps the people involved. Preserve the session history and teaching or working material as the application grows.\n"
    }
  ]
}