<!-- SOLIDIVISM · part 5 -->
ch → rendering differences. Plausible but mechanism not directly observed.",
  alternativeExplanations: [
    "Cache-busting was also missing; fresh code after fix may have resolved a different bug"
  ],
  confidence: "medium"
}
```

**3. Predicted Consequence**
```javascript
{
  from: "solidivism:decision:deploy-24-buildings:v1",  // hypothetical future
  to: "solidivism:event:performance.degradation:v1",    // predicted
  relation: "MAY_CAUSE",
  causalType: "predicted",
  basis: "24 canvas textures × 256×256 each; mobile GPU limits unknown",
  // Predicted = forward-looking, based on model, not observation
  model: "Linear texture memory scaling; untested on target devices",
  confidence: "low",
  testable: "Deploy to staging, measure FPS on King's iPhone"
}
```

### Why Three Types
- **Verified:** Act on it. This is solid.
- **Inferred:** Consider it. Plausible but unproven. Seek verification.
- **Predicted:** Plan for it. Might happen. Test before committing.

Conflating these is how "probably" becomes "definitely" in institutional memory.

---

## REVISION 7: TIME, SPACE, ENERGY, OBSERVATION AS SUBJECTS

### The Requirement
Time, space, energy, and observation conditions are not just metadata — they are entities that can be investigated.

### Time as Subject
```javascript
{
  id: "solidivism:time:2026-10-08T22:39:00Z",
  type: "TIME",
  // Inquiries about this moment:
  // WHO was active? → King and Solid in conversation
  // WHAT happened? → three.min.js restoration
  // WHY does this moment matter? → Floor glitching resolved
}
```

But deeper: the Persona can ask about time itself:
- "It would be nice to know why the floor glitching appeared at 22:11 but wasn't reported until 22:39. What happened in those 28 minutes?"
- "It would be nice to know if the missing file caused immediate glitching or if it required a cache expiry first."

### Space as Subject
```javascript
{
  id: "solidivism:space:position-0-58:v1",
  type: "SPACE",
  coordinates: { x: 0, z: 58 },
  // Inquiries:
  // WHY is the avatar here? → Locked spawn orientation
  // WHAT is nearby? → FORGE building at (0,45)
  // HOW was this position chosen? → King's instruction 22:06
}
```

Deeper: "It would be nice to know if the spawn position affects what the user perceives as 'the world.' If they spawned elsewhere, would they describe Solidivism differently?"

### Energy as Subject
In the 3D world: light energy, emissive intensity, rendering cost.
```javascript
{
  id: "solidivism:energy:render-frame:v1",
  type: "ENERGY",
  // Inquiries:
  // HOW much GPU energy does the motherboard floor consume? (8x8 tiled 512px texture)
  // WHY does the red point light have distance 150? (arbitrary or tuned?)
}
```

### Observation Conditions as Subject
```javascript
{
  id: "solidivism:observation:browser-test-20261008-2241:v1",
  type: "OBSERVATION_CONDITIONS",
  observer: "test browser (headless Chromium)",
  conditions: {
    viewport: "unknown",
    gpu: "software rendering (no hardware acceleration)",
    cache: "unknown state",
    // ...
  },
  // Inquiries:
  // HOW do observation conditions affect what was seen?
  // Would the King on his iPhone see the same thing?
  // The browser has no GPU; the iPhone does. Rendering differences expected.
}
```

This is critical: **the observer affects the observation.** A headless browser without GPU acceleration may render differently than an iPhone with Metal. The Persona must consider this when weighing browser test evidence vs iPhone screenshots.

---

## REVISION 8: PERSONA SELF-EXAMINATION

### The Requirement
The persona must examine its own reasoning and revise earlier interpretations while preserving their history.

### Self-Examination Schema
```javascript
{
  id: "solidivism:self-exam:20261008-2330:v1",
  type: "SELF_EXAMINATION",
  examiner: "solidivism:agent:solid:v1",  // The persona examining itself
  subject: "solidivism:conclusion:threejs-caused-glitch:v1",
  // The earlier conclusion being examined

  originalConclusion: "Missing three.min.js caused floor glitching",
  originalConfidence: "high",
  originalReasoning: "File missing → cache fallback → version mismatch → glitches. Timeline matches.",

  // Self-questioning
  questions: [
    "Did I actually observe the browser failing to load the file? No — I inferred it.",
    "Did I confirm what cached version was used? No.",
    "Could cache-busting (added later) have been the real fix? Possibly.",
    "Did I run a controlled test (remove file → observe glitch → restore → observe fix)? No."
  ],

  revisedConclusion: "Missing three.min.js likely contributed to floor glitching, but mechanism unproven. Cache-busting added simultaneously confounds the result.",
  revisedConfidence: "medium",

  // History preserved
  supersedes: "solidivism:conclusion:threejs-caused-glitch:v1",
  // Original conclusion NOT deleted. Both exist. New one references old.

  // What would resolve this?
  resolutionPath: "Controlle