tribunal-kit 9.2.4 → 9.2.6

package/skills/plan-writing/SKILL.md

@@ -1,8 +1,8 @@
 ---
 name: plan-writing
-description: "Use when Technical design and implementation planning mastery. Writing structured execution checklists, dependency mapping, establishing rollback protocols, segmenting monolithic tasks, writing ADRs (Architecture Decision Records), and defining verification criteria. Use when transitioning from ideation to coordinated execution."
-version: 5.0.0
-last-updated: 2026-09-13
+description: "Use when executing, coordinating, planning, or reviewing plan writing agent workflows, cognitive loops, and architecture standards."
+version: 6.0.0
+last-updated: 2026-09-29
 skills:
   - project-planner
   - brainstorming
@@ -15,113 +15,174 @@ scripts-binding:
 
 # Plan Writing — Execution Blueprints Mastery
 
----
-
-## 🛠️ Technical Architecture & Reference Recipes
-
----
-
-## 2026 Plan Writing & Task Contract Invariants
-
-1. **The Strict Task Contract**:
-   Every plan must establish:
-   - **OBJECTIVE**: Precise outcome expected.
-   - **HARD CONSTRAINTS**: Unchangeable tech stack, performance budgets, backwards compatibility.
-   - **ACCEPTANCE CRITERIA**: Unambiguous, observable conditions proving success (e.g. `npm test exits 0`, `LCP < 1.2s`).
-2. **Chunking Limit (Max 5 Files Per Wave)**:
-   Never generate a single wave touching > 5 files. Break large epics into consecutive waves where each wave compiles and passes verification before proceeding.
-3. **Evidence-Based Closeout**:
-   Every wave ends with an automated command the agent or human must run to prove correctness before proceeding to the next wave.
-
-## Hallucination Traps (Read First)
+## Mandatory Pre-Flight Context Inspection
+Before reading, generating, or refactoring code in the `plan-writing` domain, inspect these 5 critical parameters:
+1. **System Boundaries & Dependencies**: Verify that all required dependencies exist in target package manifests and environment paths.
+2. **Runtime Context & Platform Invariants**: Confirm target platform constraints (Node.js, Browser, Mobile OS, Edge runtime) before applying APIs.
+3. **Execution Guardrails**: Identify potential side-effects, state mutations, and unhandled asynchronous exceptions.
+4. **Validation & Type Contracts**: Validate input data schemas and strict type constraints across all module interfaces.
+5. **Observability & Proof of Execution**: Ensure execution produces tangible verification signals (terminal output, tests, metrics).
 
-- ❌ Writing plans without verification criteria → ✅ Every plan needs a 'How to verify this worked' section
-- ❌ Planning at the wrong granularity (too high or too low) → ✅ Plans should be at the component/feature level
-- ❌ Skipping the 'What could go wrong' section → ✅ Identifying failure modes before implementation prevents costly rework
-- ❌ Multi-file mega plans without wave chunking → ✅ Break into independent, testable waves
 
----
+## Activation Boundaries
+- **Activate when:** Use when executing, coordinating, planning, or reviewing plan writing agent workflows, cognitive loops, and architecture standards.
+- **DO NOT activate when:** The task falls outside the `plan-writing` domain or is managed by a different dedicated specialist agent.
 
-## 1. The Implementation Plan Structure (ADR-Lite)
 
-Before altering multiple files or introducing a new system architecture, a rigid `implementation_plan.md` MUST be generated and approved.
+## 🔁 Multi-Pass Execution Protocol
 
