Refresh tracked pre-launch stablecoin milestones, dates, launch phases, featured content, and promotion evidence. Use for the recurring upcoming-assets review.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Read docs/editorial-style.md; its pre-launch and coin-summary registers govern prose.
docs/process/adding-a-stablecoin.md owns lifecycle fields, schemas, promotion requirements, edits, and validation. Read Phase 0, Phase 1, and Phase 7; use shared/types/core.ts for live enum values. This skill adds the recurring research and approval loop.
shared/data/stablecoins/coins/*.json entry with status: "pre-launch", its current milestone/date/phase/content state, and data/ai-summaries.json. Rank by newest milestone or last file edit; entries with no milestone or no update for eight weeks receive deeper review.docs/process/agent-artifacts.md#harness-configuration. Check official issuer posts/docs first, then regulator material and reputable reporting. Check DefiLlama and CoinGecko structured data for activation evidence.Optional discovery of untracked candidates is research-only: search recent issuer/regulatory announcements and near-zero external listings, de-duplicate against the registry, and ask before adding anything.
Approval must cover each coin and action; an earlier explicit cohort instruction covering those coins remains valid. Ask again only for an uncovered addition, promotion, or other scope change. Preserve canonical identity, flags, and historical milestones. Add milestones oldest-first with a primary sourceUrl; add only notable featured content.
When changing an existing expectedLaunchDate, first append its old value to dateHistory as { "date": "<old>", "setOn": "<today>" }. An initial date has no prior value to append; never reconstruct guessed history.
Refresh an AI summary only for a material change: phase advance, launch-date shift of at least a quarter, named regulator/custodian/major partner, completed reputable audit, approval/charter/license decision, or confirmed mainnet date. Use write-ai-summaries for the editorial contract.
For standalone approved edits, run npm run bootstrap:generated and npm run check:stablecoin-data after coupled source edits are complete. In a coordinated addition, keep the research and promotion-evidence duties here, but return evidence, changed source paths, and observed versus unexercised checks in the addition/evidence handoff packet; the orchestrator owns the single Phase 7 generation/check pass after all specialists land. Do not treat a build alone as schema validation.
Never execute promotion here. Recommend it only when stablecoin-runtime-price-marketcap-gate proves both current price and circulating/market-cap paths, identity matches by contract or issuer domain, and the listing has non-zero live supply rather than preview-only zeros. Hand the evidence to stablecoin-addition-orchestrator, including current methodology consequences and unresolved coverage.
Report changes/approvals, no-change coins, deferred conflicts, promotion evidence, and validation. Use ignored agents/ scratch only for a campaign ledger with an owner/retention contract; do not create a durable shadow registry.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Review the retained annotation candidate queue and curate per-coin editorial history. Use weekly during active event periods, monthly otherwise, or on queue-health warnings; this does not restore the retired live chart overlay.
The English summary is being prepared. Showing the original description.
Generate a weekly changelog entry from git history, filtering operational noise and producing editorial summary, field notes, statistics, and a bounded commit manifest. Stops for review unless commit was explicitly requested.
The English summary is being prepared. Showing the original description.
Research and populate tracked stablecoin compliance sidecars for the U.S. GENIUS Act, EU MiCA, or both. Use when adding or auditing authorization, applicability, pathway, or disclosure evidence.
The English summary is being prepared. Showing the original description.
Use when adding, reviewing, squashing, deploying, or rolling back Pharos D1 migrations or schema cleanup.
The English summary is being prepared. Showing the original description.
Drain the Pharos Dependency Map coverage-audit queues into evidence-refreshed edges, reviewed target dispositions, or documented deferrals. Use monthly after weekly production dependency audits, after dependency coverage drops, or when reviewing adapter gaps, material unlinked slices, symbol leads, duplicate/split groups, or unverifiable published edges.
The English summary is being prepared. Showing the original description.
Update Pharos funding donations by reconciling inbound transfers, rejecting wallet self-activity and spam, pricing receipt-time value, and appending user-approved rows.
The English summary is being prepared. Showing the original description.