Development plan

Build the record before you build the router.

Each phase has to be usable on its own. Later phases are written down so we do not pretend they already exist.

1. 01

   V1 — Name the source

   In this build

   The desk is pointed at Studionet 0x23C029E1aB24f74b355EF05f7b540296BEdD6279. A write still has to be signed by the wallet in this browser. A stored assessment is not permission to move capital.

   • Host registry so evidence cannot point at a private network
   • Policies as structured switches, not a paragraph a model can reinterpret
   • Classification inside GenLayer, using comparative consensus
   • Approve, reject, or review decided by code after consensus
   • Reassessment that keeps every earlier reading
   • Sign screen that calls genlayer-js from the connected wallet
   • Explorer that labels fixtures instead of pretending they are live
2. 02

   V1.1 — Notice when it changes

   Planned

   Not built. Do not treat a mention on this page as a feature.

   • A scheduled re-read of markets you already care about
   • A plain alert when the primary source changes
   • More documentation hosts, added by the owner one at a time
   • Tighter parsers for a few well-known protocols
3. 03

   V1.2 — Let a vault listen

   Planned

   A consumer, not a new decision maker.

   • A small SDK that reads a finalized assessment
   • Policy templates a desk can copy
   • A webhook after finality, carrying the stored verdict only
4. 04

   V2 — Let capital follow a rule

   Planned

   Out of scope until the classification record is boringly reliable.

   • Hooks a treasury can call only after an approval
   • Coverage beyond the first documentation set
   • Controls an institution can audit without reading Python

The rules behind the current phase are in the docs.