Run NVIDIA ASR NIM with Sapat

[absalonCRC]

/claim #13

Maintainer Summary

This PR is ready for editorial review for the Daytona / Sapat NVIDIA ASR NIM guide bounty. It is documentation-only in the Daytona content repo, with the linked implementation work kept in the companion Sapat PR.

Why it can merge independently:

• Adds a focused guide, definition, author profile, and original workflow diagram
• Links the companion Sapat provider PR instead of mixing implementation into this content repo
• DCO is green and maintainer edits are enabled
• No secrets, API keys, payout details, or private endpoint values are included
• Targeted markdownlint and git diff --check validation passed locally

Summary

• Add a long-form Daytona guide for running Sapat with an NVIDIA ASR NIM / Parakeet transcription provider
• Add a companion ASR NIM definition and first-time author profile
• Add an original SVG workflow diagram for the Daytona -> Sapat -> NVIDIA NIM -> transcript flow

Companion Sapat provider PR: nibzard/sapat#34

Validation

• npx --yes markdownlint-cli guides/20260521_run_nvidia_asr_nim_with_sapat.md definitions/20260521_definition_asr_nim.md authors/absaloncrc.md
• git diff --check

@algora-pbc /claim #13

Payment fallback if Algora is not preferred: PayPal cultofrozen@gmail.com

[absalonCRC]

Status update for review and bounty processing:

• PR includes /claim #13; Algora claim page is live: https://algora.io/claims/dYoA7SvgeXbqWH2F
• Scope is the NVIDIA ASR NIM / Parakeet Sapat guide slice, with companion implementation PR linked in the body.
• Fresh local revalidation on 2026-05-21T11:34+02:00 passed:
  • npx --yes markdownlint-cli guides/20260521_run_nvidia_asr_nim_with_sapat.md definitions/20260521_definition_asr_nim.md authors/absaloncrc.md
  • git diff --check
• DCO is green, maintainer edits are enabled, and no secrets/API keys/private endpoints are included.

If Algora payout is not the preferred route, direct fallback can go to PayPal: cultofrozen@gmail.com.

[absalonCRC]

Hi @nkkko, I tried to request review through GitHub but do not have permission to use reviewer assignment on this upstream PR. Could you route this for review when available?

The PR is ready for editorial review: DCO is green, maintainer edits are enabled, the companion Sapat implementation is linked, and targeted markdownlint plus git diff checks passed locally. The issue claim is already filed at https://algora.io/claims/dYoA7SvgeXbqWH2F.