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---
38 lines
1.6 KiB
Markdown
38 lines
1.6 KiB
Markdown
# Skill: Observability
|
|
|
|
> **Atelier source:** `domains/observability/` (first-principles + logging,
|
|
> metrics, tracing)
|
|
> **Core principles:** C7 Observability
|
|
> **BA.A mapping:** basic observability bootstrap
|
|
> **Consumer:** read this before any production submission (W3.E requires
|
|
> `dashboard` + `oncall` for prod).
|
|
|
|
## First Principles (citizen-developer-relevant subset)
|
|
|
|
- **Logs are structured.** JSON with fields, not free-form text. Every
|
|
log line carries a timestamp, level, message, and context fields.
|
|
- **Every request has a correlation ID.** A request ID propagates from
|
|
ingress through every downstream call. Logs, metrics, and traces share
|
|
the same ID.
|
|
- **No high-cardinality labels in metrics.** User IDs, request IDs, and
|
|
other unbounded values go in logs/traces, not metric labels.
|
|
- **Alerts have runbooks.** Every alert links to a runbook
|
|
(`runbook` field in the submission, W3.E prod mandatory) that explains
|
|
what to do when it fires.
|
|
|
|
## Agent-Checklist Triggers (§ Observability)
|
|
|
|
- Logs are structured (JSON, fields)
|
|
- Every request has a correlation ID
|
|
- No high-cardinality labels in metrics
|
|
- Alerts have runbooks
|
|
|
|
## How Nova Uses This
|
|
|
|
The W3.E per-env mandatory table requires `runbook` + `dashboard` +
|
|
`oncall` for `prod` submissions — the submission-readiness gate enforces
|
|
this. The observability skill tells you what those artifacts must contain:
|
|
structured logs, correlation IDs, bounded metric labels, and runbook-linked
|
|
alerts. Nova provides the infrastructure (CloudWatch, the uptime
|
|
monitor); you provide the application-level observability (structured
|
|
logs, dashboards, runbooks). |