Design Principles

← Back

This page is not an implementation guide for the idk-lamp.
When designing the idk-lamp, the core question is:
How do we determine where to stop the decision?
This page offers a perspective for that inquiry.

01. Boundary

A boundary is not a line
dividing "can" from "cannot".

It is the position that separates
who accepts the responsibility for the result.

AI can execute many judgments.
However, it cannot become the subject
that bears the responsibility.

As judgment proceeds,
responsibility moves somewhere.
The boundary handled by the idk-lamp is
the point where the destination of responsibility shifts.

02. Decision Hold

Holding judgment is not
abandoning it.

It is
explicitly stating the state of not being able to accept responsibility yet.

The judgment remains undetermined.
The process has not failed.
Nor does it proceed automatically.

Decision Hold is not
an action of "stopping",
but a design of a state.
When this state is established,
the idk-lamp lights up.

03. Gate

The gate is not
a device to stop judgment.
Nor is it a checklist
to evaluate if passing conditions are met.

The gate verifies only one thing:
How far is it safe for this judgment to proceed?

Passing through does not mean
automatic execution.
The failure to pass is, in itself,
critical information.

The gate does not
evaluate the correctness of the judgment.
It is placed as a mechanism
to ensure the judgment is entrusted to the right entity.

The idk-lamp is not
a design for stopping decisions.
It is a design for
returning decisions to the place where they can be properly undertaken.