π‘ Proposals
9 / 9
| Title | Author | Status | Date βΌ |
|---|---|---|---|
| Playwright e2e per feature, gated in CI (Testim runs in parallel) | relbns | open | 2026-07-01 |
| Bounded-by-construction pagination primitive + lint enforcement | relbns | open | 2026-06-17 |
| Self-cleaning ephemeral verify harness | relbns | open | 2026-06-14 |
| LLM token-cost & context economy β promote the principle, gate the tools | relbns | graduated | 2026-06-07 |
| Versioning & release-notes standard | relbns | open | 2026-06-03 |
| Confluence content migration to bewith-docs | relbns | claimed | 2026-05-31 |
| Filter capability discovery by user role + artifact audience | relbns | open | 2026-05-31 |
| Formalize enforcement tiers + add opt-in shell helpers (Tier 0) | relbns | done | 2026-05-29 |
| Tag Datadog logs and traces with X-App-Version / X-App-Platform from mobile | relbns | claimed | 2026-05-29 |
What lives here: lightweight feature / infrastructure / process / tooling ideas before they earn an RFC or spec. Side-project sized (S/M), single-engineer scope.
Use vs. siblings: an RFC is heavier (multi-team, week-plus, comment window); a PRD is for an already-agreed feature about to be built. Proposals are the lightest tier.
Template: Proposal Β· filename:
docs/proposals/proposal-YYYY-MM-DD-slug.mdHow it works: see Proposals methodology for lifecycle, statuses, and triage cadence.
The bar to write a proposal is intentionally low β anyone in the org can drop a markdown file here. Newest at the top.
Activeβ
| Title | Author | Owner | Category | Effort | Status |
|---|---|---|---|---|---|
| Playwright e2e per feature, gated in CI (Testim in parallel) | @relbns | open | process | L | open |
| Bounded-by-construction pagination primitive + lint enforcement | @relbns | open | infrastructure | L | open |
| Self-cleaning ephemeral verify harness | @relbns | open | tooling | M | open |
| LLM token-cost & context economy | @relbns | open | infrastructure | M | open |
| Versioning & release-notes standard | @relbns | open | infrastructure | M | open |
| Filter capability discovery by user role + artifact audience | @relbns | open | infrastructure | M | open |
| Confluence content migration | @relbns | @relbns | process | L | claimed |
| Tag Datadog from X-App-Version | @relbns | @relbns | infrastructure | S | claimed |
Clusters under reviewβ
Proposals on overlapping topics that triage should decide how to resolve.
- App/service version visibility β Versioning & release-notes standard (the broad standard) subsumes the layer-3 slice in Tag Datadog from X-App-Version (already claimed/shipping). Triage: keep the Datadog one as the first concrete step, fold its pattern into the standard.
Doneβ
| Title | Owner | Shipped | Outcome |
|---|---|---|---|
| Enforcement tiers + opt-in shell helpers | @relbns | 2026-05-29 | Added docs/methodology/enforcement-tiers.md + templates/shell-helpers/ with first Tier 0 helper (git branch interceptor). |
Promotedβ
| Title | Owner | Graduated to | Date |
|---|---|---|---|
| None yet. |
Archivedβ
| Title | Author | Archived | Why |
|---|---|---|---|
| None yet. |
How to add a proposal
- Run
/proposeand answer the four questions, or - Copy the template into
docs/proposals/proposal-YYYY-MM-DD-slug.mdmanually - Append a row to the Active table above (the index is hand-maintained, not auto-generated yet β a script will land in a follow-up)
- Open a PR or commit directly β both are fine for status
claimed/open