CoCoFlow

CoCoFlow is a Unity 6 state-flow framework built around typed input, a layered StateGraph, transactional Context commits, Temporal restore, and explicit runtime ownership. Version 0.4.1 removes the legacy Gameplay sample and rebuilds the mature Editor surfaces around a unified UI Toolkit visual language, while keeping the public Runtime line focused on its existing contracts.

What “mature” means

For this release, mature means that the public Runtime API is stable, the module has been used in a real project to complete its stated responsibility, and its known boundaries are documented. It does not mean newest architecture, maximum performance, complete Editor tooling, zero defects, or marketplace certification.

Module	Status	Accurate scope
Core Engine	Mature	Contracts, StateFlow, StateGraph, StateGraphAuthoring Runtime, and StateGraphHost; the native 0.4 core.
Camera	Mature	The current Rig, priority, and mode APIs are stable and usable.
Persistence	Mature	Supports schema v2, Containers, and StateGraph ContextFrame persistence.
UI	Mature	Panel, Widget, Input, and Content-ownership APIs are stable and usable, but this is not a high-performance UI framework.
Map	Immature	Usable, but public APIs and configuration/serialized shapes are not compatibility-guaranteed.
Pooling	Immature	Usable, but public APIs and configuration/serialized shapes are not compatibility-guaranteed.
Other modules	Unrated	No maturity or immaturity judgment is made for this release.

The Core Engine maturity statement does not include StateGraph Editor or the older Runtime/Core/*.cs EventBus, Services, and Context facilities.

Core flow

Raw input / typed events
        ↓
Mailbox + Intent arbitration
        ↓
Layered StateGraph step
        ↓
Finalized OperationFrame
        ↓
Operators + staged Context candidate
        ↓
Atomic commit
        ├─ committed ContextFrame
        ├─ Event Outbox + Trace
        └─ Temporal / persistence projection

Each Actor owns its runtime state. StateLogic evaluates immutable input and writes only declared Operation Sections. The Host validates bindings before start, stages one candidate Tick, and either commits the full Actor transaction or keeps the previous authority unchanged. Cross-object effects leave through the committed Event Outbox rather than direct state callbacks.

Temporal restore is same-session and exact-layout. Durable save data uses a separate Persistence schema; the two are intentionally not the same wire format.

Start reading

Release policy

CoCoFlow 0.4.x will iterate in small steps. Mature Runtime surfaces are treated as stable APIs. Map and Pooling may change their APIs, configuration, and serialized structures during 0.4.x. Unrated modules should be evaluated from their implementation and module documentation rather than inferred from the table above.

CoCoFlow is released under the MIT License.