To ensure you can copy the raw text for Claude, here is the framework presented in a **code block**. This prevents the interface from rendering the Markdown and allows you to capture the formatting exactly as intended for another LLM.

```markdown
# Pillars: Symbolic Process Guidance (FABRIC & FLOW)

## Overview
This framework replaces "guardrails"—which implies restrictive policing—with **Symbolic Process Guidance**. It treats the LLM as a **sophisticated operator** navigating a structural map to ensure deterministic technical outcomes in a fluid development environment.

---

## 1. The FABRIC (Static Capabilities)
The FABRIC represents the material reality of the system—the stable set of methods and structural primitives available.

*   **VIVIFY:** Intelligent instantiation. The transition from loose intent (JSON) to structured, "living" objects (Perl-style hashes).
*   **SECRECY:** The hardening layer. Internal data privacy and encryption applied to the payload, independent of the transport layer.
*   **PAYLOAD:** The symmetric lifecycle container. A "vessel" managing the state from pre-processing and sending to receiving and disassembly.
*   **FREEZE:** Stabilization through serialization. Ensures complex, encrypted objects remain intact and maintain integrity during transit.
*   **SERVER:** The final distillation and anchoring. Strips packaging layers, separates blobs, and anchors data via symbolic links.

---

## 2. The FLOW (Dynamic Orchestration)
If FABRIC is the loom, FLOW is the **threading**. It represents the dynamic path data takes through FABRIC capabilities for a specific mission.

### **Example: Secret-Server Storage Flow**
1.  **Assembly:** VIVIFY + SECRECY (Creating a hardened intelligence).
2.  **Stabilization:** FREEZE (Preparing the structure for movement).
3.  **Transit:** PAYLOAD Send (The SSH-wrapped vessel moving via IP).
4.  **Extraction:** PAYLOAD Receive + SERVER (Disassembly, stripping "Ply," and archival).

---

## 3. The Guidance Layer: TENSIONING
To maintain structural integrity without "guardrails," we use **Tensioning**. This is the act of adjusting the "tightness" of constraints to keep the FLOW from "bunching or fraying".

*   **Function:** Tensioning ensures that **SECRECY** and **FREEZE** are applied with enough precision that the data survives transit.
*   **Application:** If the "tension" is incorrect, it results in a **validation failure** (the FABRIC "bunches up").
*   **Goal:** To move from "don't do X" to "ensure the logic is tight enough to traverse the next FABRIC gate".

---

## 4. Design Philosophy: Static vs. Dynamic
*   **FABRIC (Static):** Defines **what exists** (the tools on the shelf).
*   **FLOW (Dynamic):** Defines **what happens** (the sequence and intent of the mission).
*   **The Symbol Rule:** One symbol maps to one concept, and one concept maps to one behavior. This ensures the symbolic layer supports clarity rather than "decorative" metaphors.
```