Tool Design & Review

Guided implementation

From the boundary to a verifiable result.

1. 01

   Define the effect before the interface

   C0 reads or presents, C1 proposes, and C2 prepares a real change only after an explicit yes. Higher classes are closed to third parties.

2. 02

   Describe a declarative display

   Choose one of the six supported layouts and use only documented column types.

   {
     "schema": "clarity.tool/v1",
     "name": "Study outline",
     "entry": "study.outline",
     "consequenceClass": "C1",
     "permissions": [
       "profile.read"
     ],
     "display": {
       "layout": "list",
       "icon": "list.bullet.rectangle",
       "color": "blue",
       "columns": [
         {
           "name": "Outline item",
           "type": "text"
         },
         {
           "name": "Done",
           "type": "toggle"
         }
       ]
     }
   }

3. 03

   Validate on the server

   The sandbox deterministically rejects unknown layouts, types and permissions. A preview does not execute anything.

4. 04

   Explain the review request

   Submit the name, version, summary, manifest and consequence class. Approval is a human decision and remains revocable.