# PVTY 30-day evidence-led growth operator plan

Published: 31 August 2026
Objective: increase qualified discovery of PactVerity's working evidence product and canonical PVTY identity without manufactured trading, bought followers, undisclosed promotion or return claims.

## Operating rules

1. Product evidence leads; token access is secondary.
2. Every factual post links to a reproducible page, public API, source file or on-chain record.
3. Applications, proposals and submissions are never described as integrations or adoption.
4. When a post mentions market access, it also states that liquidity is founder-funded and shallow and that price, execution and exit capacity are not guaranteed.
5. No wash trading, coordinated buys, founder self-trading, paid holders, engagement pods, mass mentions, copied replies or unsolicited direct messages.
6. External forms and public posts require final human review before submission.

## Channel roles

- **Website:** canonical evidence hub, live route and trust APIs, receipts, challenge leaderboard, treasury and LP evidence.
- **GitHub:** reproducible examples, benchmark issues, bug reports and independent reproduction requests.
- **X:** concise native demonstrations, build notes, limitations and public replies to directly relevant technical discussions.
- **Telegram:** community support, verified announcements and concise answers; no unsolicited outreach to other groups.
- **YouTube:** short screen-recorded demonstrations that show the product result and verification steps rather than price charts.

## 30-day sequence

### Days 1-7: canonical identity and reproducibility

- Publish the canonical token dossier, Phantom public token link and independent market links from one website page.
- Demonstrate one Proof Engine receipt from input to re-verification in a native short video.
- Open one GitHub reproduction issue with exact commands and expected hashes.
- Invite security and agent-framework developers to reproduce a benchmark; record only verified responses.
- Publish one limitation-focused post explaining what a deterministic receipt proves and does not prove.

### Days 8-14: external evaluation

- Share the Receipt Challenge with Solana infrastructure, AI-agent tooling and API-observability builders.
- Publish a weekly readiness report with holder, liquidity, identity, product-evidence and blocker fields.
- Release one technical article targeting a specific search intent such as “verifiable AI agent receipts” or “API SLA evidence”.
- Ask qualified reviewers for a reproducible critique, not an endorsement.
- Resubmit third-party profile corrections only when each platform's rules and waiting periods permit it.

### Days 15-21: developer proof

- Publish a minimal integration example and a five-minute reproduction path.
- Turn genuine questions into an FAQ with source links.
- Record and publish verified challenge entries; do not publish unverified submissions as success.
- Hold a technical session only when there is a credible agenda and confirmed participant value.
- Compare week-over-week qualified visits, API calls, challenge submissions and GitHub activity.

### Days 22-30: compound the strongest evidence

- Expand the best-performing technical page with new verified examples and internal links.
- Repurpose the strongest demonstration into X, YouTube and Telegram formats without copying spammy text.
- Publish the next transparency and Phantom-readiness report.
- Contact a small, relevant second cohort using personalised evidence questions.
- Stop channels and formats that produce only low-quality clicks; double down on verified reproductions and developer conversations.

## Measurement

Use UTM fields on campaign links: `utm_source`, `utm_medium`, `utm_campaign=pvty_evidence_30d`, and a factual `utm_content` label. Report these separately:

- Search impressions, non-brand queries, indexed priority pages and qualified organic visits.
- Proof Engine completions, Receipt API requests, public receipt events and verified challenge submissions.
- GitHub issue responses, reproductions, review offers and merged external contributions.
- Genuine holders, unique traders, repeat traders, liquidity depth and Jupiter Organic Score.
- X impressions, profile visits, link clicks and qualified technical replies.
- Newsletter subscribers and developer applications, with applications kept separate from verified integrations.

The campaign succeeds through verified product interest and durable discovery. It does not promise a market-cap target, wallet ranking or token-price result.