Home or Weekly
This is the orchestration surface. It decides what should matter now. It reads profile depth, career status, wins, stale facts, open loops, tracked applications, and mode to choose the most relevant next action.
profile facts, mode, wins, status, open loops, market context
urgency, nudges, sequencing, and the system’s current front door
Jobs or The Market
This is the opportunity-reading surface. It should understand the user’s cohort, location, degree context, and current state, then frame roles through fit narratives instead of raw listing spam.
cohort, metros, degree context, mode, profile strengths, tracked jobs
fit signals, next-step actions, tracker entries, and prompts for tailoring or chat
Resume Audit and The Forge
These are artifact surfaces. Audit diagnoses the existing document. Forge generates a role-specific one. Both should stay grounded in the profile so the output gets sharper without drifting into fiction.
profile facts, target role, job description, uploaded resume, education and contact fields
clarity on gaps, role-specific artifacts, and stronger evidence for later actions
Talk with Dilly
This is the context bridge. It should feel available from anywhere because it is how the user pulls the rest of the system into one conversation, seeded from the current screen and current moment.
current screen context, profile facts, tracked goals, plan limits, prior prompts
clarification, next actions, and more signal that later surfaces can use
Field Intelligence and Skills
These are capability-building surfaces. Arena explains what AI is doing to the user’s field. Skills helps close the gap that Arena or jobs exposed. Together they keep the system from becoming purely reactive.
cohort, profile depth, role interests, disruption context, learning history
preparedness, capability growth, and better options for future search or advancement
Tracker, wins, and reminders
These are continuity surfaces. They turn movement into memory. Applications, deadlines, offers, and wins should not disappear after a single session. They should affect what the system believes is important next.
Design consequence
If a surface cannot point to the profile fields it reads, the state changes it reacts to, and the context it creates for later surfaces, it probably is not integrated enough yet.