◉ MEMLAB / HOMEEXPERIMENT 005 / FORENSIC MODE
THE INVESTIGATOR'S INSTRUMENT

THE OBSERVABILITY
MACHINE.

What your customer sees is only the surface. Control a simulated app. Scrub through its hidden execution. Spend a limited evidence budget, find the divergence, and identify the root cause.

01 / CHOOSE YOUR CASE FILE
VISIBLE REALITY / CLIENT UI

The customer experience

NORTHSTAR / ACCOUNT

Profile settings

Change the preferred display name and save.

Ready to save.
AdaDISPLAYED NAME
AdaPERSISTED NAME

The database value is visible here for learning; in a real system it might require an authorized backend inspection.

HIDDEN REALITY / TIME MACHINE

Scrub the execution

01UI
02REQUEST
03API
04STORE
05VIEW
T+000ms / select an event
Execute a save to generate a trace.

The customer only sees the current screen and its feedback. The system’s actual state may be different.

EVIDENCE LOCKER / 3 CREDITS

What will you inspect?

Every inspection costs one credit. Open evidence before making your diagnosis.

3CREDITS REMAIN
0 / 4ARTIFACTS OPENED
Evidence not yet requested.
03 / INVESTIGATOR'S DECISION

Where did reality diverge?

THE WEAK TEST
await page.getByRole('button', { name: 'Save changes' }).click();
await expect(page.getByText('Saved')).toBeVisible();
// Does this prove persistence?
THE STRONGER HYPOTHESIS
await page.getByRole('button', { name: 'Save changes' }).click();
await page.reload();
await expect(page.getByLabel('Display name'))
  .toHaveValue('Grace');
// Assumes persisted state is loaded on reload.