Four tiers, and the test that sorts a thing into one of them
the four questions · the tier each one selects · what refuses a drift
Platform product / System overview
Studio Kit
Tools for building Trident applications
Studio Kit combines node editing, script editing, reusable libraries, data views, and validation. It edits the same application source that runs in production.
Inside the system
Architecture plates
Each plate preserves the internal layout, paths, boundaries, and highlighted decisions. Use the short label first, then follow the lines through the system.
Five libraries that compose, and a long list they do not own
the five libraries · the surfaces they compose · what lives elsewhere
One declaration, one gate, four faces that cannot bypass each other
one record · one gate · four projections · five named refusals
The loop closes: the Kit authors an Application that composes the Kit
six route-names · no address in the Kit · the authored app runs on Fathom
Key parts
What the system does
These are the main boundaries, inputs, outputs, and failure rules. The examples show a specific use of each part.
Visual and text authoring
Teams can move between diagrams and precise Trident text without creating separate application versions.
Specific example
An operator can help shape a maintenance workflow visually while a software lead reviews the exact behavior.
Reusable mission building blocks
Shared libraries provide common controls, data patterns, and simulation tools. Applications choose and combine what they need.
Specific example
A new planning tool can reuse an approved map view and identity flow instead of rebuilding both.
Built-in review path
Authoring, validation, and evidence use the same declared application. No private tool path can bypass the platform rules.
Specific example
A prototype can mature into a pilot while keeping its review history and tested behavior connected.
Uses
Example uses
- Rapid mission application prototypes
- Operator-involved workflow design
- Reusable program software factories
Pilot questions
What the team must decide
Who needs to take part in authoring
Which building blocks can be reused across programs
What evidence is needed to move from pilot to field use