Ways of Working¶
How we build, review, and ship. Read this before opening your first PR.
The two non-negotiables¶
1. Feature branch for everything. No direct commits to main. Ever. Create a feature branch, do the work, open a PR, get review, merge.
2. Vinod signs off before merge to main. This applies to all repos — CurationStudio, Tool_Chest, Workbench, this wiki. If a ticket says "no merge without Vinod sign-off," that is a hard gate, not a suggestion.
Commit message convention¶
Every commit begins with a bracketed prefix. This makes build logs and GitHub history readable across repos.
[Prefix] type: description
| Area | Prefix |
|---|---|
| PSU Intelligence / PSU pipeline | [PSU] |
| Binding Authority | [BA] |
| Underwriting Hub / UW pipeline | [UW] |
| Claims Hub / FNOL pipeline | [Claims] |
| GKR CurationStudio | [GKR] |
| Tool_Chest / Flask tools | [Tools] |
| Auth / shared infra | [Infra] |
| Cross-cutting / multiple areas | [Workbench] |
| Wiki / knowledge | [Wiki] |
| Agent-generated PRs | [agent] |
Examples:
[GKR] feat: add WC jurisdiction rule for Ohio
[Claims] fix: AWW computation using correct denominator
[Wiki] docs: add enCODE use case for GL submission
[agent] sync: update asset library from assets.json
PR review culture¶
- One reviewer minimum — owner auto-requested via CODEOWNERS
- Preview URL required — Cloudflare Pages generates a preview for every PR; the reviewer clicks it before approving
- Agent PRs get the same gate —
[agent]prefix PRs still require human review before merge - No self-merge — even if you're the CODEOWNER, get a second set of eyes
Pages in this section¶
| Page | What it covers |
|---|---|
| Branch Discipline | Feature branch rules, naming, sign-off gates |
| Product Backlog | Active backlog items (auto-synced from tracker) |
Tools and access¶
Day-one setup and tool access → Tools & Access