idk-lamp Start • Demo → Install → Gate

idk-lamp in 5 Minutes

The idk-lamp is a quiet signal that lights up when AI should not make a decision.
It is not an error or a failure. It is a "boundary signal" to return judgment to humans.

Step 1
Experience It

Check the lighting, states, and atmosphere from the theme list.

Open Demo
Step 2
Install

Just paste the CDN link and place the tag. Ready to drop in.

Go to Install
Step 3
Define the Boundary

Define "when not to let AI decide" using the Gate.

Go to Gate
Integration Concept: The UI (idk-lamp) and the Operational Gate (predictability-gate) have different roles.
That is why this site unifies only the workflow.
Read Concept Try Demo idk-lamp Repo predictability-gate Repo

Role of this Page

This is not a "manual", but a page to align the implementation order.

What you get

• Instantly understand "what the signal is" via Demo
• "Ready to place" via CDN
• "Consistent trigger points" via Gate

What is not here

• Detailed Philosophy (→ Concept)
• Full Theme Guide (→ Demo)
• Full Specs & Implementation (→ Repos)

Install: Drop-in (CDN)

Minimal setup to "just try it out". Ready for sites or PoCs.

1) Load CDN

<script src="https://idk-lamp.org/dist/idk-lamp.min.js"></script>

2) Place the Tag

<idk-lamp state="idk" label="Need human decision"></idk-lamp>

3) Adjust look with CSS Variables (Example)

:root { --idk-lamp-size: 84px; --idk-lamp-glow: 1; --idk-lamp-label-opacity: 0.9; }

* Check the idk-lamp repository for the latest specs on state, theme, and variables.

Demo: Experience It

First, choose what fits your product. Compare the lighting atmosphere in the theme list.

Open Demo View Themes/Specs

Gate: Define the Boundary

idk-lamp is a "signal".
For the signal to work, you first need to define when to light it (conditions for AI not to decide).

What predictability-gate covers

• Translating "uncertainty" in prediction/inference/generation into operational decisions
• Defining conditions for deferring judgment (who checks what and when)
• Establishing that "stopping" is a normal operation, not an error

Read predictability-gate
Recommendation: When the Gate returns STOP/DEFER, light up state="idk" in the UI.
This creates a consistent experience of "Stopping → Returning to Human".

FAQ

Is this a "warning light"?

No. idk-lamp is not for indicating "danger", but a signal to return judgment.
It visualizes the "boundary of responsibility" on the UI, rather than replacing alerts.

Why keep Demo, Repo, and Gate separate?

Because their roles differ.
Demo is for experience, idk-lamp repo is for artifacts, and predictability-gate repo is for operational judgment.
Unifying only the workflow here prevents the concept from breaking.

Where should I start?

If unsure, go Demo → Install (here) → Gate.
Making it "placeable" first brings the Gate discussion into reality.