Terms / Glossary

AI considered a core capability, not an add-on.

Architecture assumes AI assistance in analysis, generation, or decision support from day one.

Product designed primarily as an application, not as content or documentation.

Focus on interaction, state, and workflows instead of static pages or articles.

Evidence-based framework for thoughts, emotions, and behavior.

Used as a structure, not a therapy replacement.

Not a book. An offline-first app.

CBT Cards is an application developed by MetalHatsCats for structured self-reflection and tracking.

Designing from limitations, not features.

Inspired by TRIZ. Constraints define the solution space.

Products built through rapid validation.

Small releases, real usage, fast feedback loops.

AI assists, humans decide.

Critical decisions stay with the user; AI provides structure and suggestions.

Personal system for behavior, habits, and mental models.

Combines tracking, reflection, and structured interventions into one workflow.

Data structured for analysis by language models.

Exportable, readable formats suitable for reasoning and reflection, not black-box storage.

Interface without visual noise.

Fewer components, clearer states, lower cognitive load.

App that works without internet by default.

Data is stored locally; sync is optional. Improves privacy, speed, and reliability.

Privacy embedded into architecture.

No mandatory accounts, minimal telemetry, user-controlled data export.

Team that builds and ships products end-to-end.

Research, design, engineering, and iteration under one roof, not staff augmentation.

Tools instead of explanations.

We prefer building usable systems rather than publishing guides or courses.

Method for solving contradictions.

Used to resolve constraints in product, design, and systems thinking.