Engineering documentation describes GOWDK's architecture, contribution standards, security model, operations, testing, release process, and durable decisions.
| Area | Documents |
|---|---|
| System design | Architecture |
| Repository conventions | Conventions, naming conventions, and documentation style |
| Code boundaries | Code quality, generated code policy, and dependency policy |
| Security | Security and threat model |
| Operations | Operations, testing, CI, and Windows CI |
| Releases | Release process and changelog |
| Decisions | Architecture Decision Records |
Use Product Requirements for capability status. Engineering pages explain how the system works and how to change it safely; they must not duplicate the product status matrix.
Old one-off implementation plans were removed after their useful facts moved to current product, reference, compiler, and engineering docs. Keep new plans short and scoped to active work. Delete or fold them into current contracts when they stop being useful.
Use an ADR instead of a plan when the durable decision is more important than the execution checklist.
Use the narrowest relevant checks first, then the repository gates required by the changed surface:
go test ./...
go build ./cmd/gowdk
scripts/test-go-modules.shDocumentation-only changes also run the checks listed in Documentation Style.