@rasensio/aidlc-content 1.18.0 → 1.19.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/package.json +1 -1
- package/skills/60-deployment.md +11 -3
package/package.json
CHANGED
package/skills/60-deployment.md
CHANGED
|
@@ -39,12 +39,20 @@ deployment checklist.
|
|
|
39
39
|
- Deployment steps in order
|
|
40
40
|
- Rollback procedure
|
|
41
41
|
- Monitoring and verification steps post-deploy
|
|
42
|
-
4. **
|
|
42
|
+
4. **Update the affected topic page in `docs/`.** If this instance changed how a documented topic
|
|
43
|
+
behaves — its interface, its failure modes, or the reason it is built the way it is — update that
|
|
44
|
+
topic's page before releasing, and say in the deployment artifact which page you touched or that
|
|
45
|
+
none applied. The manifest at `docs/index.yaml` maps each topic to the code it documents, so
|
|
46
|
+
start there to find the page. A design reason bought with a bugfix belongs in the page's "why"
|
|
47
|
+
section: the knowledge graph records what the code looks like and cannot afford to record why, so
|
|
48
|
+
a reason that lives nowhere else is one the next agent will simplify away. This is a checklist
|
|
49
|
+
step, not a gate — no phase is blocked on it.
|
|
50
|
+
5. **Pre-deployment checks.** Verify:
|
|
43
51
|
- CI pipeline passes
|
|
44
52
|
- No critical findings open from adversarial reviews
|
|
45
53
|
- Dependencies are pinned and audited
|
|
46
|
-
|
|
47
|
-
|
|
54
|
+
6. **Execute deployment.** Follow the release plan step by step.
|
|
55
|
+
7. **Verify.** Confirm the deployment succeeded using the monitoring steps.
|
|
48
56
|
|
|
49
57
|
## Exit Criteria
|
|
50
58
|
|