Declarative by design. Reviewable by people.

clarity.tool/v1

A contract people and systems can read.

The manifest is deliberately small. entry is a stable identity, display describes the native interface and permissions names every account boundary before installation.

{
  "schema": "clarity.tool/v1",
  "name": "Study outline",
  "version": "1.0.0",
  "entry": "study.outline",
  "summary": "A reviewed outline for a focused study session.",
  "consequenceClass": "C1",
  "permissions": ["profile.read"],
  "display": {
    "layout": "list",
    "icon": "list.bullet.rectangle",
    "color": "blue",
    "primaryColumnIndex": 0,
    "columns": [
      { "name": "Outline item", "type": "text" },
      { "name": "Done", "type": "toggle" }
    ]
  }
}

curl https://clarity.audecius.com/api/developer/v1/tools/validate \
  --request POST \
  --header "Authorization: Bearer $CLARITY_API_KEY" \
  --header "Content-Type: application/json" \
  --data @tool.json

Native presentation

Six layouts. Fifteen field types.

Layouts

table · routine · habit · counter · list · timer

Basic fields

text · number · toggle · date · rating · select

Extended fields

timer · photo · progress · currency · unit · multiSelect · link · color · location

Columns

At least 1 and at most 24. Every column has a visible name and supported type.

Identity

A stable SF Symbols identifier and a Clarity-supported tool colour; no third-party brand assets.

Least privilege

Only what is genuinely available today.

profile.read

Display name and profile language for a person-centred presentation.

sessions.read

Developer learning sessions and their status — no private day, health, school or family data.

Unavailable

Write access, health, grades, journal, messages, Family Screen Time, StoreKit and production credentials.

An installation may grant only a subset of the permissions in the reviewed manifest. A later version cannot silently adopt extra rights.

End-to-end

From an idea to a revocable installation.

1. 01

   Validate

   The sandbox deterministically checks the schema, consequence class, permissions and every declarative field type.

2. 02

   Preview

   The preview renders a review artefact. It executes no third-party code and reads no Clarity Account.

3. 03

   Human review

   Audecius reviews the purpose, minimum permissions, language, way back and claimed consequence class.

4. 04

   Install

   The person sees every requested permission and can grant, disable or remove each one.

5. 05

   Native sync

   Only compatible declarative manifests are represented in Clarity for the account. Web-only tools stay on the web.

6. 06

   Update or detach

   Empty tools adopt reviewed schema updates. Personal entries remain as a local copy when the tool is removed.