Documentation
Reference and guides for the Amalgative suite — Draft, Redline and Sequence.
Amalgative builds design and technology tools for the people who draw buildings, the people who review them, and the people who work out when any of it happens. Three products, one family: Draft makes the drawing, Redline marks it up, and Sequence schedules the work.
Draft
A 2D drafting tool with the feel of a professional CAD command line — OSNAP, ortho/polar, grips, trim/offset/fillet — that runs properly on Linux, macOS and Windows alike. Grows a 3D modelling pane.
ProductRedline
PDF markup, measurement and takeoff for AEC document control. Real PDF annotations, a calibrated measurement engine, and a markups list that reads like a spreadsheet.
ProductSequence
Construction scheduling and project planning. Activities and logic, baselines, resources and cost, look-ahead windows, scenarios, and a quality check that runs before anybody else finds the problem.
How the three fit together#
Draft plots to PDF. Redline marks up PDF. That is a real workflow, not a coincidence of file formats — the two products were built to hand work to each other, and they share a chassis so that what you learn in one transfers to the other.
Sequence is the third leg, and it works on the same drawings from the other end: the schedule that says which of them has to be finished by when. It shares the chassis too — the same panels, the same command surface, the same settings tree.
| Product | What it does | Platform |
|---|---|---|
| Draft | 2D drafting and, later, 3D modelling | Linux, macOS, Windows (Tauri desktop) |
| Redline | PDF markup, measurement, takeoff, document control | Linux, macOS, Windows (Tauri desktop) |
| Sequence | Construction scheduling and project planning | Linux, macOS, Windows (Tauri desktop) |
Where to start#
If you are new to the suite, read the overview for whichever product you are using — each one opens with what the product is for and who it is aimed at.
If you are coming from another CAD package, start with Draft › Precision drafting; it is the page that explains what Draft inherited from your muscle memory and what it deliberately did not.
If you are coming from another PDF markup tool, start with Redline › Markup tools and Redline › Measurement & takeoff.
If you are building or reviewing a schedule, start with Sequence › Overview.
If you want to know what is actually built, go straight to the roadmap.
How this documentation is written#
Three conventions run through every page, and they matter when you are deciding whether to rely on something.
Status is checked, not asserted. These are products under active development, and this site describes some things that are built and some that are designed. Every capability it names is registered with a state — shipped, partial, planned, or deliberately not planned — and anything that is not shipped carries a badge saying so, next to the sentence that describes it. The roadmap is the full list. The site does not build if a page names a capability nobody registered, and a separate check re-verifies every shipped claim against the product's own source.
Screenshots are captured, not drawn. Every image here is produced by a script that drives the real application the way the text describes — typing the command, clicking the tool. If the documented gesture stops working, the capture stops working.
Behaviour, not implementation. These pages describe what the software does. The reasoning behind an architectural choice lives in each repository's planning documents; where a choice has a visible consequence for you — a curve that facets, a format that will not round-trip — the consequence is documented here rather than hidden.
Getting help#
Questions, licensing, and support: support@amalgative.com.