Grasp replaces call chains with shape compatibility. A process declares what shapes it consumes and what it produces. When matching data appears, the process can activate without being explicitly called.
Declarative Causality
Instead of “call Process B,” you say “Data of Shape X exists.” Processes that consume Shape X awaken. The graph is the schedule. This creates a system that is message-based without explicit messages and event-driven without explicit events.Why This Scales
- Producers and consumers are decoupled.
- Adding a new process requires no rewiring.
- Flow emerges from structure rather than orchestration.
- You can inspect causality directly in the graph.
Example: File Ingestion
- You create a `Folder` node with a path.
- Query `files` to awaken a resolver.
- Resolver reads the filesystem and creates `File` nodes.
- Query `content` to read file contents.
No batch jobs, no orchestration logic. The graph grows as you ask.