Codify risk-based change and deployment workflow #64

New issue

Closed

opened 2026-07-17 15:02:25 +01:00 by nimmo · 0 comments

nimmo commented

2026-07-17 15:02:25 +01:00

Owner

Context

Issue #60 demonstrated a repeatable workflow that gave useful operational confidence: issue → feature branch → MR → local and Forgejo validation → specialisation-safe canary → genuine deployment → no-op confirmation → evidence-based closure.

Existing guidance was duplicated and partially stale: it treated direct commits as the norm, selected validation mainly by file extension, and documented raw Electra nixos-rebuild test, which activates the base battery tier.

Scope

Make the issue/feature-branch/MR lifecycle the default for meaningful behavioural, service, CI, and multi-host work.
Define risk-based validation and evidence requirements.
Make just test the canonical specialisation-safe test path.
Record the PR nix flake check/VM requirement.
Retain a lightweight direct-commit path for documentation-only work.

Completion criteria

AGENTS.md and README describe one consistent lifecycle.
Test/deploy guidance preserves or explicitly chooses the active specialisation.
Validation and live-evidence expectations are clear and proportionate.
No redundant or contradictory workflow instructions remain.

Validated locally with just check; merged by MR #65.

## Context Issue #60 demonstrated a repeatable workflow that gave useful operational confidence: issue → feature branch → MR → local and Forgejo validation → specialisation-safe canary → genuine deployment → no-op confirmation → evidence-based closure. Existing guidance was duplicated and partially stale: it treated direct commits as the norm, selected validation mainly by file extension, and documented raw Electra `nixos-rebuild test`, which activates the base battery tier. ## Scope - Make the issue/feature-branch/MR lifecycle the default for meaningful behavioural, service, CI, and multi-host work. - Define risk-based validation and evidence requirements. - Make `just test` the canonical specialisation-safe test path. - Record the PR `nix flake check`/VM requirement. - Retain a lightweight direct-commit path for documentation-only work. ## Completion criteria - [x] AGENTS.md and README describe one consistent lifecycle. - [x] Test/deploy guidance preserves or explicitly chooses the active specialisation. - [x] Validation and live-evidence expectations are clear and proportionate. - [x] No redundant or contradictory workflow instructions remain. Validated locally with `just check`; merged by MR #65.

nimmo referenced this issue from a pull request that will close it,

2026-07-17 16:23:58 +01:00

docs: codify change and deployment workflow #65

nimmo closed this issue

2026-07-17 16:24:21 +01:00