Object-Spatial Programming#
Learn Jac's unique graph-based programming paradigm with nodes, edges, and walkers.
Prerequisites
- Completed: Hello World
- Recommended: Your First Graph (gentler introduction)
- Time: ~45 minutes
What is Object-Spatial Programming?#
Traditional OOP: Objects exist in isolation. You call methods to bring data to computation.
Object-Spatial Programming (OSP): Objects exist in a graph with explicit relationships. You send computation (walkers) to data.
Traditional OOP: OSP:
┌─────────┐ ┌─────────┐
│ Object │ │ Node │◄──── Walker visits
│ .method │ │ │ and operates
└─────────┘ └────┬────┘
│ Edge
┌────▼────┐
│ Node │◄──── Walker moves
│ │ to connected nodes
└─────────┘
Quick Reference: Graph Operators
Operator Meaning Example ++>Create/connect node root ++> Person()[-->]Query outgoing edges [node -->][<--]Query incoming edges [node <--]spawnStart walker at node node spawn Walker()visitMove walker to nodes visit [-->]reportReturn data from walker report hereSee Graph Operations for complete reference.
Nodes: Objects in Space#
Nodes are classes that can be connected in a graph.
node Person {
has name: str;
has age: int;
def greet() -> str {
return f"Hi, I'm {self.name}!";
}
}
with entry {
# Create nodes (just like regular objects)
alice = Person(name="Alice", age=30);
bob = Person(name="Bob", age=25);
# Use them like regular objects
print(alice.greet()); # Hi, I'm Alice!
print(bob.age); # 25
}
Key point: Nodes are full-featured classes with methods, inheritance, etc. The graph capability is dormant until you connect them.
Connecting Nodes#
Use the ++> operator to connect nodes:
node Person {
has name: str;
}
with entry {
alice = Person(name="Alice");
bob = Person(name="Bob");
carol = Person(name="Carol");
# Connect to root (the default starting node)
root ++> alice;
root ++> bob;
# Connect alice to carol
alice ++> carol;
}
This creates a graph:
Edges: Named Relationships#
Edges can carry data and have types:
node Person {
has name: str;
}
edge Knows {
has since: int; # Year they met
has strength: str; # "close", "acquaintance"
}
with entry {
alice = Person(name="Alice");
bob = Person(name="Bob");
# Connect with a typed edge
alice +>: Knows(since=2020, strength="close") :+> bob;
}
Edge Operators#
| Operator | Meaning |
|---|---|
++> |
Connect with generic edge |
+>: EdgeType() :+> |
Connect with typed edge |
--> |
Query forward connections |
<-- |
Query backward connections |
<--> |
Query both directions |
Querying the Graph#
Use spatial operators to navigate:
node Person {
has name: str;
}
with entry {
alice = Person(name="Alice");
bob = Person(name="Bob");
carol = Person(name="Carol");
root ++> alice;
alice ++> bob;
alice ++> carol;
# Query connections from root
people = [root -->]; # All nodes connected to root
print(len(people)); # 1 (alice)
# Query from alice
friends = [alice -->]; # [bob, carol]
# Filter by type
only_people = [root -->](`?Person);
}
Query Syntax#
node Person {
has name: str;
}
edge Knows {
has since: int;
}
def query_examples(node: Person, alice: Person) {
# Basic queries
[node -->]; # All forward connections
[node <--]; # All backward connections
[node <-->]; # Both directions
# Type filtering
[node -->](`?Person); # Only Person nodes
[node ->:Knows:->]; # Only via Knows edges
[node ->:Knows:->](`?Person); # Knows edges to Person nodes
# Chained traversal
[alice ->:Knows:-> ->:Knows:->]; # Friends of friends
}
Walkers: Mobile Computation#
Walkers are objects that traverse the graph and execute abilities at each node.
node Person {
has name: str;
has visited: bool = False;
}
walker Greeter {
can start with `root entry {
visit [-->]; # Visit nodes connected to root
}
can greet with Person entry {
print(f"Hello, {here.name}!");
here.visited = True;
}
}
with entry {
alice = Person(name="Alice");
bob = Person(name="Bob");
root ++> alice;
alice ++> bob;
# Spawn walker at root
root spawn Greeter();
}
Output:
Wait, why only Alice? Because the walker visits root first (via start), then visits Alice (via greet), but doesn't continue to Bob. The walker needs to be told to continue traversing.
Walker Traversal with visit#
Use visit to continue to connected nodes:
node Person {
has name: str;
}
walker Greeter {
can start with `root entry {
visit [-->]; # Start by visiting nodes connected to root
}
can greet with Person entry {
print(f"Hello, {here.name}!");
visit [-->]; # Continue to all connected nodes
}
}
with entry {
alice = Person(name="Alice");
bob = Person(name="Bob");
carol = Person(name="Carol");
root ++> alice;
alice ++> bob;
alice ++> carol;
root spawn Greeter();
}
Output:
Walker Context Variables#
Inside a walker ability:
| Variable | Meaning |
|---|---|
here |
The current node |
self |
The walker instance |
visitor |
Same as self (alias) |
node Room {
has name: str;
}
walker Explorer {
has rooms_visited: int = 0;
can explore with Room entry {
self.rooms_visited += 1;
print(f"In {here.name}, visited {self.rooms_visited} rooms");
visit [-->];
}
}
Reporting Results#
Use report to collect results from walkers:
node Person {
has name: str;
has age: int;
}
walker FindAdults {
can start with `root entry {
visit [-->];
}
can check with Person entry {
if here.age >= 18 {
report here; # Add to results
}
visit [-->];
}
}
with entry {
root ++> Person(name="Alice", age=30);
root ++> Person(name="Bob", age=15);
root ++> Person(name="Carol", age=25);
result = root spawn FindAdults();
print(f"Found {len(result.reports)} adults");
for person in result.reports {
print(f" - {person.name}");
}
}
Output:
Entry Points#
Walkers can have different entry points:
walker DataProcessor {
has data: str;
# Runs when spawned at root
can start with `root entry {
print("Starting from root");
visit [-->];
}
# Runs when visiting a Person node
can process with Person entry {
print(f"Processing {here.name}");
visit [-->];
}
# Runs when visiting any node
can default with entry {
print("At unknown node type");
visit [-->];
}
}
Practical Example: Social Network#
node User {
has username: str;
has bio: str = "";
}
edge Follows {
has since: str;
}
walker FindFollowers {
can find with User entry {
# Find all users who follow this user
followers = [<-:Follows:<-];
for follower in followers {
report follower;
}
}
}
walker FindMutualFollows {
can find with User entry {
following = [here ->:Follows:->];
followers = [here <-:Follows:<-];
for user in following {
if user in followers {
report user; # Mutual follow!
}
}
}
}
with entry {
alice = User(username="alice");
bob = User(username="bob");
carol = User(username="carol");
root ++> alice;
root ++> bob;
root ++> carol;
# Alice follows Bob, Bob follows Alice (mutual)
alice +>: Follows(since="2024") :+> bob;
bob +>: Follows(since="2024") :+> alice;
# Carol follows Alice
carol +>: Follows(since="2024") :+> alice;
# Find Alice's followers
result = alice spawn FindFollowers();
print("Alice's followers:");
for user in result.reports {
print(f" - {user.username}");
}
# Find Alice's mutual follows
result = alice spawn FindMutualFollows();
print("Alice's mutual follows:");
for user in result.reports {
print(f" - {user.username}");
}
}
Running as an API#
The same graph code becomes a REST API:
node Todo {
has title: str;
has done: bool = False;
}
walker add_todo {
has title: str;
can create with `root entry {
new_todo = here ++> Todo(title=self.title);
report new_todo;
}
}
walker list_todos {
can list with `root entry {
for todo in [-->](`?Todo) {
report todo;
}
}
}
# Run as API server
jac start app.jac
# Call via HTTP
curl -X POST http://localhost:8000/walker/add_todo \
-H "Content-Type: application/json" \
-d '{"title": "Learn OSP"}'
Key Takeaways#
| Concept | Purpose |
|---|---|
node |
Objects that live in a graph |
edge |
Typed relationships between nodes |
walker |
Mobile computation that traverses the graph |
++> |
Connect nodes |
[-->] |
Query connections |
visit |
Continue walker traversal |
report |
Collect results from walker |
here |
Current node in walker |
spawn |
Start walker at a node |
Next Steps#
Continue Learning:
- Testing - Test your nodes and walkers
- AI Integration - Add LLM capabilities
- First App - Review the todo app example
Reference:
- Graph Operations - Complete edge/node operator reference
- Walker Responses - Understanding
.reportspatterns - Part III: OSP - Full language reference