README.md
markdown
sha256:94ec65bd2b200240ac785a97cf14c5db066832bd608a24d6a9c151f17b918b02
feat(calendar): hosted bridge/gateway route parity and time…
Human
minor
⚠ breaking
37 days ago
Engineering team template
Built for software and product engineering teams that want architecture decisions, runbooks, incidents, and retrospectives searchable beside onboarding material.
Target audience
- Tech leads documenting ADRs and runbooks without a separate wiki
- SRE and platform engineers standardizing incident and deploy practice
- Engineering managers capturing retro outcomes with traceable action items
Folder layout
| Folder | Purpose |
|---|---|
inbox/ |
New-hire orientation pointers |
architecture/ |
ADRs for APIs, data models, and cross-cutting concerns |
runbooks/ |
Step-by-step operational procedures |
incidents/ |
Post-incident notes and reusable templates |
retrospectives/ |
Sprint or milestone retros with commitments |
onboarding/ |
Checklists and first-week expectations |
Use consistent project values in frontmatter (team or service name). Sample content uses 2026-04-07 as a reference date.
File History
1 commit
sha256:94ec65bd2b200240ac785a97cf14c5db066832bd608a24d6a9c151f17b918b02
feat(calendar): hosted bridge/gateway route parity and time…
Human
minor
⚠
37 days ago