Validating canonical manifest
Preparing the bounded interface
The stable shell remains available while the manifest, registries, bindings, and permissions are checked.
Adaptive Home
Current plan
The validated manifest selects the smallest useful interface for this goal.
Interface Comparison Lab
Same data. Three manifest policies.
The modes differ by structural policy, not by separate scenarios or hand-coded screens.
Seeded demonstration fixture
Authored scenario values for exploring the hypothesis—not experimental validation.
| Metric | Fixed | Generated once | Bounded adaptive |
|---|
This browser session
Observed locally since evidence was last reset.
Confidence after the task
A user-entered self-report, stored separately from observed events.
A prototype can demonstrate a mechanism, not prove superiority.
A real evaluation would randomly assign comparable tasks to Fixed, Generated Once, and Bounded Adaptive policies; keep data and goals constant; pre-register outcome measures; capture errors and completion times; and collect blinded post-task confidence. Clearframe’s seeded fixture is not that study.
Interaction Evidence
Seeded evidence and observed behavior stay separate.
Local events may support a deterministic proposal; they are never described as model learning.
Observed session
Local browser session
Demonstration fixture
Pre-authored friction signals retained for repeatable scenarios.
Adaptation Proposals
Review resulting manifests, not promises.
Every proposal is applied to a clone, schema-validated, registry-validated, pin-checked, and mode-checked before it can be accepted.
No selection
Select a patch to inspect
Current and resulting manifests, evidence, semantic changes, and validation will appear here.
UI Manifest Inspector
One source-of-truth chain.
The standalone file embeds the exact canonical JSON used by build-time and runtime validation.
Version domains
ExplicitSource reconciliation
IdenticalActive runtime manifest
Read-only structured plan; never executed as code.
Capability & Safety Center
Choice is not authority.
Components and actions are independent registries. Unknown identifiers are rejected before rendering or execution.
Action registry
Classification, authority, preview, and confirmation remain independent of planning.
| Action | Class | Permission | Safeguard |
|---|
Component registry
Allowed regions, bindings, actions, accessibility, and risk.
| Component | Regions | Risk | Pin |
|---|
Validation attempts
Rejected plans remain inspectable and non-executable.
Adaptation History
Complete snapshots, semantic diffs, coherent undo.
Operational business data remains separate from interface restoration.
Interface snapshots
Select exactly two for a semantic comparison.
Semantic comparison
DerivedNo comparison yet
Select two complete snapshots and compare them.
Methodology
Bounded plasticity, implemented honestly.
Clearframe Lab is an original product exploration conceptually inspired by the usability principles in Steve Krug’s Don’t Make Me Think. It is not affiliated with the author or publisher.
Manifest-driven renderer
Adaptive regions are produced from validated canonical manifests and allowlisted component functions.
Rule-based planner
Goal, telemetry, and data-type triggers produce constrained patch JSON without pretending a live model is present.
Repeatable fixtures
Authored interaction evidence supports scenarios but is never presented as experimental proof.
Planner-adapter boundary
A future model could propose the same schema-valid patches. It would not receive rendering, permission, or execution authority.
Not a conclusion
The prototype investigates whether bounded adaptation reduces avoidable thought while preserving learnability.
Untrusted by default
Data, labels, rationale, and future model output are rendered as text and validated before use.
Each number governs a different contract.
0.2.4 is the product archive release. 3.5.0 is the starting UI-manifest snapshot. 2.1.0 governs component contracts. 1.1.0 governs actions and schema. 2026.07.30.2 identifies the fictional operational-data fixture. Data refreshes do not increment the structural manifest.