Engineering Discovery
This is the engineering health resource library for government delivery teams. It exists to help agency engineers move from red to green on health-report gaps — with guides, templates, and worked examples designed for the constraints of public-sector delivery.
How to use this library
There are four types of content here. Pick the one that matches where you are.
Guides — Explainers that teach a concept, when it matters, and how to approach it in a government context. Start here if the concept is new to you or your team. Guides cover the why and the what before the how.
Templates — Copy-paste starting points. They remove the blank-page problem for common artifacts: runbooks, postmortems, environment matrices, integration inventories, and more. Every template includes a filled-in government example so you can see what “good” looks like before you write your own.
Starter Kits — Bundled sets for a recurring readiness theme: monitoring, incident response, CI/CD, ATO evidence packages. A starter kit groups related guides, templates, and checklists into a single starting point for a common scenario.
The Health Report — The 1-hour Engineering Health Report maps to every section in this library. Run it at the start of an engagement to identify your red areas, then use the library to address them one at a time.
Start here
If you don’t know where to start, open the 1-hour Engineering Health Report first. Work through it in a single sitting with your tech lead or a small team. It will surface your highest-risk gaps in about an hour. Then come back to this library and use the navigation table below to find the guides and templates that address those gaps directly.
Do not try to work through this library top to bottom. Use the diagnostic to prioritize.
Navigation
Guides
| Guide | What it covers |
|---|---|
| Architecture Diagrams 101 | How to draw and maintain system architecture diagrams for government ATOs and stakeholder reviews |
| Blameless Postmortems | How to run incident reviews that improve systems without punishing people |
| CI/CD from Zero | How to build a working deployment pipeline starting from manual deployments |
| Data Flow Diagrams 101 | How to document where data goes, especially PII and PHI in agency systems |
| Environment Parity | How to keep dev, staging, and production environments aligned in government hosting contexts |
| Monitoring 101 | How to set up meaningful monitoring for a government system that has none |
| Observability 101 | How to move beyond uptime checks to structured logs, traces, and metrics |
| On-Call and Escalation Basics | How to set up a first on-call rotation and escalation path |
| Runbooks 101 | How to write runbooks that work during incidents and satisfy audit requirements |
Procurement
The procurement guidance now lives in its own Procurement section.
| Resource | What it covers |
|---|---|
| Tools and Software | Every tool in the stack — license, self-hostability, paid alternative replaced, a budget-justification template, and the enterprise functionality (SSO first) to verify before buying |
| Federal Procurement | FAR thresholds, GSA Schedules, SAM.gov, purchase cards, small-business set-asides |
| Maryland Procurement | BPW, eMMA, COMAR Title 21, small-procurement and purchasing-card limits |
Templates
| Template | What it produces |
|---|---|
| Problem Statement Brief | A structured one-pager that defines the problem, affected parties, urgency, and success criteria |
| Success Metrics Worksheet | A metrics table with baselines, targets, data sources, and review cadences |
| Ownership Map | A table mapping systems, decisions, and vendor relationships to named owners |
| Team Topology Worksheet | A roster, role coverage assessment, skill gap matrix, and sustainment plan |
| System Inventory | A full stack inventory: runtime versions, infrastructure, databases, third-party libraries |
| Architecture Diagram Starter | C4 context and container diagram templates with an ATO review checklist |
| Data Flow Diagram Starter | A DFD template with PII labeling conventions and privacy officer questions |
| Deployment Flow and Approval | A deployment stages table, emergency change process, and rollback procedure |
| Release Checklist | A pre-release, release, and post-release checklist with evidence capture fields |
| Runbook Skeleton | A complete runbook template with a filled-in database connection pool example |
| Incident Review (Postmortem) | A blameless postmortem template with government mandatory reporting checklist |
| Vendor Dependency Register | A vendor register with FedRAMP status, SLAs, fallback plans, and risk assessment |
Government delivery realities
Every guide and template in this library assumes the following:
- Approvals may be required. A change that would take an hour in a private startup may take weeks in a government context because of change management boards, authority-to-operate (ATO) requirements, or agency IT policy. The templates account for this.
- Environments may be controlled. You may not have direct access to production. You may not be able to install arbitrary software. You may be working inside a GovCloud enclave or an agency network with outbound restrictions. Every guide is written with these constraints in mind.
- Telemetry may be subject to privacy rules. What you can log, how long you can retain it, and who can access it may be governed by the Privacy Act, agency data governance policy, or a System of Records Notice (SORN). Observability advice in this library is written with those constraints in mind.
- Vendor relationships may be governed by contract or procurement rules. You may not be able to switch tools without a new procurement action. You may not be able to get a vendor to change their behavior without going through a contracting officer. Templates that involve vendor relationships include guidance for working within these constraints.
This is not private-sector DevOps content lifted from a tech company blog. It is designed for the way public delivery actually works.