JobJitsu Long-term Roadmap
Directional arc for the AI Career Operating System — not a release schedule or implementation plan.
Parent: PRODUCT_VISION.md · Modules: FEATURES.md · Guardrails: NON_GOALS.md · PRINCIPLES.md · TERMINOLOGY.md
Overview
Each horizon deepens the Career OS without abandoning JobJitsu identity: local-first, craft over volume, agent as belt not leash, calm confidence.
Horizon 1 — The Application Dojo (foundation)
Establish JobJitsu as the trusted local system for the classic pipeline:
search → curate → tailor → queue → approve → send → follow up
Focus: Identity & resume, preferences, local intelligence, agent, discovery, applications, queue & review, send, follow-ups, privacy chrome.
Outcome: A calm desktop companion with visible Agent · On-device status, user-owned agent, and mastery-over-volume defaults.
Horizon 2 — The Full Hunt Loop (depth)
Close the loop after the throw: outcomes, notes, timelines, and gentle learning from what worked — still on-device, still without FOMO metrics.
Focus: Timeline & memory depth, outcomes & reflection, clearer “what left / what stayed.”
Outcome: One coherent OS for “what I sent, what I nudged, what I learned,” not a pile of disconnected tools.
Horizon 3 — Career Craft Beyond Apply (breadth)
Extend the same philosophy into adjacent craft surfaces — interview readiness, narrative coherence, role-fit reflection — as modules inside the same dojo, never as a separate hype product or cloud upsell.
Focus: Future modules that pass PRINCIPLES.md and NON_GOALS.md.
Outcome: JobJitsu is credibly an AI Career Operating System, not only an auto-apply utility.
Horizon 4 — Sovereign Ecosystem (enduring)
An open, extensible local career OS: community-visible agent skills, optional bridges only when the user initiates outbound action, identity intact — calm, private, craft-first.
Focus: Extensibility, portability, multi-path careers — still local-first.
Outcome: The default choice for people who refuse to outsource their career data.
Roadmap discipline
Before advancing a horizon item:
- Does it deepen the Career OS or distract into a side quest?
- Does it violate a non-goal?
- Does it pass the principle checklist?
If any answer fails — redesign or reject. No implementation details belong here; this file stays vision-level only.