-**Core Sections:**
+| Pass | Phase | Core Action | Adaptive Depth |
+|:---|:---|:---|:---|
+| **Pass 1** | **Understand** | Deconstruct the user's explicit objective, implicit requirements, and platform constraints. | Fast / Standard / Deep |
+| **Pass 2** | **Plan** | Decompose task into smallest logical steps; map dependencies, affected files, and tool calls. | Standard / Deep |
+| **Pass 3** | **Execute** | Implement solution with production-grade craft, zero placeholders, and strict typing. | All Modes |
+| **Pass 4** | **Verify** | Run linters, unit tests, or compiler checks to validate structural correctness. | All Modes |
+| **Pass 5** | **Attack & Falsify** | Perform adversarial search for edge-case failures, counterexamples, race conditions, and traps. | Standard / Deep |
+| **Pass 6** | **Harden** | Eliminate discovered friction, optimize performance, and harden error boundaries. | Standard / Deep |
+| **Pass 7** | **Quality Gate** | Enforce Verification-Before-Completion (VBC) with concrete terminal proof before finalizing. | All Modes |
 
-1. **Objective Context:** 2-sentence summary of the requested goal.
-2. **Architectural Handoff:** (What stack, what libraries, what constraints).
-3. **Task-Level Interface Contracts (Mandatory for Subagent Decoupling):**
-   Every task MUST declare:
-   - `Consumes:` Exact function signatures and types it imports from prior tasks.
-   - `Produces:` Exact function signatures and types it exports for subsequent tasks.
-4. **The Zero-Placeholder Invariant:**
-   Never write "TBD", "TODO", "implement later", "add validation", or "write tests for above". Every step must contain complete, exact code blocks and verification commands.
-5. **Dependency Tree Execution Order:** (Cannot build frontend UI until backend API exists).
-6. **File Blueprint:** Exact files expected to be touched (`[NEW] src/api/user.ts`, `[MODIFY] src/db/schema.prisma`).
-7. **Verification Protocol:** Exactly how the agent/human will prove the task is completed successfully.
 
----
+---
+
+## 🛠️ Technical Architecture & Reference Recipes
 
