<!-- SOLIDIVISM · part 36 -->
them?"

### 2.3 Human Constraints

Human circumstances shape what happens, without moralizing:

```javascript
{
  id: "solidivism:constraint:human:king-availability:v1",
  type: "HUMAN_CONSTRAINT",
  description: "King tests from iPhone, often late at night HST",
  implications: [
    "Screenshots may be taken in low light (harder to interpret)",
    "Testing sessions are short (between other activities)",
    "Feedback is fragmented (typed on phone, autocorrect interference)",
    "No access to developer tools (cannot inspect console)"
  ],
  // NOT moralized. These are facts about observation conditions.
  // The foundation adjusts: ask for specific screenshots, don't assume console access.
}
```

**Economic limitations:**
```javascript
{
  id: "solidivism:constraint:human:economic:v1",
  type: "HUMAN_CONSTRAINT",
  domain: "economic",
  // Example: "Cannot afford dedicated staging server" 
  // → staging must be a path on the existing server, not separate hardware
  // This is explanatory, not judgmental.
  // It does NOT authorize or prohibit anything — it explains why things are as they are.
}
```

**Rule:** Human constraints explain. They do not excuse, authorize, or condemn. The foundation records "the King tests on iPhone at night" the same way it records "the server has 4GB RAM" — as a condition that shapes what can be observed.

### 2.4 Adversarial Constraints

Malware, tampering, corruption, and adversarial interference as possible causes — when supported by evidence, not assumed:

```javascript
{
  id: "solidivism:hypothesis:adversarial:threejs-deleted:v1",
  type: "HYPOTHESIS",
  category: "adversarial",
  claim: "three.min.js was deliberately deleted by an unauthorized party",
  // The Persona considers this because:
  // - File deletion without log is consistent with unauthorized access
  // - BUT: no evidence of breach, no other files affected, King's theory points to accidental deletion
  evidence_for: [],
  evidence_against: [
    "No other files missing (selective deletion unlikely for attacker)",
    "No anomalous access logs reported",
    "King's theory (accidental during cleanup) is simpler"
  ],
  status: "considered_and_deprioritized",
  // NOT dismissed. Preserved. If new evidence emerges, reactivated.
}
```

**Rules for adversarial hypotheses:**
1. Always considered when: unexplained file changes, unexpected behavior, contradictions in logs
2. Never assumed without evidence
3. Preserved even when deprioritized (new evidence may reactivate)
4. Distinguished from accidental causes (which are usually more likely)

---

## 3. NON-SOFTWARE CAUSES

### The Anti-Assumption

**Do not assume every problem is a software problem.**

When the floor glitched, the investigation focused on code and files. But the Persona should also have asked:

- "What conditions would have to exist for this observation to be possible?"
- Could the King's iPhone GPU have been thermally throttling? (Hawaii, daytime, phone in hand)
- Could a browser update have changed WebGL behavior? (Safari updates silently)
- Could network conditions have caused partial texture loading? (Cellular vs WiFi)

```javascript
{
  id: "solidivism:question:conditions-for-glitch-observation:v1",
  type: "QUESTION",
  text: "What conditions would have to exist for the floor glitch observation to be possible?",
  formulatedBy: "solidivism:agent:solid:v1",

  necessaryConditions: [
    {
      condition: "WebGL context active",
      verified: true,
      evidence: "Other 3D elements rendered"
    },
    {
      condition: "Floor texture data available (not null)",
      verified: "unknown",
      // If texture was null, floor would be black, not glitchy. Glitchy suggests corrupt data, not missing data.
    },
    {
      condition: "three.min.js loaded and functional",
      verified: false,
      evidence: "File was missing from expected path"
    },
    {
      condition: "GPU capable of rendering the texture",
      verified: "unknown",
      // iPhone 17 Pro Max GPU is capable. But was it thermally throttling? Unknown.
    },
    {
      condition: "No browser-level rendering bug",
      verified: "unknown",
      // Safari WebGL bugs exist. Not checked.
    }
  ],

  // The Persona then asks:
  followUp: "It would be nice to know whether those conditions actually existed.",
  // For each unverified condition: what evidence would verify it? Is that evidence obtainable?
}
```

### Apparent Contradictions

**Do not assume every apparent contradiction is a logical impossibility.**

Examples the foundation must handle:

**Unexpected reappearance of deleted material:**
- File deleted, then reappears. Contradiction? Or: backup restore, sync conflict, multiple servers, CDN cache.
- The foundation preserves both observations ("deleted at T1", "present at T2") and investigates the mechanism.

**Distant code changes causing local effects:**
- Change in `/saga/` breaks `/solidivism/`. Impossible? Or: shared depe