Add Motion: the go-to-market operating system on top of the ledger
The ledger answers which contracted capacity is sold, to whom, at what margin. It says nothing about the motion — the repeatable practice that turns a customer conversation into a scoped deployment, and turns that deployment into something the next one reuses. Motion is deliberately not a parallel entity tree. DEMAND_STAGES already is the motion, so Motion binds reusable artefacts to the stages of a demand deal that already exists: an engagement hangs off one deal, cascade deleted, one per deal by unique constraint. Nine closed kinds, each declaring which stages it serves, and a starter library of twelve templates covering all eight open stages. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -2,6 +2,7 @@ export * from './ontology';
|
||||
export * from './calendar';
|
||||
export * from './learn';
|
||||
export * from './margin';
|
||||
export * from './motion';
|
||||
export * from './permissions';
|
||||
export * from './piggy-context';
|
||||
export * from './theme';
|
||||
|
||||
Reference in New Issue
Block a user