Product · Composer · v1.5
The document surface of the platform.
Composer is where contracts, memos, structured documents, and legal positions are authored: against typed schemas, with the same versioning, audit, and Workblock binding that Studio uses for Workblocks.
What Composer is for
- 01
A senior contracts manager
Drafting a master agreement in a Composer document bound to a contract-position schema. The schema knows what a payment-term position looks like. Composer knows when the document drifts from the position.
- 02
A finance director
Drafting a board memo in a Composer document bound to a financial-decision schema. The memo's recommended action is linked to a Workblock instance in Flow. The audit is one click away.
- 03
A legal lead
Drafting a regulatory response in a Composer document bound to a citation schema. Each citation is a verifiable reference to a primary source. Hallucination is not a category Composer accepts.
Alongside Studio
- 01
Studio
The author's surface. Where the person closest to the problem builds the Workblock: with real data, against a real schema, in-room with the client.
Read more - 02
Flow
The runtime. Where Workblocks execute in production, with human-in-the-loop as a native state and full audit captured by default.
Read more - 03
Conductor
The spreadsheet surface: where models, analyses, and structured calculations live with the same schema rigour.
Read more