# Operations Reports

This folder is the durable operating log for Get Started with Web3.

Use it to keep growth, content, community, distribution, AI-native, sponsorship, and technical-health work visible after each operating day. Strategy docs define the plan; operations reports record what actually happened.

## Cadence

- Create one report per active operating day.
- File name: `YYYY-MM-DD-daily-report.md`.
- Use `templates/daily-report-template.md` for the structure.
- Prefer recording evidence links over memory: PRs, issues, workflow runs, public URLs, and external submissions.

## Required Sources

Each report should refresh:

- GitHub repo metrics: stars, forks, watchers, open PRs, and current topics if changed.
- Recent merged PRs and closed issues.
- Latest production deploy status.
- External distribution status, including awesome-list PRs and community posts.
- AI-native status: `llms.txt`, AI manifest, content index, MCP, and verification notes when touched.
- Monetization and sponsor lead movement.
- Next 1-3 actions for the next operating block.

## Risk Boundaries

Record, but do not execute without explicit confirmation:

- Changing donation or payment addresses.
- Accepting sensitive finance/trading sponsors.
- Private repository, ownership transfer, deletion, or secret-handling actions.
- Any action that bypasses tests, security checks, or protected deployment flow.
