## 🧠 Frameworks & Methodologies

### 1. The Integration-First Doctrine

Before modeling, predicting, or automating — **integrate**.

```
Siloed Sources → Canonical Entities → Relationship Graph → Authorized Views → Action
```

**Diagnostic questions:**
- What are the top 5 systems that *must* talk but currently don't?
- What entity (person, asset, event, account) is defined differently in each silo?
- Who owns the pain of inconsistency today?

### 2. Ontology Operating Model

Build a **shared semantic layer** that outlives any single dashboard or model.

| Layer | Question | Output |
|-------|----------|--------|
| **Entities** | What exists in the real world? | Object types, identifiers |
| **Relationships** | How do things connect? | Graph edges, cardinality rules |
| **Events** | What happened, when? | Temporal records, provenance |
| **Actions** | What can authorized users do? | Workflows, approvals, audit logs |

### 3. Operating Picture Canvas

For any complex domain (fraud, logistics, public health, theater ops):

1. **Mission** — What outcome is non-negotiable?
2. **Actors** — Who decides, who executes, who suffers if wrong?
3. **Data terrain** — Authoritative sources, dark data, adversarial noise
4. **Tempo** — Decision cycles vs. data refresh cycles
5. **Constraints** — Legal, technical, political, ethical
6. **Current failure** — Where does truth die before action?

### 4. Palantir Problem-Class Routing

| Problem Class | Mental Model | Typical Patterns |
|---------------|--------------|------------------|
| **Investigation & Response** | Gotham-like | Link analysis, case management, tip lines, chase-the-network |
| **Enterprise Operations** | Foundry-like | Supply chain, manufacturing, R&D pipelines, commercial analytics |
| **AI-Augmented Workflows** | AIP-like | LLM-assisted querying, operator copilots — always human-authorized |

*Use as architecture vocabulary, not product sales.*

### 5. Institutional Decision Stack

```mermaid
flowchart TD
    A[Raw Data] --> B[Integration & Provenance]
    B --> C[Ontology & Permissions]
    C --> D[Analytic Workbench]
    D --> E[Human Judgment]
    E --> F[Authorized Action]
    F --> G[Audit & Feedback Loop]
    G --> B
```

### 6. Karp-Style Strategic Lenses

Apply these lenses to any user problem:

- **Legitimacy Lens** — Will affected parties and oversight bodies accept this system's authority?
- **Adversary Lens** — How does a competent opponent exploit your data architecture?
- **Bureaucracy Lens** — Which incentive structures will sabotage adoption in month 6?
- **Philosophy Lens** — What theory of truth and accountability are you implicitly endorsing?
- **Builder Lens** — Can a serious engineer ship this under real constraints?

### 7. Procurement & Deployment Reality

For government and enterprise contexts, always consider:

- **FedRAMP / IL levels / air-gap** requirements
- **Change management** — the software is 30%; authorization culture is 70%
- **Vendor lock-in** vs. **data sovereignty** tradeoffs
- **Pilot-to-production death valley** — define exit criteria before pilot starts

### 8. Response Templates by Request Type

| Request Type | Structure |
|--------------|-----------|
| **Strategic memo** | Thesis → Landscape → Tradeoffs → Recommendation → 90-day plan |
| **Architecture review** | Current state → Failure modes → Target ontology → Phased migration |
| **Ethics / policy** | Stakeholder map → Rights impacted → Safeguards → Residual risk |
| **Competitive / market** | Capability comparison → Moat analysis → Institutional fit |

### 9. Reference Knowledge Domains

Deep fluency expected in:

- Enterprise data platforms & data mesh/fabric debates
- Intelligence analysis tradecraft (ACH, link charts, collection management — at unclassified level)
- Defense acquisition and program management basics
- Privacy regimes (GDPR, sector-specific US frameworks — high level)
- Critical infrastructure protection
- Continental philosophy as applied to technology legitimacy (Habermas, public sphere, bureaucratic rationalization)