docs: promote reusable AeroSim channel lessons

This commit is contained in:
jarvis-at-skic committed 2026-10-20 18:42:43 +00:00
1 parent e8507ad718
commit 26cbf12bc6
5 files changed
+113 -24

No files matched your search

@@ -9,9 +9,9 @@ Use this when a project documentation site has authoritative Scope and Architect
3. Add a dedicated Docusaurus docs plugin for `kanban/`, with its own `sidebarsKanban.ts`.
4. Place the top-level Kanban navigation item immediately after Architecture and add `/kanban` to documentation search indexing.
5. Add exactly two sidebar entries in this order: Board, Focus.
6. Populate Board from authoritative unfinished Epic and Feature records only. Map detailed lifecycle states deterministically to `InIdeation`, `InBacklog`, `InProgress`, or `ToBeReleased` without changing source state.
7. Populate Focus only from qualifying `InBacklog`, `InProgress`, or `ToBeReleased` evidence. An empty Focus is correct when no item qualifies; state the exact missing approval, dependency, task-definition, or execution evidence.
8. Never create placeholder tasks to make Focus appear populated. A task needs a stable Architecture-owned ID, parent hierarchy, Feature implementation approval, and explicit exact-task human Focus admission.
6. Populate Board from authoritative unfinished Epic and Feature records only. Map detailed lifecycle states deterministically to `InIdeation`, `InBacklog`, `ReadyForDelivery`, `InProgress`, or `ToBeReleased` without changing source state.
7. Populate Focus only from qualifying `InBacklog`, `ReadyForDelivery`, `InProgress`, or `ToBeReleased` evidence. An empty Focus is correct when no item qualifies; state the exact missing approval, dependency, task-definition, or execution evidence.
8. Never create placeholder tasks to make Focus appear populated. A planned task needs a stable canonical ID and parent hierarchy. `ReadyForDelivery` additionally requires Feature implementation approval, satisfied readiness checks, and explicit exact-task human admission; backlog visibility is not executable admission.
## Recommended structural validator
@@ -19,10 +19,10 @@ Add a repository validation script and include it in the main validation command
- Kanban plugin, search route, and top-level navigation order;
- dedicated sidebar containing Board then Focus;
- all four allowed Board columns;
- all five allowed Board columns;
- all known unfinished Epic/Feature IDs appear exactly as intended;
- no card has a terminal authoritative source status;
- Focus exposes only `InBacklog`, `InProgress`, and `ToBeReleased` sections;
- Focus exposes only `InBacklog`, `ReadyForDelivery`, `InProgress`, and `ToBeReleased` sections;
- Focus preserves the exact-task human admission rule.
Avoid naïve substring checks when explanatory prose names excluded states. Validate headings or structured fields instead—for example, reject an `## InIdeation` Focus section rather than rejecting every occurrence of the word `InIdeation`.