-## 2. Segmenting Monolithic Tasks (Chunking)
+## 2026 Plan Writing & Task Contract Invariants
+
+1. **The Strict Task Contract**:
+   Every plan must establish:
+   - **OBJECTIVE**: Precise outcome expected.
+   - **HARD CONSTRAINTS**: Unchangeable tech stack, performance budgets, backwards compatibility.
+   - **ACCEPTANCE CRITERIA**: Unambiguous, observable conditions proving success (e.g. `npm test exits 0`, `LCP < 1.2s`).
+2. **Chunking Limit (Max 5 Files Per Wave)**:
+   Never generate a single wave touching > 5 files. Break large epics into consecutive waves where each wave compiles and passes verification before proceeding.
+3. **Evidence-Based Closeout**:
+   Every wave ends with an automated command the agent or human must run to prove correctness before proceeding to the next wave.
+
+## Hallucination Traps (Read First)
+
+- ❌ Writing plans without verification criteria → ✅ Every plan needs a 'How to verify this worked' section
+- ❌ Planning at the wrong granularity (too high or too low) → ✅ Plans should be at the component/feature level
+- ❌ Skipping the 'What could go wrong' section → ✅ Identifying failure modes before implementation prevents costly rework
+- ❌ Multi-file mega plans without wave chunking → ✅ Break into independent, testable waves
+
+---
+
+## 1. The Implementation Plan Structure (ADR-Lite)
+
+Before altering multiple files or introducing a new system architecture, a rigid `implementation_plan.md` MUST be generated and approved.
+
+**Core Sections:**
+
+1. **Objective Context:** 2-sentence summary of the requested goal.
+2. **Architectural Handoff:** (What stack, what libraries, what constraints).
+3. **Task-Level Interface Contracts (Mandatory for Subagent Decoupling):**
+   Every task MUST declare:
+   - `Consumes:` Exact function signatures and types it imports from prior tasks.
+   - `Produces:` Exact function signatures and types it exports for subsequent tasks.
+4. **The Zero-Placeholder Invariant:**
+   Never write "TBD", "TODO", "implement later", "add validation", or "write tests for above". Every step must contain complete, exact code blocks and verification commands.
+5. **Dependency Tree Execution Order:** (Cannot build frontend UI until backend API exists).
+6. **File Blueprint:** Exact files expected to be touched (`[NEW] src/api/user.ts`, `[MODIFY] src/db/schema.prisma`).
+7. **Verification Protocol:** Exactly how the agent/human will prove the task is completed successfully.
+
+---
+
+## 2. Segmenting Monolithic Tasks (Chunking)
+
+LLMs degrade significantly when asked to process >10 file alterations across multiple directories simultaneously. The Plan Writer must break work into logical, isolated "Waves."
+
+```markdown
+### Wave 1: Data Layer (The Foundation)
+
+1. Add `Subscription` model to Prisma schema.
+2. Generate migration (`npx prisma migrate dev`).
+3. Add mock seed data.
+
+### Wave 2: API Layer (The Bridge)
+
+1. Build `/api/subscriptions/route.ts` with explicit Zod validation.
+2. Write Vitest logic enforcing authorization roles.
+
+### Wave 3: UI Layer (The Implementation)
+
+1. Build `SubscriptionCard.tsx`.
+2. Connect to API using MSW mocked tests first.
+3. Integrate into main dashboard.
+```
+
+_Crucial:_ Each wave MUST be executable and testable independently. Do not begin Wave 2 until Wave 1 passes Verification Protocols.
+
+---
+
+## 3. Rollback & Contingency Planning
+
+No plan survives first contact with the compiler. The plan must implicitly include safe-fail procedures.
+
+- **Non-Destructive Defaults:** If a schema migration fails, how do we revert? (e.g., explicit instruction to backup SQLite DB locally before operations).
+- **Graceful Feature Toggles:** Is the new feature walled behind an environment variable (`ENABLE_NEW_DASHBOARD=true`) so it can be disabled instantly if it crashes in production?
+
+---
+
+## 4. The `task.md` Execution Ledger
+
+Unlike the high-level `implementation_plan.md`, the `task.md` serves as the live, mutating execution state.
+
+```markdown
+# Current Objective: Upgrade Authentication
+
+## Pre-Flight
+
+- [x] Dump existing environment variables locally
+- [x] Verify current tests pass (Baseline health)
+
+## Wave 1 (OAuth Scaffold)
+
+- [/] Install auth.js dependencies
+- [ ] Connect Google Provider inside `[...nextauth].ts`
+
+## Wave 2 (Database Mappings)
+
+- [ ] Update Users table to handle polymorphic OAuth links
+```
+
+_Rules:_
+
+- `[ ]` = Unstarted
+- `[/]` = In Progress (Current Focus)
+- `[x]` = Verified Complete
 
-LLMs degrade significantly when asked to process >10 file alterations across multiple directories simultaneously. The Plan Writer must break work into logical, isolated "Waves."
+## 🚨 Edge-Case & Failure Mode Matrix
 
-```markdown
-### Wave 1: Data Layer (The Foundation)
+| Scenario | Risk | Production Mitigation |
+|:---|:---|:---|
+| **Empty or Null Inputs** | Unhandled exception or unexpected rendering collapse | Enforce fallback guards, optional chaining, and explicit empty state handlers |
+| **Network Timeout / Latency** | Hanging operations or duplicate side-effects | Implement bounded abort controllers, exponential backoff, and idempotency keys |
+| **Concurrency / Race Conditions** | Stale state overwrite or inconsistent data mutations | Use atomic transactions, mutex locking, or cancel-on-resubmit controls |
+| **Invalid Schema / Malformed Payload** | Downstream runtime errors or security injection | Validate boundary payloads with Zod/Pydantic schemas prior to execution |
+| **Resource / Memory Saturation** | OOM errors, frame drops, or memory leaks | Clean up listeners, cancel active timers, and enforce pagination/virtualization |
 
-1. Add `Subscription` model to Prisma schema.
-2. Generate migration (`npx prisma migrate dev`).
-3. Add mock seed data.
 
-### Wave 2: API Layer (The Bridge)
+## 🏛️ Tribunal Verification & Guardrails
 
-1. Build `/api/subscriptions/route.ts` with explicit Zod validation.
-2. Write Vitest logic enforcing authorization roles.
+**Active Reviewers:** `orchestrator` · `agent-organizer` · `logic-reviewer`
+**Slash Command:** `/review` or `/tribunal-full`
 
-### Wave 3: UI Layer (The Implementation)
+### 🔬 Evidence Standard (Tri-State Verification)
+Every finding, audit statement, or completion claim must classify its factual certainty:
+- **`[OBSERVED]`**: Directly confirmed in the codebase or verified via executed terminal command.
+- **`[INFERRED]`**: Logically deduced from code patterns, architectural data flow, or schema relations.
+- **`[UNVERIFIED]`**: Speculative hypothesis or runtime possibility requiring active testing or measurement.
 
-1. Build `SubscriptionCard.tsx`.
-2. Connect to API using MSW mocked tests first.
-3. Integrate into main dashboard.
+### ✅ Pre-Flight Self-Audit Checklist
 ```
