How Stag Vault Tracks Are Researched, Tested and Updated
Every track in the vault goes through the same process before it is published and the same review loop afterwards. This page sets out that process so you can judge the material for yourself.
- Published:
- Last reviewed:
- Last updated:
Written and maintained by Ross, founder of Stag Vault. Prompts are described as structured and quality-reviewed — we do not claim a formal certification standard.
Opportunity research
Potential tracks are assessed against:
- Identifiable paying customer
- Specific problem
- Urgency
- Ability to pay
- Competition
- Start-up cost
- Delivery complexity
- AI leverage
- Speed to a paid pilot
- Recurring-revenue potential
Conflict and duplication check
New ideas are compared against existing tracks to prevent repeated or thin variations of the same opportunity.
Workflow design
Prompts are placed in a useful commercial order, normally covering:
- Validation
- Buyer selection
- Offer development
- Pricing
- Asset creation
- Marketing
- Outreach
- Delivery
- Quality assurance
- Upselling
- Review and improvement
Prompt testing
Prompts are tested for:
- Clarity
- Relevant output
- Useful structure
- Editable variables
- Realistic assumptions
- Safety boundaries
- Practical next actions
Commercial and safety review
Each track is checked for:
- Unrealistic earnings claims
- Copyright problems
- Personal-data risks
- Spam or deceptive marketing
- Professional-service boundaries
- Industry-specific legal or safety considerations
Publication and versioning
For every published page we record:
- Original publication date
- Last reviewed date
- Last substantially updated date
- Version number
- Author
- Reviewer
- Change summary
Dates shown on pages come from stored records and only change when content is reviewed or materially updated — never on page loads or deployments.
Ongoing corrections
Tracks may be revised when:
- Tools or platforms change
- Pricing assumptions become outdated
- Users identify unclear instructions
- A legal, ethical or safety concern arises
- A better workflow is validated
Spotted something that needs reviewed?
Submit a correction