What the profile is
The profile is not just a static resume replacement. It is the system’s living source of truth. It holds identity, academic context, current status, experience, projects, goals, preferences, wins, and the career facts other surfaces need to make useful decisions.
What writes into it
Name, school, cohort, graduation timing, concerns, role/company for holders, and the initial career state.
Personal details, location, LinkedIn, academic fields, work experiences, projects, certifications, interests, and preferences.
Job landed, job lost, internship started, mode changes, and settings-driven career status changes.
Transcript review, resume hydration, and tracked experiences that add more context than a single prompt ever could.
What reads from it
- home or weekly surfaces decide what the next action should be
- jobs defaults and fit narratives use cohort, location, degree context, and current movement
- The Forge fills contact and education fields, checks depth, and grounds output in real facts
- Field Intelligence reads cohort and career state to generate a relevant lens
- tracker, reminders, and wins reflect where the user is actually moving
- public-profile settings decide what can be shared and what stays private
Why it compounds
A stronger profile improves every downstream read. Better jobs context creates stronger fit narratives. Better experience detail creates stronger resumes. Better status and wins create better nudges. The system should feel more aligned after each useful interaction, not equally shallow forever.
What it is not
- not a leaderboard identity
- not a one-screen summary built for public display first
- not a document that resets each time the user opens a new tool
- not public by default
Design consequence
If a new surface cannot meaningfully read from or write back to the profile spine, it will feel bolted on. That is usually a sign the surface should be redesigned or cut.