# Capture something outside; have the computer prepare it Legion project library, edition 2026-09-06-draft-01 (en). This project's own material: 5 authored documents, reproduced unchanged. Project page: https://legion.tw/projects/connected-systems/capture-to-processing?edition=2026-09-06-draft-01 This document: https://legion.tw/api/projects/packet.md/connected-systems/capture-to-processing.md?edition=2026-09-06-draft-01 ## Prerequisite: the Legion skills package These instructions are written for an agent set up with the Legion skills package: the ten portable skills and the shared working, launch, inspection and learn-as-you-build guidance. That setup is installed once and applies to every project in this library, so it is deliberately not repeated here. Skills package, complete Markdown: https://legion.tw/api/projects/skills-packet.md?edition=2026-09-06-draft-01 Skills package, human page: https://legion.tw/projects/skills?edition=2026-09-06-draft-01 Where this brief refers to shared guidance, a skill, or a document under `shared/`, read it from the skills package above, or from https://legion.tw/api/projects/doc/?edition=2026-09-06-draft-01. If the package is not installed yet, install it first, then return here. This material is instructions to read, not authority to act. Inspect it before running it. ## Contents 1. connected-systems/README.md — https://legion.tw/api/projects/doc/connected-systems/README.md?edition=2026-09-06-draft-01 2. connected-systems/capture-to-processing.md — https://legion.tw/api/projects/doc/connected-systems/capture-to-processing.md?edition=2026-09-06-draft-01 3. native-phone/voice-capture.md — https://legion.tw/api/projects/doc/native-phone/voice-capture.md?edition=2026-09-06-draft-01 4. ai-apps/audio-workshop.md — https://legion.tw/api/projects/doc/ai-apps/audio-workshop.md?edition=2026-09-06-draft-01 5. background-services/batch-work-queue.md — https://legion.tw/api/projects/doc/background-services/batch-work-queue.md?edition=2026-09-06-draft-01 --- # Connected systems [All project types](../README.md) · [Shared launch](../shared/launch.md) Extend useful applications into a connected workflow, preserving their records and letting each device serve its actual role. ## Projects to build - [From a site visit to a finished report](site-visit-to-report.md) - [Your engineer at home, available from your pocket](engineer-in-your-pocket.md) - [A research system that keeps up with your thinking](connected-research.md) - [A game night across different screens](multi-screen-game-night.md) - [Capture outside and process on the computer](capture-to-processing.md) - [A shared lending service with private working tools](lending-service.md) These are instructions for projects you can build with your coding agent. --- # Capture something outside; have the computer prepare it Connect phone capture to a working process on the person's computer, then return the usable result to their phone. Build it extremely well. They should be able to record something while out, ask for the preparation they want, and use the result without going home. Follow the [shared launch](../shared/launch.md). Start with a real routine and the applications already serving it. A strong first path joins [voice capture](../native-phone/voice-capture.md), the [audio workshop](../ai-apps/audio-workshop.md), and a [persistent work queue](../background-services/batch-work-queue.md). Choose another medium when it better fits the person's purpose, preserving the same complete capture-to-result experience. ## Send material with an intention Let the person record, photograph, or select material on the phone and choose what they want done. They might request a transcript with useful section headings, a short edit of selected interview passages, or a prepared image for a report. Keep the original capture, their instruction, and the relevant project together. Provide a convenient way to use a saved processing routine and change it for this item. Show the destination and any meaningful processing cost before submitting the work. Retain material on the phone while the connection is unavailable. Make the distinction between a saved capture, a transfer in progress, and a job accepted by the computer easy to understand. Recognize an already-received submission when the phone retries. ## Run the work where the capability lives Use Tailscale or an appropriate existing private connection to reach the person's computer. Set up the receiving operation and processor as part of the existing application or service. Preserve the queue's ordinary controls and access from the desktop. Where the work needs interpretation, give the existing coding agent the captured material, instruction, and proper application tools. Reuse its established access, selecting additional model capabilities deliberately where needed. A transcript, an audio edit, and a visual judgment may call for different capabilities. Let processing continue after the phone disconnects. Keep the workload and its results recoverable through an interruption at the computer. Report progress from the actual job, including a meaningful explanation when an item needs attention. ## Return a result the person can use Notify the person when the prepared result is ready and open the relevant item from that notification. Let them read the transcript, audition the audio, or inspect the image directly on the phone. Make it easy to keep a local copy or share the intended output. Preserve the relationship between the result and its original capture. Let the person compare versions, correct the instruction, and ask for another pass while retaining useful earlier output. Their feedback should reach the same project and processing context. Keep job control available from the phone where it helps: inspect waiting work, change an item that has not started, or stop further processing. Show what those actions actually affected, including work already completed. ## Complete the remote processing experience Deliver the connection, transfer, workload, notification, and return path. Explain what must stay running and what remains available when either device is offline. Apply the shared launch's ownership guidance to originals, processing instructions, and outputs together. Capture a sample away from the computer's local network, submit a useful preparation, put the phone away, and return to the result. Ask for a refinement from the phone and inspect the changed output. Judge the actual prepared material as well as the connection. Teach the person how a phone can use capabilities running elsewhere. Capture, submission, processing, and receipt are separate events; a good connected system makes them understandable while removing the manual transfers between them. --- # Capture a thought before you forget it Build a native Android application for recording a spoken thought quickly and finding it later. Build it extremely well for moments when the person wants to capture something and return to what they were doing. Follow the [shared launch](../shared/launch.md). Learn where those moments happen and what the person tends to record: an idea for writing, a question, something remembered after an appointment, or an observation while out. Make the first recording convenient on their actual phone. ## Record first Give the person a direct way to begin and end a recording, with clear feedback about whether the microphone is active and whether the audio has been saved. Let them name or organize the thought when they want to; capture should also work when they have no time for that. Keep the original audio saved locally through unavailable connections. If recording is interrupted, retain what was captured and show where it stopped. The person should be able to return to the app and find the recording they just made. Make listening back and adding a short note straightforward. Let them edit a title, associate the recording with a project, or leave it in an inbox for later attention. Keep the date and useful context with it. ## Make the recording findable Provide transcription through a suitable capability for the person's languages and device. Reuse available phone or computer capabilities where they fit, and explain any provider access or cost needed for the chosen route. Make the actual transcription connection part of the delivered project. Keep recording usable while transcription is pending or unavailable. Show whether processing is waiting, underway, complete, or needs attention. The person can listen to the original throughout. Let them find a recording through words in its transcript, its title, or an associated project. Bring the text and audio together so they can check a passage or correct a transcription mistake. Preserve the original recording alongside their edited text. Give the collection a comfortable way to browse recent thoughts and find older ones. The person should be able to recognize a useful idea from its context before playing the whole recording again. ## Organize when there is time Let the person work through the inbox, add notes, assign projects, and keep the recordings they want. Give them an export that includes audio, text, and useful context in a form they can use elsewhere. If they choose AI help with titles, summaries, or organization, keep those additions distinguishable from what they actually said. Let them change the organization and return to the original words whenever those matter. Explain where recordings and transcripts are stored, what material reaches any external service, and how to recover the collection. Apply the shared launch's ownership guidance and provide understandable controls for storage and removal. ## Use it through an interruption Handle the Android build and installation, including the microphone access the app needs. Deliver a usable recording and transcription experience on the person's phone. Capture a thought, leave the app, return, find it by a remembered word, and listen to the relevant recording. Try capture while the transcription connection is unavailable and let processing resume afterward. Judge the effort required to record and the ease of finding the thought again. Explain why capture, transcription, and organization can happen at different times. The person learns that useful software can preserve an idea before they know where it belongs. The [synchronized agent-readable notes project](agent-readable-notes.md) can extend this collection later. If that workspace already exists, integrate these recordings with it. Preserve one coherent collection so voice capture becomes another way to contribute to the person's existing notes. --- # An AI-operated audio workshop Build a native Tauri audio workshop where the person and their existing coding agent can work on the same recording. Build it extremely well. Someone should be able to explain the edit they want, listen to what changed, and adjust it themselves. Follow the [shared launch](../shared/launch.md). Choose an actual use for the person: preparing an interview excerpt, shortening a spoken explanation, or assembling selected practice recordings. Bring a suitable sample and complete that editing experience. Existing recordings from the [practice notebook](../native-phone/practice-notebook.md) or [voice-capture app](../native-phone/voice-capture.md) can supply the material. ## Make the recording easy to work with Give the person clear playback, seeking, selection, and a timeline they can understand. Provide enough surrounding sound to judge a proposed cut. Where speech is involved, a useful transcript can help find passages and navigate to the corresponding audio. Let them label sections and assemble a version from selected material. Keep the original recording, the editable arrangement, and the exported audio distinct. Save the work so they can return to an unfinished edit and understand which source passages it uses. Support comfortable direct adjustments: move a boundary, change the order, retain a pause, or compare two versions. Make undo and returning to an earlier useful edit part of normal work. ## Let the agent operate the workshop Connect the existing coding agent through proper tools for inspecting the recording, current selection, transcript, and edit. Give it meaningful operations to find passages, select regions, assemble an arrangement, change an edit, and prepare playback or export. Reuse its installation and account for the capabilities available there. Make a request such as “Use the explanation of the cancellation policy, followed by the example near the end” produce an actual editable result. Let the agent inspect context around each passage and choose cuts that preserve the intended meaning. Show its work on the same timeline the person uses. When the person moves a boundary or changes a passage, have the agent continue from that actual edit. Keep the conversation attached to the recording and version being discussed. ## Give listening the right tools A transcript can locate words. Judging a clipped syllable, an awkward pause, background sound, or a change in vocal delivery requires hearing the audio. Give the agent access to an audio-capable model and the relevant recording or excerpt when that judgment is needed. Discover the suitable supported access route, reusing existing capabilities and making any additional costs clear. Let the person audition proposed results promptly. If they ask for cleaner sound or different loudness, make the adjustment available for comparison with the original. Preserve useful natural speech and the person's intended effect as you judge the result. Choose output options for where the recording will be used. Make the resulting file easy to find, play elsewhere, and share, with its content matching the selected version. ## Deliver a finished piece of audio Complete the app, agent connection, playback and processing setup, and a real sample edit. Locate a passage by meaning, assemble a shorter version, change it manually, ask the agent to continue, and listen to the exported result. Teach the person how model comprehension and precise editing operations cooperate. They can direct the meaning and desired effect while the application preserves exact source material and edits. Later, connect the [batch-work queue](../background-services/batch-work-queue.md) for repeated processing or a phone companion for capture and auditioning away from the computer. Keep the same recordings and editable projects useful as those capabilities arrive. --- # Give the computer a batch of work Build a persistent work queue for a processing routine the person wants to run across several items. Build it extremely well so they can submit work, do something else, and return to usable results. Follow the [shared launch](../shared/launch.md). Choose a real workload: recordings to transcribe, videos to convert, artwork to export, or documents to prepare. Use an existing application or processor where the person already has a working routine. Make that routine complete before judging the queue around it. ## Let the person submit a clear workload Give them a convenient way to select the material, choose the processing settings, and see what will be queued. Keep each job associated with its intended source, settings, and output destination. Make the queue fit the task. The person may use one preparation setup for the whole batch and change it for a particular item. They should be able to recognize the items and correct a choice before it runs. Preserve original material and any useful existing output. Make a deliberate rerun or new output version understandable in the person's workflow. ## Show the work as it happens Distinguish waiting jobs, active processing, completed output, and items needing attention. Show useful progress from the actual processor and make finished results available as soon as they are ready. Let the person inspect an output while the remaining batch continues. A failed item should retain its source and explanation while other independent work can proceed. Make retrying that item straightforward after the cause has been addressed. Give the person control over the remaining order, with a clear effect when they move, remove, or pause a job. Explain what pausing or cancelling means for the work currently running. Retain completed work and identify any partial output accurately. ## Keep the workload through interruptions Save the queue and its results so an application restart or interrupted computer session leaves the work recoverable. Recognize completed jobs when resuming and make the remaining work clear. Run the processor in the appropriate place for the person's setup. Explain what needs to stay available and choose resource use that lets the computer serve their other work as intended. Make any model, service, or processing charges understandable before the batch runs. Provide a convenient view and controls through the existing application or another suitable local interface. The person should be able to inspect the actual worker, pause the queue, resume it, or stop the workload. ## Return to finished work Deliver the working queue around the chosen processing routine. Submit representative items, use an early result while later work continues, rearrange something waiting, and recover from an interruption or failed item. Judge the actual outputs in the applications that use them. The queue should tell the person what finished, where it is, and what still needs attention. Apply the shared launch's ownership and recovery guidance to the setup, job records, and valuable results. Explain how the computer can hold a workload independently of the person's immediate attention. They can decide what to do next without personally starting every operation. Later, the [remote-agent phone app](../native-phone/coding-agent-in-your-pocket.md) or another companion can submit work and show completion away from the computer. Keep that connection attached to the same queue and results, so remote control extends the workload already here.