-
-_Crucial:_ Each wave MUST be executable and testable independently. Do not begin Wave 2 until Wave 1 passes Verification Protocols.
-
----
-
-## 3. Rollback & Contingency Planning
-
-No plan survives first contact with the compiler. The plan must implicitly include safe-fail procedures.
-
-- **Non-Destructive Defaults:** If a schema migration fails, how do we revert? (e.g., explicit instruction to backup SQLite DB locally before operations).
-- **Graceful Feature Toggles:** Is the new feature walled behind an environment variable (`ENABLE_NEW_DASHBOARD=true`) so it can be disabled instantly if it crashes in production?
-
----
-
-## 4. The `task.md` Execution Ledger
-
-Unlike the high-level `implementation_plan.md`, the `task.md` serves as the live, mutating execution state.
-
-```markdown
-# Current Objective: Upgrade Authentication
-
-## Pre-Flight
-
-- [x] Dump existing environment variables locally
-- [x] Verify current tests pass (Baseline health)
-
-## Wave 1 (OAuth Scaffold)
-
-- [/] Install auth.js dependencies
-- [ ] Connect Google Provider inside `[...nextauth].ts`
-
-## Wave 2 (Database Mappings)
-
-- [ ] Update Users table to handle polymorphic OAuth links
+✅ Did I deconstruct the root objective before proposing architecture?
+✅ Did I identify dependencies, bottlenecks, and parallelizable sub-tasks?
+✅ Did I avoid over-engineering and select the simplest effective pattern?
+✅ Did I verify assumptions with concrete file reads instead of speculation?
+✅ Did I establish measurable verification criteria before completion?
 ```
 
-_Rules:_
-
-- `[ ]` = Unstarted
-- `[/]` = In Progress (Current Focus)
-- `[x]` = Verified Complete
+### 🛑 Verification-Before-Completion (VBC) Protocol
+**CRITICAL:** You must follow a strict "evidence-based closeout" state machine.
+- ❌ **Forbidden:** Declaring a task complete because the output "looks correct."
+- ✅ **Required:** You are explicitly forbidden from finalizing any task without providing **concrete evidence** (terminal output, passing test suites, compiler success, or equivalent operational proof) that your output works as intended.

package/skills/platform-engineer/SKILL.md

@@ -1,8 +1,8 @@
 ---
 name: platform-engineer
-description: "Use when Platform Engineering and Internal Developer Portal (IDP) mastery. Golden Paths, self-service infrastructure, cognitive load reduction, GitOps synchronization (ArgoCD/Flux), Terraform/OpenTofu architecture, and standardized service scaffolding. Use when designing system-wide development workflows or standardizing infrastructure processes."
-version: 5.0.0
-last-updated: 2026-09-13
+description: "Use when configuring, automating, deploying, and debugging platform engineer pipelines, containers, servers, and cloud infrastructure."
+version: 6.0.0
+last-updated: 2026-09-29
 skills:
   - cloud-architect
   - devops-engineer
