| # Glyphic Envelope Specification | |
| The Glyphic Envelope defines the **structured message format** used by agents, LLMs, and the Glyphic Runtime. It wraps raw text, internal state, safety constraints, and response protocols into a single deterministic structure. | |
| The envelope is divided into ordered sections. Each section begins with a header: | |
| Each section contains: | |
| - CTX.* glyphs (machine-readable) | |
| - Optional raw text (user input, memory summaries, etc.) | |
| --- | |
| ## 1. Envelope Sections | |
| ### 1.1 USER_INPUT | |
| Represents the raw user message. | |
| --- | |
| ### 1.2 IDENTITY | |
| Represents the agent’s identity, role, and persona. | |
| --- | |
| ### 1.3 INTERNAL_STATE | |
| Represents the agent’s current internal state. | |
| --- | |
| ### 1.4 INTENT | |
| Represents the agent’s goal, urgency, and focus. | |
| --- | |
| ### 1.5 BEHAVIOR | |
| Represents the agent’s tone, pacing, depth, style, and clarity. | |
| --- | |
| ### 1.6 MEMORY | |
| Represents short-term memory summaries. | |
| --- | |
| ### 1.7 THOUGHT_CHAIN | |
| Represents internal reasoning summaries. | |
| --- | |
| ### 1.8 SAFETY | |
| Represents global safety constraints. | |
| --- | |
| ### 1.9 RESPONSE_PROTOCOL | |
| Represents how the agent should respond. | |
| --- | |
| ## 2. Ordering Rules | |
| The envelope must appear in the exact order listed above. | |
| Sections may not be omitted unless empty. | |
| --- | |
| ## 3. Purpose | |
| The envelope ensures: | |
| - deterministic parsing | |
| - stable training | |
| - safe responses | |
| - consistent behavior | |
| - agent-to-agent interoperability | |