Contribute
The corpus is the measuring instrument. Good contributions to the corpus — thoughtful prompts in underserved axes — make the record more useful for everyone.
Proposing a prompt
Open an issue on the source repository using the Prompt proposal template. Your proposal should include:
- The exact prompt text.
- The axis you believe it fits (or a new axis with a rationale for why existing axes don’t cover it).
- What drift you think this prompt could expose and why that matters.
- Any known prior art — has this prompt been used in a study, benchmark, or news story?
- Optional: expected stance direction, if any, based on current public discourse.
What we reject
- Prompts designed to embarrass a specific provider. We measure drift; we are not a marketing arm for anyone.
- Prompts that would put our API keys at risk of takedown or that seek actually-harmful outputs. The refusal-boundary axis covers the gradient at a specificity level short of operational harm.
- Duplicates of prompts already in the corpus (public or held-out). Maintainers will check.
Reporting bugs
Methodology errors, statistical mistakes, or site bugs: open an issue and cite the specific URL or chart. We fix faster with a reproducible example.
Support financially
API costs dominate the budget. The current configuration runs on roughly $86 per month. Each meaningful expansion — adding Gemini, unalternating the frontier models, growing the corpus to 100+ prompts, funding durable S3 + IPFS storage so the “retention forever” guarantee is real — requires another step of sustained monthly funding.
Full breakdown at /funding/ — what funding unlocks.