Intelligent Career

Any document in the swarm can be sent here (ADR-139 Send to…) and absorbed into your profile. Single-tenant, multi-user (per-user isolation); multi-tenant ready.

• Career Database. Read the signed-in user's career-hunter data — scored job matches, applied/generated pipeline counts, fresh high-fit roles, and resume gap themes — from their migrated jobs database
• Draft Application. Write the tailored resume + cover letter PDFs for ONE approved posting — the engine tailors against the user's real profile (its own LLM pass under their connected key) and returns the…
• Draft Application (OSHAL variant). Same as career_draft but includes the OSHAL/open-source resume section. OPT-IN only
• Score Fresh Postings. AI fit-score the signed-in user's fresh in-lane postings (bounded to recent postings; the engine's own scoring pass under the user's connected key)
• Refresh Jobs Database. Start the full jobs-database refresh NOW — scrape every company's ATS feed, re-index all users' keyword matches, AI-score the new roles, and queue the top drafts
• Refresh Status. Whether a jobs-database refresh is currently running, plus the corpus's newest last-seen timestamp (how fresh the data is)
• Read Resume (Master Document). Read the signed-in user's editable resume document — the durable master career profile (headline, summary, competencies, experience with bullets, skills, clearance) every tailored resume is…
• Save Resume Edits. Apply an edited resume document — 'master' saves the durable career profile through the whitelist write-back (backup snapshot + audit), a numeric postingId saves that job packet's tailored…

1. 01

   You open it, or the assistant does

   Opening ?app=career-hunter loads its 14 screens into the shared cockpit, starting on career-board. The ribbon, the ticket list and the assistant are already there — the app contributes views, not a second application to log into.

2. 02

   Or you just ask

   The assistant classifies what you asked for and hands it to the bot that owns that domain. You do not pick the app, and you do not learn a command — routing is by declared capability, not by keyword matching a menu.

3. 03

   A named bot picks it up

   career-hunter is accountable for the work. 13 declared capabilities say what it is trusted to do; the tokens and dollars it spends are recorded against that identity, so the cost has a line item rather than disappearing into a monthly bill.

4. 04

   Longer work becomes a ticket

   Scheduled and swarm-initiated work enters the queue as a career-application ticket. It is durable, it has an owner, you can watch it move through its phases, and if it fails it fails somewhere you can open and read.

5. 05

   The result lands where you can check it

   Back on the app's own screens, as state you own — not as a chat message you have to scroll back to find.

• Routing is by declared capability, not by keyword. career-hunter advertises what it is accountable for, and the assistant matches against that.
• Asks that land here: anything about ats scraping, anything about job scoring, anything about resume generation, anything about cover letter generation, anything about careers discovery, anything about job search.
• The specialist does the work, not the assistant. Cost, permissions and audit stay attached to the bot above — delegation does not launder accountability.
• It will tell you when it cannot. If a request needs your screen — an approval, a payment, a login — it says which app to open rather than guessing.

• Other apps: Portrait Studio. Install is dependency-aware and refuses to orphan them.
• Platform capability: graph notifications — reached by declaration, never by copying platform code into the package.

All 6 knowledge apps →