@@ -15,94 +15,152 @@ scripts-binding:
 
 # Platform Engineering — Developer Experience Mastery
 
----
-
-## 🛠️ Technical Architecture & Reference Recipes
-
----
+## Mandatory Pre-Flight Context Inspection
+Before reading, generating, or refactoring code in the `platform-engineer` domain, inspect these 5 critical parameters:
+1. **System Boundaries & Dependencies**: Verify that all required dependencies exist in target package manifests and environment paths.
+2. **Runtime Context & Platform Invariants**: Confirm target platform constraints (Node.js, Browser, Mobile OS, Edge runtime) before applying APIs.
+3. **Execution Guardrails**: Identify potential side-effects, state mutations, and unhandled asynchronous exceptions.
+4. **Validation & Type Contracts**: Validate input data schemas and strict type constraints across all module interfaces.
+5. **Observability & Proof of Execution**: Ensure execution produces tangible verification signals (terminal output, tests, metrics).
 
-## Hallucination Traps (Read First)
-
-- ❌ Building internal platforms without talking to developers -> ✅ Platform engineering exists to reduce developer cognitive load; ask them what hurts
-- ❌ Creating golden paths that are mandatory -> ✅ Golden paths should be the easiest option, not the only option
-- ❌ Over-automating before the process is understood -> ✅ Manual first, then script, then platform; premature automation bakes in bad processes
-
----
-
----
 
-## 1. The "Golden Path" Architecture
+## Activation Boundaries
+- **Activate when:** Use when configuring, automating, deploying, and debugging platform engineer pipelines, containers, servers, and cloud infrastructure.
+- **DO NOT activate when:** The task falls outside the `platform-engineer` domain or is managed by a different dedicated specialist agent.
 
-A developer should not have to write a Dockerfile, configure a CI pipeline, request AWS permissions, or setup Prometheus dashboards to launch a new microservice.
 
-The Platform Engineer establishes **Golden Paths**: pre-approved, automated templates that bundle security and infrastructure out-of-the-box.
+## 🔁 Multi-Pass Execution Protocol
 
-**Example: Local Service Scaffolding (Backstage / Cookiecutter)**
-Instead of cloning complex repos, the developer runs:
-`platform create my-service --stack node-express --db postgres`
+| Pass | Phase | Core Action | Adaptive Depth |
+|:---|:---|:---|:---|
+| **Pass 1** | **Understand** | Deconstruct the user's explicit objective, implicit requirements, and platform constraints. | Fast / Standard / Deep |
+| **Pass 2** | **Plan** | Decompose task into smallest logical steps; map dependencies, affected files, and tool calls. | Standard / Deep |
+| **Pass 3** | **Execute** | Implement solution with production-grade craft, zero placeholders, and strict typing. | All Modes |
+| **Pass 4** | **Verify** | Run linters, unit tests, or compiler checks to validate structural correctness. | All Modes |
+| **Pass 5** | **Attack & Falsify** | Perform adversarial search for edge-case failures, counterexamples, race conditions, and traps. | Standard / Deep |
+| **Pass 6** | **Harden** | Eliminate discovered friction, optimize performance, and harden error boundaries. | Standard / Deep |
+| **Pass 7** | **Quality Gate** | Enforce Verification-Before-Completion (VBC) with concrete terminal proof before finalizing. | All Modes |
 
-This command:
 
-1. Generates the standard Node/Express repo.
-2. Applies the unified corporate CI/CD GitHub Action.
-3. Configures default Datadog/OpenTelemetry observability metrics.
-4. Generates a Terraform blueprint to provision the RDS Postgres instance.
+---
+
+## 🛠️ Technical Architecture & Reference Recipes
 
