Home or Weekly

The orchestration screen. 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.

Reads

profile facts, mode, wins, status, open loops, market context

Creates

urgency, nudges, sequencing, and the app's current front door

Jobs or The Market

The opportunity-reading screen. It understands the user's cohort, location, degree context, and current state, then frames roles through fit narratives instead of raw listing spam.

Reads

cohort, metros, degree context, mode, profile strengths, tracked jobs

Creates

fit signals, next-step actions, tracker entries, and prompts for tailoring or chat

Resume Audit and The Forge

The artifact screens. Audit diagnoses the existing document. Forge generates a role-specific one. Both stay grounded in the profile so the output gets sharper without drifting into fiction.

Reads

profile facts, target role, job description, uploaded resume, education and contact fields

Creates

clarity on gaps, role-specific artifacts, and stronger evidence for later actions

Talk with Dilly

The context bridge. 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.

Reads

current screen context, profile facts, tracked goals, plan limits, prior prompts

Creates

clarification, next actions, durable facts written back to the profile

Field Intelligence (AI Arena)

The capability-building screen. One page with eight sections that explain what AI is doing to the user's field, who their cohort is, what role drift looks like, and what to learn next.

Reads

cohort, profile depth, role interests, disruption context, learning history

Creates

preparedness, capability growth, and Skills hooks for future search or advancement

Tracker, calendar, wins, reminders

The continuity screens. They turn movement into memory. Applications, deadlines, offers, and wins do not disappear after a single session. They affect what the system believes is important next.

Design consequence

If a screen cannot point to the profile fields it reads, the state changes it reacts to, and the context it creates for later screens, it is not integrated enough yet.

Related pages