Dataset viewer

My email

saved Feb 13, 2017 22:53trap
1linked record
2named, not linked

Fields

NameMy email
Passcode variantEmail Password
PasscodeCoonvalley55!Mail
Emailpeg.ostrander@badgermail.example
DescriptionChanged in June 2025 after the business with the Mastercard.

Linked to

1 record, 2 more named

→ the link goes from this record; ← it comes from the other one. These are the edges the build gives the app. A name in the text is only a match on the words and is never treated as a link.

Comments

0

Comments are added in the local viewer; this copy is read-only.

Why it exists

someone_elses Peg and Ray each have a debit card PIN, a telephone code, a patient portal login, a Social Security login and an email password. "My" means Peg's.

In the app

missing

From the app's own code (viewer/app_export.sh): Not made yet: run viewer/app_export.sh retired-couple.

One step out

assign_to →Peg Ostrander — Contact; assign_toPeg OstranderMy email

As the app receives it

1

The graph nodes the build makes for it: the record, and its phones, emails, addresses, pictures and files.

{
 "$type": "n_type_passcode",
 "id": "n_pc_email_peg",
 "createdAt": "1487026398595",
 "name": "My email",
 "passcodeVariant": "Email Password",
 "email": "peg.ostrander@badgermail.example",
 "passcode": "Coonvalley55!Mail",
 "description": "Changed in June 2025 after the business with the Mastercard."
}

Source

personas/retired-couple/records/passcodes.yaml:196

- id: pc-email-peg
  kind: passcode
  for: me
  name: My email
  passcodeVariant: Email Password
  email: peg.ostrander@badgermail.example
  passcode: "Coonvalley55!Mail"
  description: Changed in June 2025 after the business with the Mastercard.