[est. 1–4h · ~20k–200k tok · ~$0–5] Optional: peer outreach for shared-quota-semantics (last)

[djbclark]

Estimate: 1–4h focused work · ~20k–200k norm. tok · **$0–5 norm. $** (wide/rough).
Last optional step after dogfood — operator-gated outreach, not auto-spam.

Summary

Share meaning (prepaid ≠ burn, shared allotment, pace bands, fixtures) with 1–2 Layer 1 or peer tools via short upstream issues/PRs that link one fixture + one rule id — not “please read our Python.”

Candidates (examples)

• CodexBar / OpenUsage / caut — prepaid display honesty, stable window_minutes
• quotabot / onWatch — optional decision-band vocabulary (no code merge)

Non-goals

• Merging aiuse into another product
• Demanding they adopt ranking
• Publishing a separate PyPI package until a peer wants co-ownership

Acceptance

• At least one thoughtful upstream issue filed by operator (or explicitly wontfile)
• Links recorded in docs/shared-quota-semantics.md or handoff

Context

docs/next-options.md, docs/competitive-landscape.md — “move ideas into competitors.”