Report Unemployment

Report Unemployment

The weekly motion that turns the work search log into a filed MyUI+ payment request. The log is already kept in audit shape; this skill moves the week into the state system and captures the confirmation trail. The claimer agent runs this method in the background and bails to Forni at every gate; run it inline when Forni wants to drive together.

Where Truth Lives

• The log: ~/Eudaimonia/Craft/Vocation/FY27-work-search.md. Weekly sections in MyUI+ audit shape. The slate comes from here, and the confirmation number goes back here.
• The claim: ~/Eudaimonia/Constitution/Financial/FY27-unemployment.md. Claimant ID, effective date, benefit year end.
• The task: Todoist "💰 Request UI Payment in MyUI+", recurring every Monday at 17:00. Completing it after submission is the last step.
• The site: the MyUI+ claimant portal, sign in via ID.me. System hours 04:00 to 19:00 MT, nightly processing 22:00 to 03:00 MT.

The Slate

Claim weeks run Sunday through Saturday; the Monday task files for the week that ended two days earlier. Pull the matching week section from the log and keep only what was genuinely completed:

• Applications actually submitted report as job applications with outcome Applied.
• Supporting activities (listings reviews, job platform registrations and profiles) report with outcome No Decision.
• Excluded: postings that closed before anything went out, roles declined on fit, anything still in flight. If it would not survive an audit, it stays off.
• The cadence targets five activities (three applications plus two supporting, per the FY27 plan). Fewer than five is reported honestly, never padded.

Sweep forward before trusting the count. The claim week's own section is not the whole slate. An activity that was committed to in an earlier week and happened during the claim week is often recorded only in the earlier week's row, as "call booked for " or "interview scheduled", and never written into the week it actually landed in. Reading the claim week's section alone therefore undercounts. Before settling the count:

1. Scan the two preceding week sections for any row naming a future date, and keep the ones falling inside the claim week.
2. Confirm each against the calendar (gws calendar events list over the claim week) and the mailbox, which is where a call leaves its real trace. A post call email is the strongest evidence a booked call was actually held.
3. Anything confirmed is a genuine activity and goes in, and the log gets the missing row backfilled at the same time the confirmation number is appended. That backfill is the inline path's, exactly like the confirmation number append: a background run never writes the Eudy repo, and instead returns the confirmed rows in its report for the main session to record.

Codified 2026-08-25, when the week of 08-16 read as three applications and was actually four. A True Search intro call sat in the week of 08-09 as "Call booked 2026-08-18", the calendar showed it at 14:30 that Tuesday, and Forni's own "Great chatting, Nick" email an hour later proved it happened. Forni had to supply it from memory because neither the skill nor the agent thought to look one week back.

Browser Mechanics

The agent-browser bundled Chromium cannot pass the ID.me Cloudflare challenge, headed or not; the check spins forever on the automation fingerprint. Attach to Forni's real Brave instead:

1. Quit Brave gracefully (osascript -e 'quit app "Brave Browser"') and wait for the process to exit.
2. Relaunch with the port: open -a "Brave Browser" --args --remote-debugging-port=9222 --restore-last-session.
3. Verify the port with curl -s http://localhost:9222/json/version, then confirm Brave itself owns it with lsof -nP -i :9222 | grep LISTEN. Do not check the JSON's Browser field: Brave is Chromium and reports Chrome/<version> there, never its own name, so that test can only ever fail. A listener that is not Brave means a stale process holds the port, so stop rather than attach. Then agent-browser --session myui connect 9222.
4. Open MyUI+ in a new tab and pin it (tab new <url>, tab list, tab <id> --pin-tab). Unpinned, the session follows whatever tab Forni focuses.

If a fresh ID.me login or MFA is needed, hand the keyboard to Forni and wait. An existing session redirects the login URL straight into the claimant flow.

The Flow

Drive every control by DOM id, and read the section and error state rather than trusting a reported success. Snapshot ref clicks do fire on this site, but refs shift on every postback, so a stable id is the safer target. Ids and the entry path are in learned-rules.md.

1. Confirm the week. Start from My Claim Status and open the specific week row whose dates match the slate, not a generic start button. Only one week is ever certifiable, and the next week's row shows the date it opens.
2. Basic Questions are Forni's answers (work, earnings, offers, able, available). Inline, walk them with him; a background run bails to the main session the moment the section is not already Complete, per the agent contract. Forni may hand the whole section over ("I trust you to answer these"), and most of it genuinely is derivable from the record: offers, refusals, quits, discharges, layoffs, holidays, able, available, and work search all follow from the log and the week. Two never are, no matter how broad the authorization: whether he worked (self employment counts, so any Atelic work is work) and whether he received severance, retirement pay, 401(K), or pension. Only he knows those, a wrong answer is a false certification under penalty of perjury, and a blanket yes does not create knowledge. Ask those two, answer the rest, and say which is which.
3. Activity count: select the radio matching the slate size (Five or More at cadence).
4. One form per activity, saved individually. Field ids, dropdown mapping, and the ASPX gotchas live in learned-rules.md. Verify each save by the numbered activity list growing.
5. Work Search Plan checkboxes describe the coming week's intent: inquire online, apply online, interview online and by phone, other activities.
6. GATE: work search certification. Checkbox plus initials (MGF), then FINISH. Requires Forni's explicit yes in that moment.
7. Summary readback. Read every section back to Forni in full: Basic Questions answers, all activities, the plan.
8. GATE: penalty of perjury certification and Submit. Requires Forni's explicit yes in that moment. Two gates, two yeses; never batch them.
9. Capture and close. Record the confirmation number, submitted week, and timestamp. Inline, append a confirmation line to the week's section in the log; a background run reports the number and leaves the append to the main session. Complete the Todoist task and report the number.

Activity Type Mapping

Contact method is Online for the standard motion. Contact information takes the posting URL. Position title and platform go in Additional Information; the form has no position field.