feat: mine reusable AeroSim channel lessons

2026-09-10 11:41:25 +00:00
parent fad0703294
commit 31088a5ed8
11 changed files with 670 additions and 2 deletions
@@ -1,7 +1,7 @@
 ---
 name: corp-v1-channel-architecture
 description: "Use when operating or synchronizing a Corp v1 project's architecture channel. Maintains C4-based architecture documentation, Draw.io diagrams, architecture decisions, and requirements while correlating verified activity across the project's seven channels."
-version: 1.8.0
+version: 1.9.0
 author: Hermes Agent
 license: MIT
 metadata:
@@ -286,6 +286,25 @@ Requires team approval for:
 - adopting a project-specific `diagrams-drawio` copy;
 - irreversible or high-impact implementation/deployment work.

+
+## Mined Project-Adoption Improvements
+
+## Dedicated Project Channel Workspace
+
+Every project adoption must bind this channel to a dedicated local workspace under the active working root. Keep clones, worktrees, plans, reports, screenshots, generated artifacts, retained logs, and channel inputs inside that channel root. Use run-unique or task-specific children under `workspace/`; keep durable project truth in approved repositories. A local folder boundary organizes execution only—it neither broadens authority nor replaces remote evidence. Delivery adoptions should additionally use a channel-level `cache/` for reusable pinned toolchains and dependencies, while keeping Task evidence isolated by Task.
+
+## Project-Adoption Architecture Lessons
+
+Resolve authority from the active project authorization contract at invocation time; broad delegation never replaces exact-item evidence, safety boundaries, or a later narrower owner decision. Use [references/authority-precedence-and-concurrent-evidence.md](references/authority-precedence-and-concurrent-evidence.md).
+
+For cross-channel handoffs, emit a stable verified packet and let the destination re-check its own entry gates. Process each handoff ID once and return incomplete work without fabricating a lifecycle transition. Follow [references/channel-handoff.md](references/channel-handoff.md).
+
+When Scope and Architecture traceability disagree, preserve Scope-owned Feature identity and product-question dependencies, move Architecture-only findings into clearly proposed technical risks, and repair record coherence without manufacturing solution approval. When task execution, publication, deployment, or acceptance advances, audit every presentation surface and keep Scope lifecycle, solution completeness, implementation approval, task-derived execution, deployment, acceptance, and final version allocation separate. Use [references/multidimensional-lifecycle-presentation-audit.md](references/multidimensional-lifecycle-presentation-audit.md).
+
+An “in sync” Architecture audit must report structural compliance, content completeness, and build/render health separately. Verify current default-branch bytes, exact C4 levels, dedicated FR/NFR registries and readers, reciprocal traceability, task/dependency readiness, editable Draw.io rendering, browser health, and remote readback. Use [references/c4-container-registry-component-views.md](references/c4-container-registry-component-views.md), [references/diagrams-drawio-canonical-compliance.md](references/diagrams-drawio-canonical-compliance.md), and [references/docusaurus-drawio-browser-verification.md](references/docusaurus-drawio-browser-verification.md).
+
+Use RED-first repository contracts for delegated solution packages and task identity, [references/delegated-solution-package-tdd.md](references/delegated-solution-package-tdd.md); classify runner failures separately from repository failures, [references/gitea-actions-evidence-triage.md](references/gitea-actions-evidence-triage.md); and close scheduled evidence races before final reporting, [references/scheduled-sync-evidence-convergence.md](references/scheduled-sync-evidence-convergence.md).
+
 ## Common Pitfalls

 1. Drawing architecture without loading `diagrams-drawio`.