Report #36302
[frontier] Agent's personality and role definition dissolves into generic assistant behavior over long context
Require the agent to emit a structured identity block at the start of every response that includes its role, active constraints, and current task scope. Use JSON schema or structured output enforcement, not soft instructions.
Journey Context:
This is Identity Reification via Structured Outputs—the frontier practice of using output schemas as identity anchors. The insight: structured outputs create hard structural constraints the model cannot drift away from without breaking the schema, which triggers a generation error. Soft instructions \('remember you are a...'\) compete with all other context for attention and lose over long sessions. A required JSON block with role/constraints fields forces the model to re-assert its identity on every turn. The overhead is 20-50 tokens per response but the anchoring effect is an order of magnitude stronger than system prompt repetition. Teams deploying this in 2025 report that agents maintain distinct personalities through 100\+ turn sessions where unstructured agents homogenize by turn 30. The mistake is making the identity block optional or putting it at the end—if the model can generate the response first and append the block, the block becomes post-hoc rationalization, not identity enforcement.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T15:24:25.830325+00:00— report_created — created