@[Andrew Mewborn] great question!
Refrakt doesn’t treat “the model” as a shared mutable object. The primary units are
versioned workflows, configs, and the artifacts produced by each run.
Collaboration is centered around reproducible runs and explicit artifacts (e.g.
being able to inspect, compare, or reuse outputs from prior executions) rather than
multiple people concurrently editing the same state.
For now, the focus is on making iteration legible and traceable (who ran what, with
which config, producing which artifacts).
More explicit team-level collaboration primitives are something we’re thinking about, but this walkthrough is mainly meant to show the core workflow abstraction.
