MAIster keeps a small deterministic spine around work that remains non-deterministic. Agents can reason and produce open-ended results, while the platform records ownership, state, evidence, budgets, decisions, and promotion.

​
Sequence

  1. A Project identifies a repository and its delivery policy.
  2. A Flow package supplies a pinned, versioned process.
  3. A Task or scratch session supplies the intent.
  4. A Run records one immutable attempt.
  5. A Workspace isolates repository changes.
  6. ACP sessions execute agent nodes with scoped capabilities.
  7. Human-in-the-loop requests pause at declared decisions.
  8. Evidence reports whether required outputs are present and current.
  9. Review applies human judgment to the result.
  10. Promotion creates a pull request or performs a controlled local merge.

​
What is deterministic

  • Flow and runner revisions
  • Node state transitions
  • Workspace and branch ownership
  • Attempt and event history
  • Budget and rework limits
  • Required evidence status
  • Human decisions
  • Promotion target and result

​
What remains open

Agent prompts, reasoning, patches, reports, and structured result payloads may vary between runs. A Flow should constrain the contract that matters without pretending the creative work is deterministic.

​
Trust boundary

The web control plane owns product state. The execution supervisor owns agent processes and live ACP sessions. Both currently run on one trusted host and use the same local repositories and worktrees. Postgres stores the durable ledger.