← Back to selected work

ENGINEERING CASE STUDY / 06

Haveloc Placement Agent.

Application workflows with verification at every consequential step. Preparation before authorization.

AUTOMATION / WORKFLOWS
PythonFastAPIChrome ExtensionSQLAlchemy
SYSTEM ARCHITECTUREFLOW / 06
STEP 1 — DISCOVERINPUT BOUNDARY

PROJECT SCOPEMock-portal workflow. Successful external portal submissions are not claimed.

01 / CONTEXT

The problem worth solving.

Eligibility, deadlines, documents, and submission must be coordinated. A generated draft is not authorization to submit.

Engineering objectives

  • Validate eligibility and deadlines.
  • Keep sessions in the local browser.
  • Require verification and confirmation.

02 / SYSTEM DESIGN

Follow the flow.

LOGICAL DATA FLOWFLOW / 06
STEP 1 — DISCOVERINPUT BOUNDARY

Implementation details

  • A Manifest V3 extension handles browser interactions.
  • Backend services separate eligibility, deadlines, and resume selection.
  • Verification binds normalized answers to an integrity hash.

03 / TRADEOFFS

The reasoning behind the code.

01

Confirmation over assumption

A receipt is required before completion.

02

Human verification

CAPTCHA challenges pause automation.

Engineering challenges

Stale fields and ambiguous responses need read-back validation and careful retry rules.

Security & performance boundaries

Portal credentials remain in the browser. Single-use authorization is separate from drafting.

04 / EVIDENCE

What’s there. What’s next.

Extension source, backend services, lifecycle tests, and a mock portal are available.

Explore the source, documentation, and tests to inspect the implementation and its current boundaries.

Read the repository
NEXT CASE STUDY / 01Agentic Commerce