Jobber/orchestrator.md at 1f929dfc7f1f2d76093c9b14bb7fba0135f01aa0

Shaheer Sarfaraz 1f929dfc7f

Create the setup for the documentation page (#171 )

* don't run for generated docusaurus

* format

* workflow to autoupdate docs version

* fix versioning

* add link back to app

* remove old docs

* html link???

* don't track .docusaurus

* documantation build

2026-02-15 22:50:52 +00:00

2.5 KiB

Raw Blame History

id, title, description, sidebar_position

id	title	description	sidebar_position
orchestrator	Orchestrator	Job states, ready flow, and PDF generation/regeneration behavior.	1

This guide explains job states, how jobs become ready, and how PDF generation works.

Job states

discovered: Found by crawler/import, not tailored yet.
processing: Tailoring and/or PDF generation in progress.
ready: Tailored PDF generated and ready to apply.
applied: Marked as applied.
skipped: Explicitly excluded from active queue.
expired: Deadline passed.

Intended ready flow

1) Manual flow

Job starts in discovered.
Open in Discovered panel and choose Tailor.
Edit JD/tailored fields/project picks.
Click Finalize & Move to Ready.

2) Auto flow

Pipeline scores discovered jobs.
Top jobs above threshold are auto-processed.
Jobs move directly to ready with generated PDFs.

Ghostwriter

Ghostwriter is available in discovered and ready job views.

For details, see Ghostwriter.

Generating PDFs (first time)

PDF generation uses:

Base resume selected from RxResume
Job description
Tailored summary/headline/skills/projects

Common paths:

Discovered → Tailor → Finalize
- POST /api/jobs/:id/process
Ready → Regenerate PDF
- POST /api/jobs/:id/generate-pdf

Regenerating PDFs after edits

If JD or tailoring changes, regenerate PDF to keep output in sync.

API flow

PATCH /api/jobs/:id
{
  "jobDescription": "<new JD>",
  "tailoredSummary": "<optional>",
  "tailoredHeadline": "<optional>",
  "tailoredSkills": "[{\"name\":\"Backend\",\"keywords\":[\"TypeScript\",\"Node.js\"]}]",
  "selectedProjectIds": "p1,p2"
}

POST /api/jobs/:id/summarize?force=true
POST /api/jobs/:id/generate-pdf

Post-application tracking

For inbox routing flow and setup, see Post-Application Tracking.

Notes and gotchas

processing is transient. On PDF failure, job reverts to discovered.
PDFs are served at /pdfs/resume_<jobId>.pdf with cache-bust on updatedAt.
skipped/applied jobs can be reopened by patching status to discovered.

External payload and sanitization defaults

LLM prompts send minimized profile/job fields.
Webhooks are sanitized and whitelisted by default.
Logs and error details are redacted/truncated by default.
Correlation fields include requestId, and when available pipelineRunId and jobId.

2.5 KiB Raw Blame History