How to Use This Handbook
Choose the path that matches your work
Section titled “Choose the path that matches your work”Application developer: engineering principles → developer practice → SDLC → repository governance → React, Node, or Python CI → testing.
Platform/DevOps engineer: all of the above, plus reusable CI, CD, containers, Kubernetes, Terraform, supply-chain security, and operations.
Reviewer or engineering manager: principles → lifecycle → quality gates → repository governance → CI metrics → exceptions.
Page structure
Section titled “Page structure”Most standards use the same structure: purpose, Nexa context, mandatory and recommended rules, working model, evidence, failure modes, and maturity path. This consistency is intentional. A reader should quickly distinguish between policy and explanation.
Resolving conflicts
Section titled “Resolving conflicts”When standards appear to conflict, use this order:
- Security and legal requirements.
- The repository-type standard.
- The general handbook rule.
- Team convention.
Raise unresolved conflicts as a handbook issue rather than creating an undocumented local workaround.
Changing a standard
Section titled “Changing a standard”A proposed change should describe the problem, affected repositories, migration impact, security implications, and rollback plan. A standard is not changed solely because one repository finds it inconvenient. Conversely, a rule that repeatedly requires exceptions is a signal that the rule needs redesign.