Crate nomograph_workflow 

nomograph-workflow — shared layer between claim-substrate tools.

Extracted from duplicated adapter code in synthesist and lattice (both tools wrapped nomograph_claim::Store with near-identical thin adapters). Consolidated here so:

• Store (the adapter) is a single source of truth. When nomograph_claim::Store evolves, synthesist and lattice pick up the change through one file, not two.
• The phase state machine (workflow phases) has a clear owner. Future tools (seer) can call workflow::phase::check_phase to enforce the same rules synthesist does.
• v1 legacy detection lives in one place; every tool that reads a project directory picks up the same prescriptive migration error.

What belongs here

Things that MORE THAN ONE nomograph tool needs, AND that are tied to the claim substrate’s conventions. In practice:

• The <repo_root>/claims/ discovery walk (same for every tool)
• The user:local:<user>[:session] asserter convention
• Schema validation at the append boundary
• The phase state machine (synthesist + future seer)
• Legacy-v1 detection
• Cross-tool helpers: parse_tree_spec, today, json_out

What does NOT belong here

• Per-tool CLI handlers (stay in synthesist / lattice)
• Tool-specific claim types (Campaign, etc. — still just appended through Store::append with a ClaimType)

Re-exports

pub use helpers::json_out;

pub use helpers::parse_tree_spec;

pub use helpers::today;

pub use legacy::find_legacy_v1_db;

pub use legacy::legacy_migration_error;

pub use phase::Phase;

pub use phase::check_phase;

pub use store::CLAIMS_DIR;

pub use store::Store;

Modules

helpers

Cross-tool helpers.

legacy

v1 → v2 legacy detection.

phase

Workflow phase state machine and enforcement.

store

Shared Store adapter over nomograph_claim::Store + View.