← OrdoAnimi Architecture / Engagement Archetypes
Information critical to the solution is being deliberately withheld by a vendor, internal party, or stakeholder with a vested interest in preventing full disclosure. The defining characteristic is intent — the withholding is purposeful. This is not structural absence. Someone knows. Someone is choosing not to tell you.
Primary Risk
Design on false premises
Velocity Target
10–20 days to CIS
Detection
Signals
Observable Signals
- Vendor confidence without documentation
- Vague answers to direct data flow questions
- Completed POC not being shared
- Decisions made with no audit trail
- Egress described as ingress
- Architecture diagrams contradicted by system behaviour
- Escalation treated as personal attack
OrdoAnimi Concepts Activated
- Information Asymmetry
- Governance Drag — Deliberate
- Decision Altitude Collapse
- The Blank Cell
Operating Posture
Forensic
Field Instruction
Every answer is a hypothesis until independently verified. The heat map is the interrogation instrument. Every blank cell is deliberate, not accidental. Go to unofficial channels. Cross-reference vendor claims against observable system behaviour. Hold the line until every cell is answered. Do not design until the asymmetry is resolved or formally acknowledged.
In the Obfuscation Engagement, the standard intake process will not surface what you need. Formal workshops and discovery sessions are managed performances. You extract the real picture from documentation discrepancies, informal conversations, and observable system behaviour that contradicts the stated position.
The heat map is your primary instrument. Every blank cell is a deliberate choice. Map the blanks before you map the answers.
Field Execution
Tactical Guidance
Never confront the obfuscation directly in formal settings. Confrontation triggers defensive escalation. Build the picture independently and present your findings as a gap analysis, not an accusation.
Go to unofficial channels. The person withholding information in the formal engagement is rarely withholding it in every conversation. Find the practitioner who built the system, not the person managing the relationship.
Log everything. Every question asked, every non-answer received, every document requested and not provided. This log becomes your escalation artefact if the engagement deteriorates.
Use the vendor's own documentation against the verbal position. Vendors withholding information frequently contradict themselves between their public product documentation and their stated configuration. Find the contradiction.
Combination Patterns
When Archetypes Combine
The Obfuscation Engagement rarely appears in isolation. Common combinations:
Obfuscation + Negligent Void
Information is being withheld AND no architectural foundation exists. Hardest combination. You cannot build on what you cannot see and what does not exist.
Obfuscation + Institutional Paralysis
History is being withheld and the organisation has failed before. The obfuscation is protecting prior failures from scrutiny. Escalation is heavily politicised.