Skip to main content

WorkGraph Example

This example models a Homecore-style situation where incoming information, calendar context, and routine automation produce shared durable work.

Scenario

A calendar event says L is taking A to the dentist on May 20. A strongly prefers car P. A new maintenance update says car P is in the workshop. A needs preparation for irregularities, so L should receive a reminder the day before the appointment. WorkGraph does not infer the family policy. The agent reasons about the data, then records the durable commitment and dependencies.

1. Create The Work Items

The reminder item should not be ready until transport details are verified.

3. Ask WorkGraph What Is Ready

The agent does not inspect blocker counts itself. It works from the ready list returned by WorkGraph.

4. Claim, Act, And Add Evidence

After checking the maintenance and vehicle data, the agent attaches evidence.
Then it closes the blocker.
The dependent reminder can now become ready when its time gates allow it.

5. Observe The Graph

A UI or operator can inspect the same realm without mutating it:
or:

Why This Is Not An Expert System

The LLM decides what matters from calendar data, maintenance records, family preferences, and user policy. WorkGraph only records the durable to-do spine: dependencies, readiness, claim state, evidence, and terminal truth.