How Dilly Works

One connected system, not a stack of disconnected tools.

Dilly works because the profile, the mode, and every major surface read from shared context.

This site explains the internal logic behind Dilly. Why one profile can power jobs, coaching, resumes, tracking, and field intelligence. Why the experience changes when career status changes. Why the system gets sharper as the user adds signal.

Start with the Profile See the Surface Map
Core Pages

The five pieces that make the system hold together.

Dilly is easiest to understand when you break it into its core layers: source of truth, system state, surfaces, compounding signal, and boundaries.

Source of truth The Profile Spine How one living profile stores the facts, goals, and context the rest of Dilly reads from. Read the profile logic → System state The Mode Engine Why Student, Seeker, and Holder are not separate products, but different operating states on top of the same profile. Read the mode logic → System surfaces The Surface Map How home, jobs, Forge, Arena, tracker, and chat each read and write different parts of the same system. See the system map → Compounding signal The Signal Loop How one action sharpens the next one, so Dilly feels more useful over time instead of resetting every session. Follow the signal loop → Guardrails The Boundaries What the system will and will not do, where trust lives, and why connected does not mean unbounded. See the boundaries →
System Principles

The rules underneath the experience.

01 The profile is the source of truth. Dilly is built around a person, not around a resume, a one-time prompt, or a feed session.
02 Mode changes the lens, not the person. Student, Seeker, and Holder change priorities, language, defaults, and actions. The underlying identity carries across.
03 Every surface reads shared context. Jobs, Forge, Arena, and coaching should feel related because they are reading the same underlying record.
04 The system compounds with use. The best next action becomes clearer when the user adds profile depth, tracks movement, and closes loops.
What Moves Together

When one thing changes, the rest of the system should react.

The system is strongest when state changes are not isolated. A new role, a stronger profile, a tracked application, or a completed learning step should affect what rises next.

Example

If a user moves from Seeker to Holder, Dilly should not behave like a brand-new account. The profile remains. The tabs relabel. The jobs feed changes. Weekly intel becomes more relevant. The system adapts around the same person.

Profile change A deeper profile sharpens jobs, Forge, and coaching. Richer experience data makes fit narratives stronger, resume output more grounded, and home nudges more specific.
Status change A mode flip should reframe the front door. The system changes language, tabs, filters, and hero actions without throwing away prior history.
Loop closure Tracked movement creates better next actions. Applied roles, wins, and changed goals give Dilly better reasons to nudge the user toward the next useful move.
Read This Alongside

Method sits between help, privacy, and vision.

This site explains system logic. It is not usage support, and it is not the trust hub. Those surfaces stay separate on purpose.

Neighbor sites