PopIt3 (running on pomelo) processes incoming emails and manages job data.Ask (this project) uses that job data to generate applications.These are separate but complementary systems.
1. Email arrives at john.js@critchley.biz from JobServe2. PopIt3 processes via POP3/OAuth2, stores in GDBM database3. PopIt3 generates report at home.critchley.biz/jobs (when pomelo at home)4. You copy job description from report or PopIt3 saves file5. Ask processes job description with your CV → JSON6. Ask generates DOCX files for application
PopIt3 maintains:• Jobs table/database (GDBM format)• Job descriptions• Analysis results• Application trackingSee popit3/job-analysis for storage details.
From PopIt3 report:1. Visit home.critchley.biz/jobs (requires pomelo at home)2. Click job posting3. Copy full job description text4. Save to file: jobs/JS-12345.txtOr PopIt3 auto-saves:1. Check if PopIt3 job handler saves to directory (see popit3/job-analysis)2. Extract from email: use jobs/extract_job.py on .eml file
If you need to query PopIt3 jobs from Ask:1. PopIt3 GDBM database location: See popit3/database docs2. PopIt3 API endpoint: home.critchley.biz/jobs (when pomelo at home)3. Current workflow: Manual copy-paste (simpler, less coupling)
Benefits of current design:• Ask tool remains general-purpose (not hardcoded to email workflow)• Each system focuses on its domain (email processing vs document generation)• Manual step allows review before generation (quality control)• Can use Ask for other purposes (code review, document analysis, etc.)
Potential improvements (not currently implemented):1. Read job descriptions directly from PopIt3 database2. Automatically generate applications for new job posts3. Track which jobs have been applied to (integration with PopIt3 tracking)4. Auto-upload generated CVs/cover letters to JobServe API