Clarity Trust · Action safeguards

Impact determines the boundary.

Reading, recommending, changing and acting for other people are not the same. Clarity therefore assigns every supported action a consequence class from C0 to C4 before execution.

From source to receipt

No direct jump to execution.

Clarity separates source, signal, context, plan, approval and result. That keeps the origin of a suggestion and the threshold before its effect visible.

  1. 01

    Sources

    Native permissions, manual imports and Clarity data you created.

  2. 02

    Signals

    Changes enter as bounded signals tied to their source.

  3. 03

    Context

    Role, time, permissions and relevance determine what belongs together.

  4. 04

    Plan

    Clarity forms a traceable next step or preview.

  5. 05

    Approval

    The consequence class determines whether observation, your approval or a human-only path applies.

  6. 06

    Receipt

    Executed or rejected steps receive a result, time and — where possible — undo.

C0 bis C4

Responsibility rises with consequence.

The class does not describe how impressive a feature is. It describes how much effect it may have and who must make the final decision.

C0
Consequence class

Observe

Reads or shows. Changes nothing.

No execution path required.

C1
Consequence class

Suggest

Puts information in context and recommends a next step.

A human decides and acts.

C2
Consequence class

After your approval

Prepares a real change.

Preview and explicit approval before execution.

C3
Consequence class

Within your boundary

May act only within a predefined, reversible boundary.

Daily budget, live permission, receipt and undo; never on behalf of other people.

C4
Consequence class

Human only

Payment, medicine, law, identity or particularly sensitive safety.

Clarity may prepare, but not execute autonomously.

A reversible C2 action · Example

See first. Then decide.

A preview makes the intended change concrete before it runs. This example shows a bounded, reversible route — not a blanket promise for every action.

SourceToday · Mathematics task

Interactive example · no live execution

C2 · PreviewNothing changed yet

Mathematics task

Today17:00
Tomorrow17:00

Only this task. Other tasks and events stay the same.

Safeguards that remain visible in the route

Four states. Not four footnotes.

01

Preview

Shows what is intended to change and which area is affected before a real change.

02

Your approval

A C2 action runs only after your explicit approval.

03

Receipt

The result remains visible as a traceable step — even when execution was declined.

04

Undo

For supported reversible changes, undo belongs to the route and is not mentioned only in small print.

C3 · Within your boundary

Autonomy needs a smaller box, not more trust.

C3 may act only inside a reversible boundary set in advance. The technical control contract requires a daily budget, live permission, a receipt and undo — and never permits this route for other people.

BoundarySet in advance
  • Daily budgetRequired
  • Live permissionRequired
  • Receipt and undoRequired
  • For other peopleNot permitted
C4

Human only.

Clarity may prepare steps involving payment, medicine, law, identity or particularly sensitive security, but may not execute them autonomously.

Safety interruptionPreview

Global Stop

One central route to stop immediately.

Global Stop belongs to the target design for the next generation of Clarity. It will be called available only after the complete route has been reviewed. Until then, this presentation is explicitly a preview.

Status
Preview
Release
Only after complete end-to-end review
Purpose
Centrally interrupt supported autonomous action routes

A useful action remains an accountable action.

The AI route, consequence class and technical state can be reviewed separately.

Clarity action safeguards — C0 to C4, preview and undo