Files
AWatch-rus/.github/GOVERNANCE.md
T
igor04091968 dcf14eae67
CI / Rust checks (push) Canceled after 0s
CI / Docs and registry checks (push) Canceled after 0s
CI / Smoke checks (push) Canceled after 0s
Coverage / Coverage baseline (push) Canceled after 0s
Dependency hygiene / Unused dependency check (push) Canceled after 0s
Dependency hygiene / Dependency duplicate report (push) Canceled after 0s
Dependency hygiene / Dependency security policy (push) Canceled after 0s
Dependency hygiene / Cargo udeps nightly advisory (push) Canceled after 0s
Operational maturity / Offline operational maturity (push) Canceled after 0s
Operational maturity / Live operational contract (push) Canceled after 0s
Security / Cargo audit (push) Canceled after 0s
Security / Cargo deny (push) Canceled after 0s
Security / Secret pattern check (push) Canceled after 0s
Security / Dependency review (push) Canceled after 0s
Codify production-first engineering governance
2026-07-01 08:48:35 +03:00

1.4 KiB

AWatch-rus Governance

GitHub is the public mirror validation surface. Primary registry release evidence must be produced on the Russian build-runner and primary operational context remains the private Gitea contour.

Production-first standard

AWatch-rus is already deployed in a real company. Production stability has absolute priority. The canonical engineering standard is:

Required PR evidence

Every PR must state:

  • Purpose.
  • Operational impact.
  • Risk assessment.
  • Rollback strategy.
  • Validation steps.
  • Documentation changes.
  • Acceptance criteria.

Documentation-only or governance-only PRs must explicitly state that runtime, API and UI behavior are unchanged.

Guardrails

  • Prefer additive, backward-compatible changes.
  • Do not redesign working subsystems without measured benefit.
  • Do not add dependencies without justification and validation.
  • Do not weaken authentication, authorization, audit logging, secret handling, dependency hygiene or configuration validation.
  • Do not enable heavy DLP, Loki or always-on Velociraptor during routine recovery, validation or public CI.
  • Keep blocking CI fast; keep heavy/load/nightly checks scheduled or advisory.