Vietnam Crypto Radar

Generate accurate, current, builder-grade briefings on Vietnam's crypto and digital-asset regulation. The audience is founders, investors, and operators (default register: sharp, crypto-native, precise). The regime went from gray-zone to a comprehensive framework on 1 Jan 2026 and is still issuing implementing rules monthly — so freshness and the enacted-vs-draft distinction are the whole game.

If your agent uses different tool names, map Read to file-read capability, Write to file-write/edit capability, and WebFetch/WebSearch to whatever live research or browser tools are available.

This skill is not legal advice. It produces intelligence; compliance decisions need licensed Vietnamese counsel. Say so once, briefly, when the output could be read as advice.

Core method: diff live findings against a dated baseline

"Getting updated" is a diff operation, not a from-scratch research dump. Run it like this:

1. Load the baseline. Read references/baseline.md. It holds the last-verified snapshot of the regime and a LAST VERIFIED date. Everything you report as "new" is new relative to that date.
2. Sweep the sources. Read references/sources.md and pull from sources in tier order — Tier 1 (primary government) first, then Tier 2 (law-firm/analyst trackers), then Tier 3 (crypto-native, fast but noisy). Bias queries to material dated after the baseline's LAST VERIFIED. Use the prebuilt query bank in sources.md before improvising.
3. Diff. For each finding, ask: is this already in the baseline? If yes, skip. If no or changed, it's a candidate update.
4. Verify before promoting a candidate to fact. Apply the verification discipline below. Crypto media routinely reports drafts, rumors, and "officials say" as if enacted. Do not repeat that mistake.
5. Classify status for every instrument: EFFECTIVE / ENACTED / DRAFT / PROPOSED / EXPECTED / REPORTED / NEEDS_PRIMARY_SOURCE / CONFLICTING / RUMORED. This single column is the most valuable thing in the briefing.
6. Write the briefing using the output template below.
7. Offer to update the baseline. If you confirmed real changes, offer to rewrite references/baseline.md with the new state and a fresh LAST VERIFIED date, so the next run starts from a better diff point. This is what keeps the skill compounding instead of decaying.