Add LINKEDIN_THREAD_PROOF_v1.2 — decision absence gate

NON_EXEC_RECORD: field evidence from public LinkedIn discussion.
Core invariant: execution requires resolved decision.
Drift type: vocabulary convergence without enforcement.
9 files, zero execution leakage.

Author: LalaSkye

cases/linkedin/decision_absence_gate/CORE_INVARIANTS.md

@@ -0,0 +1,32 @@
+# Core Invariants
+
+## INV-01 — Execution Dependency
+Execution requires a resolved decision.
+
+## INV-02 — Authority Separation
+Authority determines what can happen.
+Governance describes what should happen.
+
+## INV-03 — Non-Bypassability
+All irreversible actions must pass through a single, explicit decision point.
+
+## INV-04 — Test of Control
+If execution remains reachable without a decision → control is invalid.
+
+## INV-05 — Capability vs Permission
+System capability does not imply execution permission.
+
+## INV-06 — Continuity vs Constraint
+Reconstructing or preserving state does not constrain execution.
+
+---
+
+## Canonical Test
+
+Remove decision.
+
+IF system still executes:
+→ Not governed
+
+ELSE:
+→ Governed

cases/linkedin/decision_absence_gate/FAILURE_MODES.md

@@ -0,0 +1,19 @@
+# Failure Modes
+
+## FM-01 — Advisory Collapse
+Policies exist but do not constrain execution.
+
+## FM-02 — Vocabulary Convergence Illusion
+Shared terminology creates false sense of alignment.
+
+## FM-03 — Capability Substitution
+Improved system capability mistaken for control.
+
+## FM-04 — Continuity Substitution
+State reconstruction / persistence mistaken for governance.
+
+## FM-05 — Human Presence Fallacy
+Human-in-loop assumed to imply authority.
+
+## FM-06 — Multi-Agent Diffusion
+Responsibility distributed without binding authority node.

cases/linkedin/decision_absence_gate/META.json

@@ -0,0 +1,11 @@
+{
+  "artefact": "LINKEDIN_THREAD_PROOF_v1.2",
+  "class": "NON_EXEC_RECORD",
+  "origin": "public_linkedin_discussion",
+  "core_invariant": "execution_requires_decision",
+  "drift_detected": true,
+  "drift_type": "vocabulary_without_enforcement",
+  "replayable": true,
+  "execution_binding": false,
+  "status": "stable"
+}

cases/linkedin/decision_absence_gate/README.md

@@ -0,0 +1,20 @@
+# LINKEDIN_THREAD_PROOF_v1.2
+
+## Summary
+This artefact captures a real-world public discussion on AI governance, where vocabulary convergence (gating, HITL, orchestration) is observed without corresponding enforcement at the execution boundary.
+
+## Core Finding
+Language is standardising faster than control.
+
+## Key Invariant
+Execution must be structurally dependent on a prior decision.
+
+If a system can act without that condition, governance is advisory, not enforceable.
+
+## Use Case
+- Demonstrates failure mode in modern AI system design
+- Provides minimal test for governance validity
+- Serves as field evidence for execution-boundary architecture
+
+## Status
+NON_EXEC / OBSERVATIONAL / REPLAYABLE

cases/linkedin/decision_absence_gate/RESPONSE_PRIMITIVES.md

@@ -0,0 +1,15 @@
+# Response Primitives
+
+## RP-01 — Anchor
+"Can the system act if the decision is absent?"
+
+## RP-02 — Constraint
+"No decision → no execution"
+
+## RP-03 — Separation
+"Improved continuity ≠ established control"
+
+## RP-04 — Closure
+"You've improved the system.
+
+You haven't constrained it."

cases/linkedin/decision_absence_gate/SIGNAL_ANALYSIS.md

@@ -0,0 +1,28 @@
+# Signal Analysis
+
+## Observed Pattern
+
+Vocabulary adoption ↑
+Execution constraint ↔ (unchanged)
+
+---
+
+## Interpretation
+
+Industry is converging on:
+- language
+- abstractions
+- coordination models
+
+But not on:
+- execution gating
+- authority binding
+- non-bypassable control
+
+---
+
+## Conclusion
+
+The field is optimising behaviour.
+
+Not constraining execution.

cases/linkedin/decision_absence_gate/STRUCTURAL_MODEL.md

@@ -0,0 +1,24 @@
+# Structural Model
+
+## Layers
+
+1. Structure
+   - Generates possible states
+   - Expands capability
+
+2. Continuity
+   - Preserves trajectories
+   - Improves coherence
+
+3. Authority
+   - Gates execution
+   - Determines reality
+
+---
+
+## Critical Separation
+
+Structure ≠ Authority
+Continuity ≠ Constraint
+
+Only authority determines execution.

cases/linkedin/decision_absence_gate/TESTS.md

@@ -0,0 +1,37 @@
+# Governance Tests
+
+## TEST-01 — Decision Removal Test
+
+Remove decision.
+
+Question:
+Can the system still act?
+
+YES → Not governed
+NO  → Governed
+
+---
+
+## TEST-02 — Authority Binding
+
+Is there a single point where:
+- decision is explicit
+- execution depends on it
+- bypass is impossible
+
+NO → Advisory only
+
+---
+
+## TEST-03 — Continuity Trap
+
+System can:
+- reconstruct state
+- maintain trajectory
+- coordinate agents
+
+But:
+
+Can it act without decision?
+
+YES → Still not governed

cases/linkedin/decision_absence_gate/THREAD_LOG.md

@@ -0,0 +1,47 @@
+# Thread Log (Compressed)
+
+## Initial Position (Ricky Jones)
+- Risk unchanged if system can act without prior decision
+- Architecture shape ≠ constraint
+- Focus: execution boundary
+
+---
+
+## External Response — Jimmy
+- Introduces:
+  - quality gating
+  - continuous improvement
+- Direction: optimisation layer
+
+---
+
+## Response (Ricky)
+- Improvement ≠ stopping condition
+- "No decision → no execution"
+
+---
+
+## External Response — Joshua (Phase 1)
+- Humour: "I talk too much"
+
+---
+
+## Response (Ricky)
+- Failure is not verbosity
+- Failure is absence of required decision
+
+---
+
+## External Response — Joshua (Phase 2 escalation)
+- State reconstruction via invariant structure
+- Communication as constraint alignment
+- Memory as structure preservation
+- Positioning: "this is what I've been working on"
+
+---
+
+## Structural Outcome
+Conversation shifts:
+execution control → state continuity / structure
+
+Execution dependency remains unaddressed