Manifesto

Appearance

Upgrade to the Next Major ​

Moving onto the hard-cut runtime surfaces, including the optional advanced runtime.

This guide captures the practical changes needed to move onto the current next-major surface after the hard-cut align work.

Runtime Choice ​

Use one of these two public entry paths:

  • @manifesto-ai/sdk with createManifesto() and activate() for base runtime
  • @manifesto-ai/lineage + @manifesto-ai/governance for the advanced runtime

Do not mix them into a single bootstrap story.

Hard-Cut Changes ​

If you are moving old approval/history code forward, align to these surfaces:

  • use createManifesto(schema, effects) instead of config-style runtime factories
  • use withLineage(...) and withGovernance(...) before activate()
  • use action.<name>.submit(...) on the activated runtime. Base, Lineage, and Governance modes share that call shape and differ through their result unions.
  • use package-owned stores and services from Lineage and Governance directly
  • treat the retired facade, adapter subpaths, and facade-owned coordinator/runtime as removed

Advanced Runtime Bootstrap ​

The current advanced-runtime path is:

  1. Create the app definition
  2. Add Lineage
  3. Add Governance
  4. Activate
  5. Call action.<name>.submit(...)
  6. Observe settlement with waitForSettlement(...)
  7. Read history through Lineage queries such as getLatestHead() and restore()

Use getWorldSnapshot(worldId) when you need the stored snapshot for a committed history record. Use restore(worldId) when you need the normalized runtime resume path.

What Not to Carry Forward ​

Do not reintroduce the removed transition surfaces from earlier drafts:

  • retired facade entrypoints
  • retired facade adapter subpaths
  • facade-owned coordinator/runtime types
  • facade-owned execution seams
  • config-first createManifesto(...) bootstraps

See Also ​