Personal Language Key (PLK)
Relevant source files
The following files were used as context for generating this wiki page:
The Personal Language Key (PLK) is a system component within GestaltView that translates human-specific idioms, metaphors, and language patterns into executable code structures. It allows the platform to maintain a user's unique linguistic context while interacting with digital intelligences and automated workflows. Sources: diagram_inventory.json:1159-1160
The PLK operates as part of the "Intelligence and Orchestration" layer. It ensures that system outputs remain authentically aligned with the user’s personal voice rather than reverting to generic Large Language Model (LLM) prose. Sources: diagram_inventory.json:1161-1163
Architecture and Data Flow
The PLK functions as a bridge between "Natural Language Space" and "Code Entity Space." It captures user-specific linguistic data during onboarding and stores it within embodiment schemas located in the shared/ and api/embodiment directories. Sources: diagram_inventory.json:1161-1162
Translation Pipeline
The translation process follows a specific pipeline that moves from raw human expression to structured intent classification.
The diagram shows how user idioms are processed through diagnostic tools like toneGuard.ts to update the embodiment schema. Sources: diagram_inventory.json:1166-1172
Key Components and Logic
The PLK relies on several core backend entities to process and enforce linguistic consistency.
| Component | Responsibility | Relevant Files |
|---|---|---|
| Profile Ingestion | Initializes PLK profiles during user onboarding. | shared/, api/embodiment |
| Tone Guard | Evaluates generated responses against the PLK profile to ensure authenticity. | server/core/toneGuard.ts |
| Intent Classifier | Maps human metaphors to specific system actions or intents. | shared/orchestration/intentClassifier.ts |
| Embodiment Schema | Stores the persistent state of the user's linguistic preferences. | shared/embodiment/ |
Sources: diagram_inventory.json:1161-1164
State Hydration
During the orchestration of a request, the system performs "State Hydration." This process pulls the user's identity, active memory frames, and specific PLK parameters before dispatching the request to the LLM router. This ensures the LLM has the necessary context to generate a response that matches the user's "Personal Language Key." Sources: diagram_inventory.json:626-628
Integration with Orchestration
The PLK is tightly integrated with the Orchestration API. When a request is processed, the PLK parameters act as a constraint or guide for the specialized Digital Intelligences (DIs).
The sequence illustrates the hydration of PLK parameters into the orchestration flow. Sources: diagram_inventory.json:626-630, diagram_inventory.json:1161-1163
Summary
The Personal Language Key (PLK) provides the architectural infrastructure for linguistic continuity in GestaltView. By mapping personal metaphors to code entities and utilizing diagnostic tools like Tone Guard, the system prevents the loss of individual context during AI-assisted creation and communication. Sources: diagram_inventory.json:1160-1164, build_story_artifact.py:85-87