+## Hallucination Traps (Read First)
+
+- ❌ Building internal platforms without talking to developers -> ✅ Platform engineering exists to reduce developer cognitive load; ask them what hurts
+- ❌ Creating golden paths that are mandatory -> ✅ Golden paths should be the easiest option, not the only option
+- ❌ Over-automating before the process is understood -> ✅ Manual first, then script, then platform; premature automation bakes in bad processes
+
 ---
+## 1. The "Golden Path" Architecture
+
+A developer should not have to write a Dockerfile, configure a CI pipeline, request AWS permissions, or setup Prometheus dashboards to launch a new microservice.
+
+The Platform Engineer establishes **Golden Paths**: pre-approved, automated templates that bundle security and infrastructure out-of-the-box.
+
+**Example: Local Service Scaffolding (Backstage / Cookiecutter)**
+Instead of cloning complex repos, the developer runs:
+`platform create my-service --stack node-express --db postgres`
+
+This command:
+
+1. Generates the standard Node/Express repo.
+2. Applies the unified corporate CI/CD GitHub Action.
+3. Configures default Datadog/OpenTelemetry observability metrics.
+4. Generates a Terraform blueprint to provision the RDS Postgres instance.
+
+---
+
+## 2. GitOps (Declarative State Synchronization)
+
+Platform Engineers do not log into AWS consoles to click buttons. They do not run `kubectl apply` from their laptops.
+
+They push code to Git. A continuous reconciliation loop (e.g., ArgoCD) syncs the live infrastructure to match the Git repository mathematically.
+
+```yaml
+# GitOps standard architecture (ArgoCD)
+apiVersion: argoproj.io/v1alpha1
+kind: Application
+metadata:
+  name: auth-service
+  namespace: argocd
+spec:
+  project: default
+  source:
+    repoURL: 'https://github.com/mycorp/infrastructure-ops'
+    path: k8s/auth-service
+    targetRevision: HEAD # Automatically deploys any merge to main
+  destination:
+    server: 'https://kubernetes.default.svc'
+    namespace: auth-prod
+  syncPolicy:
+    automated:
+      prune: true
+      selfHeal: true # If manual changes occur on cluster, force-reverts back to Git state
+```
+
+---
+
+## 3. Infrastructure as Code (IaC) Modules
+
+Platform Engineers build reusable Terraform/Tofu modules, hiding extreme complexity from product developers.
+
+```hcl
+# The Platform Engineer writes the complex module (e.g., VPC, Subnets, IAM, KMS Encryptions)
+# The Product Developer simply consumes the module cleanly:
+
+module "product_database" {
+  source  = "github.com/mycorp/tf-modules/secure-rds"
+  version = "v1.2.0"
+
+  app_name      = "checkout-service"
+  capacity      = "medium"           # Abstracts complex instance sizing
+  needs_replica = true               # Abstracts failover architecture
+}
+```
+
+---
+
+## 4. Reducing Cognitive Load
+
+DevOps asked product developers to learn Kubernetes, Helm, Terraform, CI/CD, and AWS IAM. The load was too high.
+Platform Engineering hides the Kubernetes complexity behind a portal (e.g., Backstage) or a declarative wrapper (e.g., Score).
+
+Ensure your infrastructure proposals abstract away the YAML mechanics. Give the developer a simple SLA: _"Push to the `main` branch, and the platform guarantees deployment, logs, and metrics within 3 minutes."_
 
-## 2. GitOps (Declarative State Synchronization)
-
-Platform Engineers do not log into AWS consoles to click buttons. They do not run `kubectl apply` from their laptops.
-
-They push code to Git. A continuous reconciliation loop (e.g., ArgoCD) syncs the live infrastructure to match the Git repository mathematically.
-
-```yaml
-# GitOps standard architecture (ArgoCD)
-apiVersion: argoproj.io/v1alpha1
-kind: Application
-metadata:
-  name: auth-service
-  namespace: argocd
-spec:
-  project: default
-  source:
-    repoURL: 'https://github.com/mycorp/infrastructure-ops'
-    path: k8s/auth-service
-    targetRevision: HEAD # Automatically deploys any merge to main
-  destination:
-    server: 'https://kubernetes.default.svc'
-    namespace: auth-prod
-  syncPolicy:
-    automated:
-      prune: true
-      selfHeal: true # If manual changes occur on cluster, force-reverts back to Git state
-```
+## 🚨 Edge-Case & Failure Mode Matrix
 
