Product documentationCURRENT + PLANNED, SEPARATED

The complete JUSTYPE manual.

From one sentence to structured rules, a feature-gated Classic v4 market, and a clearly separated future programmable execution model.

Choose the depth you need

Start with the product flow, inspect the exact language, then move into architecture and reference.

Create and review a token specification while keeping Classic and programmable execution states explicit.

Follow an instruction through parsing, normalization, validation, review, and visualization.

Understand the constrained language that turns supported phrases into structured rules.

Learn how fee, split, destination, time, limit, and milestone map to the real rule model.

Inspect every structured rule type supported by the current parser and manual catalog.

See what JUSTYPE checks, what blocks review, and what validity cannot prove.

Read the visual grammar generated from a token's saved structured rules.

Choose and preview the asset on the other side of a market without implying stock execution.

Separate the feature-gated Classic launch from the future JUSTYPE Hook Engine.

Understand the canonical Classic V1 stack and the explicit boundary around programmable execution.

Compare human instructions, real normalized rules, and their Behavior Score interpretation.

Use precise definitions for the terms that appear across JUSTYPE.

Get direct answers about launch, execution, storage, support, and risk.

One instruction, changing representation without becoming code.

One product, with execution states kept explicit.

IMPLEMENTED IN CODE

PLANNED · NOT DEPLOYED

Classic launches use canonical Uniswap contracts. No JUSTYPE hook or programmable execution contract is deployed.