> cat /system/feature-log.txt CURRENT v1.0.0

FEATURE LOG_HOW PROBLEM.ME GOT HERE.

A compact record of the meaningful product releases. Small fixes may ship between entries; this log tracks changes that altered what problem.me can actually do.

CURRENT RELEASEv1.0.0
STORAGE MODELLOCAL-FIRST / INDEXEDDB
CONNECTED WORKSPACE5 WHYS + FISHBONE + PARETO

RELEASE HISTORY_

NEWEST → OLDEST
v1.0.0CURRENT
LOCAL-FIRST WORKSPACE

One investigation. A clearer next step.

The first stable release brings the existing workspace, learning layer and shared navigation together. CAPYBARA.EXE is ready; your conclusions still need evidence.

  • 5 Whys, Fishbone and Pareto with one Evidence Ledger
  • Private Sessions and browser-local investigations
  • Portable .problemme exports; schema 1, 2 and 3 compatibility
  • Four Field Guides and plain-language privacy notes
  • Shared navigation and readable mobile layouts
  • No accounts, cloud sync or AI reasoning engine
v0.9.2RELEASED
KNOWLEDGE + PRIVACY

Methods you can read. Privacy you can understand.

The technique library gains practical field guides, while Capybara explains the boundaries of local storage, Private Session and portable exports.

  • Four technique field guides
  • Dedicated plain-language privacy page
  • Capybara privacy notes in workspaces
  • Readable .problemme export warning
  • Local / Private Session boundaries explained
  • No investigation schema change
v0.9.1STABILIZATION
STABILIZATION

Safer saves. Clearer next steps.

Shared Pareto joins the investigation flow, with stronger local-save and Private Session boundaries.

  • Three connected techniques / schema 3
  • Pareto handoffs after data entry
  • Atomic conflict-safe local saves
  • Private Sessions leave saved copies intact
  • Safer legacy migration
  • Mobile and browser regression checks
v0.8.1LOCAL LIBRARY
MY INVESTIGATIONS

Multiple problems. One local library.

The shared workspace became a real investigation library instead of a single saved pilot.

  • IndexedDB investigation storage
  • My Investigations dashboard
  • Continue / duplicate / export / delete
  • Search and status filtering
  • Legacy pilot migration
  • Private Sessions remain unsaved
v0.8SHARED PILOT
INVESTIGATION MODEL

An investigation contains techniques.

5 Whys and Fishbone moved inside one shared investigation with one reasoning trail.

  • 5 Whys + Fishbone in one case
  • Shared Evidence Ledger
  • Fishbone cause → 5 Whys handoff
  • Portable .problemme v2 files
  • Private / local workspace modes
  • Versioned investigation schema
v0.7.1PILOT
PORTABLE CASE FILES

Investigations become an object.

The first named investigation pilot proved local save plus portable import/export using 5 Whys.

  • Named investigation snapshot
  • .problemme export / import
  • Schema validation
  • Private-safe behavior
v0.6REASONING
REASONING LAYER

Keep evidence separate from assumptions.

Every technique gained a shared reasoning pattern around the method itself.

  • Evidence Ledger
  • FACT / ASSUMPTION / TEST / RESULT
  • Technique handoffs
  • Local-first context transfer
  • Capybara reasoning guidance
v0.5.3PRIVACY
PRIVACY PARITY

Private Session everywhere.

All interactive techniques adopted the same explicit local/private storage behavior.

  • Private Session mode
  • Local save remains opt-in/out
  • Clear All Local Data
  • Credential / token warnings
v0.5.2REPORTS
EXPORT

Turn the reasoning into a document.

The interactive tools gained structured print and Save-to-PDF reports.

  • Technique-specific PDF layouts
  • Evidence included in reports
  • Local generation in the browser
  • Print-friendly styling
v0.4INTERACTIVE
TOOLS

Case Files became usable workspaces.

The four teaching techniques moved from examples into interactive tools for real problems.

  • Interactive 5 Whys
  • Interactive Fishbone
  • Interactive Pareto
  • Interactive Kepner–Tregoe
  • Local browser drafts
  • Copy / reset / print actions
v0.3LIBRARY
INFORMATION ARCHITECTURE

A proper Technique Library.

The site stopped being only a homepage and became a navigable set of Case Files.

  • Technique Library page
  • Four coordinated Case Files
  • Goal filters and local search
  • Previous / next Case navigation
  • Consistent technique metadata
v0.2.1POLISH
DESIGN SYSTEM

The Case Files learned to speak the same language.

Shared terminal styling, headers, responsive behavior and hero structure were standardized across techniques.

  • Canonical palette and typography
  • Unified Case File header
  • Consistent hero identity
  • Mobile-responsive layouts
  • Accessibility and focus polish
LOGGING RULE_ This page records meaningful product releases, not every commit or bug fix. The current architecture remains local-first: browser storage is convenient, while exported .problemme files are the portable backup.