Agency/docs/sites/PROPOSAL_TEMPLATE.md
Ryan Schultz d944943c55 refactor: rename TEMPLATE.md to PROPOSAL_TEMPLATE.md; link templates from docs
Names the process step not just the outcome. Both PROPOSAL_TEMPLATE.md
and RETIREMENT_TEMPLATE.md now linked from ARCHITECTURE.md site governance
section and README Contributing section.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-05-11 13:09:15 -05:00

54 lines
1.2 KiB
Markdown

# Site Proposal: [Platform Name]
**Proposed by:** [username]
**Date:** [YYYY-MM-DD]
**Status:** Proposed / Active / Retired
---
## What is this platform?
[Brief description of the platform and its role in the community.]
---
## Inclusion criteria
| Criterion | Met? | Notes |
|---|---|---|
| Data is publicly accessible (no API key required) | Yes / No | |
| Actively used by a meaningful portion of the community | Yes / No | |
| Activity represents genuine effort, not easily gamed | Yes / No | |
| Platform is stable enough to depend on | Yes / No | |
| Relevant to the community's actual work | Yes / No | |
---
## What signals would be collected?
[List the specific data points that would be pulled — e.g. post count, commit count, etc.]
---
## How would it be collected?
[Describe the public URL or feed that would be used. No API keys allowed — see ADR 003.]
---
## Proposed score weight
[Suggested weight and rationale. Remember weights are set separately in config.yaml —
this is a starting suggestion for community discussion.]
---
## Concerns or open questions
[Any known risks, gaming vectors, or unresolved questions about this platform.]
---
## Discussion
[Link to forum thread or other discussion, once opened.]