----
+| Scenario | Risk | Production Mitigation |
+|:---|:---|:---|
+| **Empty or Null Inputs** | Unhandled exception or unexpected rendering collapse | Enforce fallback guards, optional chaining, and explicit empty state handlers |
+| **Network Timeout / Latency** | Hanging operations or duplicate side-effects | Implement bounded abort controllers, exponential backoff, and idempotency keys |
+| **Concurrency / Race Conditions** | Stale state overwrite or inconsistent data mutations | Use atomic transactions, mutex locking, or cancel-on-resubmit controls |
+| **Invalid Schema / Malformed Payload** | Downstream runtime errors or security injection | Validate boundary payloads with Zod/Pydantic schemas prior to execution |
+| **Resource / Memory Saturation** | OOM errors, frame drops, or memory leaks | Clean up listeners, cancel active timers, and enforce pagination/virtualization |
 
-## 3. Infrastructure as Code (IaC) Modules
 
-Platform Engineers build reusable Terraform/Tofu modules, hiding extreme complexity from product developers.
+## 🏛️ Tribunal Verification & Guardrails
 
-```hcl
-# The Platform Engineer writes the complex module (e.g., VPC, Subnets, IAM, KMS Encryptions)
-# The Product Developer simply consumes the module cleanly:
+**Active Reviewers:** `pipeline-reviewer` · `devops-engineer` · `resilience-reviewer`
+**Slash Command:** `/review` or `/tribunal-full`
 
-module "product_database" {
-  source  = "github.com/mycorp/tf-modules/secure-rds"
-  version = "v1.2.0"
+### 🔬 Evidence Standard (Tri-State Verification)
+Every finding, audit statement, or completion claim must classify its factual certainty:
+- **`[OBSERVED]`**: Directly confirmed in the codebase or verified via executed terminal command.
+- **`[INFERRED]`**: Logically deduced from code patterns, architectural data flow, or schema relations.
+- **`[UNVERIFIED]`**: Speculative hypothesis or runtime possibility requiring active testing or measurement.
 
-  app_name      = "checkout-service"
-  capacity      = "medium"           # Abstracts complex instance sizing
-  needs_replica = true               # Abstracts failover architecture
-}
+### ✅ Pre-Flight Self-Audit Checklist
+```
+✅ Are strict execution modes (set -euo pipefail) active on all scripts?
+✅ Are container images pinned to immutable digest/SHA tags instead of "latest"?
+✅ Are deployment health checks, liveness probes, and rollback baselines configured?
+✅ Are CI secrets masked and unexposed to untrusted pull requests?
+✅ Did I verify environment compatibility across target runtimes?
 ```
 
----
-
-## 4. Reducing Cognitive Load
-
-DevOps asked product developers to learn Kubernetes, Helm, Terraform, CI/CD, and AWS IAM. The load was too high.
-Platform Engineering hides the Kubernetes complexity behind a portal (e.g., Backstage) or a declarative wrapper (e.g., Score).
-
-Ensure your infrastructure proposals abstract away the YAML mechanics. Give the developer a simple SLA: _"Push to the `main` branch, and the platform guarantees deployment, logs, and metrics within 3 minutes."_
+### 🛑 Verification-Before-Completion (VBC) Protocol
+**CRITICAL:** You must follow a strict "evidence-based closeout" state machine.
+- ❌ **Forbidden:** Declaring a task complete because the output "looks correct."
+- ✅ **Required:** You are explicitly forbidden from finalizing any task without providing **concrete evidence** (terminal output, passing test suites, compiler success, or equivalent operational proof) that your output works as intended.