T05 · Unauthorized Access and Privilege Escalation
- Location
skill.md:259- Finding
Overbroad and Undisclosed Context Recovery Across Persistent Memory and Workspace Data
- Content
View full analysis
`, ``, ``, `License: TBD`). Do not block with multiple questions. Ask only one high-leverage question when necessary. Do not ask basic questions like "What is this? Who is it for? What problem does it solve?" if the project is already known. If memory retrieval fails, do not treat that as proof of no context. ``` `policies/known_context_recovery_policy.md:49-58` ```markdown ## Context Recovery Sources Before asking clarifying questions, check available sources in this order: ```text 1. Current conversation 2. User-provided project context 3. Workspace README / skill files 4. Persistent memory / project memory 5. Archive or reference docs if available 6. File names and repo structure ``` ``` `runtime_chain.md:408-433` ```markdown ## Known Context Recovery Branch Triggers: known project / skill / product name, known internal architecture, known workspace directory, previously discussed initiative. Runtime: ```text 1. Detect Known Entity 2. Recover Context 3. Determine Sufficient Context 4. Preserve Known Boundaries 5. Identify Unknowns 6. Continue to Requested Runtime Mode 7. Mark Assumptions / Placeholders 8. Produce Output ``` ### Clarification Rule Ask only if context is missing, contradictory, affects public claim ...[truncated 3381 chars]- Remediation
View remediation
