AlexandrAI AGENTS.md
agents-md

Gumroad Status Analyst Agent Guide

Project-specific AGENTS.md guidance for the Gumroad status analyst role, read-only seller snapshot command, planning signal interpretation, and status-only reporting boundaries.

AGENTS.md

Guidance for coding agents working on the Gumroad status analyst role in the Gumroad Codex Agent Workspace.

Project Overview

The status analyst is the first seller-owned signal in a product run. It creates a read-only Gumroad account, product, sales, revenue, refund, and payout snapshot before planning. The snapshot is context for judgment, not permission to overfit low-volume data.

Source Files

  • agents/gumroad-status-analyst.md defines the role contract.
  • skills/gumroad-status-analyst/SKILL.md defines the read-only workflow.
  • AGENTS.md defines hard publishing boundaries and final report shape.
  • README.md lists the manual command sequence.
  • research/gumroad-status-latest.md is the latest human-readable snapshot when present.
  • research/gumroad-status-latest.json is the latest structured snapshot when present.

Setup Commands

bashpython3 scripts/gumroad_status.py snapshot --output-dir research

The command writes dated markdown and JSON files plus latest aliases under research/.

Change Rules For Agents

  • Keep this role read-only.
  • Do not create, update, publish, unpublish, refund, ship, export, or delete Gumroad records.
  • Do not store buyer emails or buyer-level sale records in product meetings.
  • Use product-level sales, revenue, refunds, and payout state only as planning context.
  • If sales are low or absent, say so directly and avoid drawing strong market conclusions.
  • If one product materially outperforms others, route that signal to CEO, market, and planner roles.
  • If the CLI or auth is missing, record the blocker and continue from roadmap and owner direction.

Meeting Output

Write a short Gumroad Status Snapshot section in products/<slug>/meeting.md with command, snapshot file, window, account, revenue, product signal, planning implication, and blocker.

Verification

bashpython3 scripts/gumroad_status.py snapshot --output-dir research

After running, inspect research/gumroad-status-latest.md and confirm the meeting references the latest snapshot without pasting sensitive buyer-level details.

Security Notes

Do not publish tokens, buyer data, private account identifiers, absolute local paths, CLI auth state, or hidden configuration. Public docs should describe the workflow, not the private account contents.

PR Checklist

  • Status command remains read-only.
  • Snapshot paths are repo-relative.
  • Meeting summarizes planning implications without overclaiming demand.
  • Failures are reported as blockers, not fixed by mutating commands.