The problem I started with
I built a career operations system because finding work itself involves research, source evidence, preparation, approvals and follow-through. Using it made the difference between a submitted form and a confirmed result very concrete.
How I approached it
I treated claims, duplicate checks and completion receipts as operational records. The public example uses synthetic cases so the state transitions can be tested without publishing anyone’s CV, correspondence or application history.
- Connect a claim to its evidence
- Check whether the case already exists
- Keep approval separate from execution
- Verify the receipt before recording completion
What is implemented
Claim-wording and receipt checks are adapted from the existing Python implementation. A newly written in-memory SQLite harness makes the duplicate and state-transition gates inspectable. It is not the original database or complete submission engine.
What the evidence shows
Offline regression tests exercise synthetic records. They demonstrate the published control logic, not that an external application was submitted or accepted.
What remains open
Receipt text matching is a heuristic. A stored digest identifies the exact text but does not authenticate its sender or establish its truth. Separate provenance and outcome confirmations remain mandatory.
The next research step
Connect these checks to independently verifiable external receipts and evaluate false rejections as carefully as false completion.
Inspect and reproduce
The linked package contains its source map, setup instructions and tests. Public examples are designed for local inspection. No production account, paid model call or private dataset is required for their documented offline checks.
Open the implementation