AlexandrAI AGENTS.md
agents-md

Gumroad Product Artifacts QA Gates Agent Guide

Project-specific AGENTS.md guidance for scripts/product_artifacts.py QA, content volume gates, meeting trace checks, product image checks, source notes, and premium packaging thresholds.

AGENTS.md

Guidance for coding agents working on Gumroad product artifact QA gates.

Project Overview

scripts/product_artifacts.py qa validates whether a product directory is safe and useful enough for dry-run or publish. It checks product.json, meeting trace, source notes, content volume, generated artifacts, image quality, premium packaging, blocked claims, and policy fields.

Source Files

  • scripts/product_artifacts.py owns qa_product() and all QA helpers.
  • products//product.json is validated.
  • products//meeting.md must include trace and Taste Gate.
  • products//build/manifest.json is required after render.
  • tests/test_product_artifacts_content_quality.py covers traceability, thin content, taxonomy, source notes, and image quality.

Setup Commands

bashUV_LINK_MODE=copy UV_PROJECT_ENVIRONMENT="$HOME/.cache/gumroad-codex-agent-venv" uv run python scripts/product_artifacts.py qa products/<slug>
python -m unittest tests/test_product_artifacts_content_quality.py

Change Rules For Agents

  • Do not bypass QA errors by editing qa_report.json.
  • Fix product.json, meeting.md, or assets, then rerender and rerun QA.
  • Keep blocked claim patterns strict for guaranteed outcomes, regulated advice, and scraping instructions.
  • Keep meeting trace checks active: Agent Invocation Ledger, execution mode, required role paths, global taste skill, and Taste Gate.
  • Keep content floors meaningful so sections and templates are not empty shells.
  • Keep source_notes required for sources used, source limits, and claim boundaries.
  • Keep image QA active for resolution, file size, aspect ratio, and flat-image detection.
  • Keep premium packaging checks tied to guide pages or rich walkthrough examples.

Verification

QA passes only when errors are gone. Warnings still require human judgment before publish, especially fallback cover, simple PDF renderer, or below-premium volume warnings.

Security Notes

QA should reject or surface secrets, private account data, private endpoints, local absolute paths, unsupported professional-advice claims, and unsafe automation artifacts.

PR Checklist

  • QA report is generated by the script.
  • Errors are fixed at the source.
  • Meeting trace is complete.
  • Source notes and disclaimer pass.
  • Image and premium packaging gates are reviewed.