Skip to main content
Back to selected work
Implementation evidence package

Inspectable workflow orchestration with state machines

Open-source implementation work on Python statechart semantics, actors, clocks, and XState-compatible workflow definitions.

Implementation EvidenceOpen Source ProjectPrototypePublic ArtifactPublic
Public source | State transition example
state = lights.initial_state
assert state.value == "green"

state = lights.transition(state, "TIMER")
assert state.value == "yellow"

An excerpt of the documented traffic-light example: an explicit event changes the state. This is source evidence, not production adoption.

Read the complete example
Situation

Durable AI and automation workflows need explicit state and actor boundaries when retries, time, human decisions, and partial failure matter.

Jovani's role

Implemented, Contributed, Authored

Public source and technical writing expose the implementation surface and its current limitations.

Intervention

  • Implemented statechart and actor behavior in Python
  • Worked on clocks and XState-compatible workflow definitions
  • Documented the shared workflow contract and current limitations

Inspectable artifacts

  • Public source repository
  • Tests
  • Technical workflow-contract note
Verified public artifact

The public source and writing provide inspectable implementation evidence for an evolving workflow prototype.

Claim boundary

The repository is implementation evidence for an evolving prototype; it is not evidence of production adoption, durability, or operational outcomes.

Not publicly proven

  • - There is no public evidence of production adoption or durable-execution guarantees.
  • - Upstream acceptance and a stable public release remain unresolved.
Evidence links

Inspect the public artifacts

Last verified 2026-08-20

Next step

Bring one consequential AI workflow.

Share the workflow problem. We will use the first conversation to determine whether a two-week decision engagement is the right next step.

Assess a workflow