Jon Chery
2c08c778a9
REQ-221: skills/ directory with 9 Atelier-derived skill files mapped to the BA.A citizen-developer catalog: api, security, data, testing, observability, errors, devops, infrastructure-as-code, compliance. Each names the Atelier source path, distills first-principles to the citizen-dev-relevant subset, links to agent-checklist triggers, maps to BA.A 5-skill catalog. REQ-222: docs/skills.md index (9-skill table, Atelier provenance, 8 core principles C1-C8, consumption instructions, reference-only domains, excluded domains). PROJECT.md BA.A decision extended with the Atelier-derived skill catalog reference. ---ci--- project: acdl phase: 4 milestone: v1.18 status: execute requirements: covered: [REQ-221, REQ-222] partial: [] ---/ci---
1.6 KiB
1.6 KiB
Skill: DevOps
Atelier source:
domains/devops/(first-principles + ci-cd, environments) Core principles: C5 Reversibility, C7 Observability, C8 Economy BA.A mapping: scheduled job, worker Consumer: read this before any deployment.
First Principles (citizen-developer-relevant subset)
- The pipeline is the process. No manual steps. Every change flows through the same pipeline: contract → resolver → plan → policy → confidence → (HITL gate for qa/prod/dr) → apply → evidence.
- Rollback path is known. Every deployment has a documented rollback. Terraform state is the rollback mechanism; the pipeline replans to the prior state.
- Config is in code, not on the server. Environment variables, SSM parameters, secrets — all declared, versioned, and reviewable. No hand-configured server state.
- Environments are parity. dev = prod modulo data. The same contract deploys to all environments; only the environment field changes.
Agent-Checklist Triggers (§ DevOps)
- The pipeline is the process (no manual steps)
- Rollback path is known
- Config is in code, not on the server
- Environments are parity (dev = prod modulo data)
How Nova Uses This
Nova IS the pipeline. The citizen developer's contract declares intent; Nova provides the process. The DevOps skill tells you what the platform expects from your submission: no manual steps (everything flows through the contract), a known rollback (Terraform state), config in code (SSM SecureString, not hand-configured servers), and environment parity (one contract, four environments).