Last checked with GitLab: . Status comes from GitLab using a 2-minute cache. Merge events clear affected cached statuses. An already-open page does not update itself. Refresh page.

An MR completes this bounty when it is merged into main with Closes #281 and GitLab closes the issue. A mention or an updated timestamp is not completion. Awarded points appear in Activity.

Submit a merge request that closes this issue to earn points on merge — bounties stack on the standard +40 merge_pr award. New to the repo? See the Contributing guide, and Local Development & SSO to run the app locally (cp .dev.vars.example .dev.vars && pnpm dev, after rebasing on main) and fully test your change before opening the MR.

Description

Required timestamps, Markdown commands and accepted scripts

  • Clickable video timestamps are required. For each major step taken from the source video, provide the actual MM:SS (or HH:MM:SS) timestamp linked to that exact point in this issue's direct video URL using its t= offset. Map the numbered guide steps and their commands to those timestamps. Label new or changed steps that exist only in the current DragonOS release as current-release additions instead of inventing a source timestamp. Watch and verify the referenced segment; a link to the full video alone is insufficient.
  • Commands must use fenced Markdown code blocks. Use a language tag such as bash for shell commands or python for Python code. Keep commands copyable, omit shell prompt characters, explain placeholders and working directories, and put expected output in separate text or json blocks. Preserve command order and distinguish required commands from optional commands. Screenshots and inline prose supplement the code blocks.
  • Supporting scripts are accepted bounty deliverables. Reusable setup, capture, analysis or verification scripts can be published as public GitLab snippets in Public Repos / irregularchat-snippets, the community's gist-style project. Link each script from the guide and its MR with its filename, purpose, dependencies, inputs, outputs, license/attribution, tested revision/commit when available, and SHA-256 checksum of the tested contents. Include fenced commands to obtain and run the script, example arguments, expected results and cleanup. Record its actual execution on the latest installed DragonOS and map the workflow it automates to the guide/video timestamps. The public script and the wiki guide are parts of this same bounty.
  • Confirm the snippet itself is public. Project visibility alone is insufficient: bot-created snippets default to internal. For a file shared through the Signal bot, its uploader or an admin can reply to the bot's snippet message with the command below. Link the resulting snippet, then verify that its page and source can be read while signed out. Publish only the contributor's intended public code and examples; keep credentials and private captures out of snippets.
!code -p

Acceptance evidence must include the timestamp-to-step mapping, rendered fenced command blocks, and—when submitting scripts—the public snippet URL, tested contents checksum and a reproducible run. Existing latest-installed-DragonOS, topic-specific outcomes and reviewer reproduction requirements still apply.

<!-- dragonos-guide-format-and-scripts:2026-10-18 -->

---

Source video and current-release clarification (2026-10-18)

Direct source: DragonOS LTS DSP and signal analysis with Composable-SDR + Inspectrum (RTL-SDR) — CemaXecuter / Aaron. Convert only the file-analysis/inspectrum portion into a first written lesson using the shared #280 synthetic-IQ fixture unchanged. Do not recreate the video's live capture or require Composable-SDR. Link relevant source timestamps and explicitly document this narrower scope.

The latest x86-64 release checked today is DragonOS Resolute R1 (DragonOS_Resolute_R1.iso, Ubuntu/Lubuntu26.04): official files. Recheck the latest stable release at implementation and MR review. Install it in an x86-64 VM or on a dedicated machine and test the lesson there; another distribution, a live-only session or an unexecuted transcript is insufficient. Record the ISO/checksum verification, installed OS/kernel, inspectrum version, architecture, environment and test date. If a newer stable release appears, use it and update the guide; record any blocker rather than silently testing an older version.

Require original numbered steps/screenshots with alt text, expected output, troubleshooting, cleanup, a video-to-current-version changes table, and a second reader's reproduction on the latest installed release. Credit the creator and link his direct video/channel; use original prose and correctly licensed fixtures. No RF hardware is required for this file-only exercise. Installation is a documented prerequisite, not a new OS installer automation deliverable.

This is the existing first-tone/sample-rate lesson, distinct from later live capture, protocol decoding or spectrum automation guides. It remains blocked on #280; the earlier contradictory independent-fixture sentence below has been removed. The shared fixture remains the single source of truth. Link this lesson from the DragonOS overview. Installation walkthrough work is a separate guide in this series.

---

Use the shared synthetic-IQ learning fixture to add one first DragonOS file-processing exercise. This follows the fixture generator/report foundation and teaches one existing DragonOS tool without requiring a receiver.

Who might enjoy this

  • Community interests: RF / SDR (Dragon), Hardware / fabrication, Tech
  • Skills: docs, qa
  • Experience: starter; work style: writing.
  • Readiness: blocked; bounty size: S (existing points tier; standard merge award stacks separately).

Current behavior and starting points

Source-reviewed against main cf05b29c6256dba70d0ebc09b22cc9867cdb786a on2026-10-18. Check current main and related issues/MRs before implementing so existing work is reused.

Relevant Files

Deliverables

  • A worked file-processing walkthrough consuming the rf-synthetic-iq fixture unchanged with one already-listed DragonOS tool; link its existing generator instead of creating another.
  • Document the tested tool version, expected display, no-hardware check, and the wrong-sample-rate teaching case using that same fixture.

Dependencies and decisions

  • #280: Build a reproducible synthetic IQ learning bench

Acceptance criteria

  • [ ] A clean documented local environment opens the fixture and shows the specified synthetic tones with labeled axes.
  • [ ] A second reader can reproduce the exercise using only the published files and steps; record the exact tool version and an original screenshot.
  • [ ] The lesson identifies an incorrect sample rate as a controlled wrong-answer case and explains why the display changes.
  • [ ] Record named baseline failures and the exact commands used. A behavior fix includes a real route/database/protocol check observed failing before the change. Knowledge work includes source traceability and reproducible reviewer evidence.
  • [ ] Run the affected app's existing checks. Explain any baseline failures rather than reporting a matching failure count as proof.

Try it locally

Start from the existing source files above. The following is the target demo your contribution should enable; a newly proposed script or fixture is part of the deliverable:

Open the supplied synthetic recording in the documented tool; no SDR dongle, license, account or transmitter is needed.

Use public or synthetic examples. Starter work should run without production access; explicitly name any software/device prerequisite before claiming it is ready.

Out of scope

  • No operating-system installation automation, USB flashing, real RF capture or device purchases. A manually installed current DragonOS environment is required for validation.
  • Unrelated refactors, new services/providers, bulk dependency changes, production access changes, unrequested notifications, and copying private member material. Keep credentials and unresolved security findings outside the issue and repository.

For a coding agent and reviewer

Read AGENTS.md, applicable .cursor/rules/, app instructions and docs/contributing/agentic-bounty-review.md. Reuse the existing shared helpers, identity/access paths and app styling. Implement one bounded story and provide evidence the accepting app maintainer can reproduce. State updated / pre-release verified / released / live verified accurately.

A parent index carries no duplicate award for these child deliverables. Open one scoped MR using this issue's actual number after the closing keyword. Link your GitLab identity on Scoreboard; the existing merge webhook handles eligible points.

Catalog index: #258.

<!-- community-interest-bounty:2026-10-18:dragonos-offline-first-lab --> Video-guide series index: #301.

Relevant files

Hints

No hints yet.

Activity

No points have been awarded for this bounty yet.

Comments

No comments yet. Be the first to weigh in.

↑ Top