JUSTYPE
Profile
Architecture

Programmable markets

Separate the current configuration product from the future execution ambition.

A programmable market is a market whose operation can include explicit behavior beyond a static pair and fee. JUSTYPE’s current product designs and explains those behaviors; it does not execute them yet.

One product, two clearly separated states.
CURRENT PRODUCT
  1. 01Parse
  2. 02Normalize
  3. 03Validate
  4. 04Review + Behavior Score
  5. 05Browser-local profile
PLANNED · NOT DEPLOYED
  1. ARule compiler / adapter
  2. BHook execution
  3. CSettlement + indexing

No JUSTYPE contract, hook address, or live execution path exists in this repository.

Current: a deterministic configuration product

Today you can describe behavior, review structured rules, and save a local profile. This makes the mechanics legible before any future execution exists. Markets and Activity remain at public genesis, and local profiles stay in one browser.

Planned: an execution adapter with a narrower contract surface

The repository identifies a future rule compiler or adapter that would accept only validated, supported rule families and map them to audited deployment parameters. That integration has not been designed in contract code here, so the eventual executable subset may be smaller than the frontend’s current 21-type language.

Why Uniswap v4 is relevant

Uniswap v4 lets a pool attach an optional hook contract whose selected callbacks can run around lifecycle actions. That makes v4 a relevant architecture for market-specific behavior. It does not make arbitrary behavior safe or automatically compatible, and hooks still require careful contract design, testing, deployment, and review.