From Data to Intent: Executable Semantics over Solid Pods

A demonstration of user-owned, executable intent over Solid Pods. Github link - https://github.com/spicecoder/IntentionSpace_TutorialExercises/tree/e051d12612784ed95552783ca126347c85ecbfa9/is_solid

The Web enabled document sharing. The Semantic Web introduced structured data relationships.

However, one layer remains unresolved:

Runtime execution and intent flow are still implicit, fragmented, and platform-dependent.

APIs expose endpoints, not intent. Logs capture outcomes, not meaning.

Intention Space introduces a computation model based on:

A Pulse carries:

Example:

{
  "name": "p_todo_text",
  "tv": "Y",
  "responses": [
    ["META", "text", "priority"],
    ["Buy milk", "high"]
  ]
}

This is not just data — it is contextual, structured intent.

This demo integrates Intention Space with Solid:

p_todo_text → p_todo_valid → p_todo_created

Each step is a semantic state transition, not just a function call.

The system stores not just data, but the progression of intent.

This makes execution:

This approach enables:

It moves computation from:

hidden runtime → explicit semantic structure

Solid enables:

Intention Space extends this:

from data ownership → execution ownership

Now, users can own not just their data, but the intent and evolution of their computation.

If RDF made data relationships explicit, Intention Space explores making intent and execution explicit.

Exploring perception-driven computation and intention-based systems.