Skip to main content
Career Memory is the durable asset behind TLDT. It holds reviewed professional context that can be reused across real vacancies, interview preparation, owner testing, and optional recruiter-facing representation. A résumé can summarize roles and outcomes. Career Memory can also preserve the context needed to explain them: decisions, constraints, trade-offs, scope, dates, metrics, uncertainty, working style, and boundaries.

What makes Memory trustworthy

  • Owner supplied: personal facts begin with evidence the owner chooses to add.
  • Reviewable: content and Properties stay editable in a draft before publication.
  • Separated by state: Raw evidence, Derived summaries, drafts, and published versions do different jobs.
  • Explicitly published: runtime workflows use only an immutable version the owner approved.
  • Reusable: the same approved context can support Fast Check, Auto Simulate, Preview, Public Chat, and Public CV.

The Memory workspace

Open Memory from the owner sidebar:
  • Raw keeps original owner-supplied evidence.
  • Derived keeps concise operational explanations linked to Raw sources.
  • Properties describe retrieval, visibility, sensitivity, and special roles.
  • Drafts separate editable workspaces from live representation.
  • Versions hold immutable publications and let you activate an approved version.

Raw Memory

Use it for CVs, notes, transcripts, project records, dates, metrics, and original wording.

Derived Memory

Use it for focused project context, role explanations, evidence summaries, and representative guidance.

Reuse across workflows

A session never silently rewrites Memory. You may save supported session material to Raw Memory explicitly, then review it through the normal draft and publication flow.

Special roles

Each draft can have at most one Public document for each special role: A special role guides representation; it does not become evidence of work history. The document still follows Public/Private, sensitivity, review, and publication rules.
A useful Memory preserves the uncomfortable edges: team vs. individual ownership, approximate vs. exact metrics, missing dates, negative results, and limits. Honest context improves both preparation and representation.