Alderbrook Immigration Law • Powered by Regisseur
From a firm's own website to a matter closed — four real cases, start to finish.
Start with the firm's own public site, follow an H-1B extension request from Fabrikam Robotics through document collection, government filing, a Request for Evidence, and approval, then a removal-defense matter where a hearing filing deadline is tracked, missed, detected, escalated, and resolved — then a general consultation that turns into a brand-new matter automatically, and a citizenship application where every eligibility number is computed, not guessed.
58
Screens captured from real runs
40
Automated pipeline steps
12
Client / employer-visible steps
4
Real matters, start to finish
Priya Raman
Managing Attorney at Alderbrook Immigration Law. Reviews and approves every filing and hearing packet — by replying to a real email.
Managing AttorneyTomás Rivera
Senior Paralegal. Confirms drafts, monitors deadlines, chases evidence, and closes out completed steps.
Senior ParalegalAnika Sharma & Jordan Lee
H-1B beneficiary (Fabrikam Robotics) and her employer's HR contact — the applicants in Story A.
H-1B Beneficiary / HR Contact"Mateo H."
Removal-defense client. Named by first name and last initial only, by design, throughout this matter.
Removal-Defense ClientDevika Nair
Submits a general consultation request about citizenship — the applicant in Story C, whose accepted consultation opens her own citizenship matter automatically.
Consultation ClientAmara Osei
Applies for naturalization — the applicant in Story D, whose eligibility is computed from her own residency and travel history.
Naturalization ApplicantStory A — Anika's H-1B extension, one request, end to end
Jordan submits
Alderbrook's site, no login
→
Documents & deadline
Secure upload, I-94 deadline read
→
Forms fill themselves
Labor certification, petition, support letter
→
Priya approves
By replying to a real email
→
Filed & questioned
Filed, evidence request answered
→
Approved
Petition approved, client notified
Story B — Mateo's removal-defense matter, the deadline guardian
Matter opens
Hearing dates on file from day one
→
Evidence chased
Secure upload link, automatic follow-up
→
Deadline missed
Flagged overdue, escalated automatically
→
Resolved & packet built
Paralegal acts, hearing packet assembled
→
Priya approves
Hearing-prep packet, by email
→
Decision & appeal window
Recorded, 30-day window, matter closed
Story C — Devika's consultation, accepted, becomes a matter automatically
Devika submits
A general consultation request, no login
→
Classified & summarized
Practice area identified, situation summarized
→
Reviewed & accepted
Paralegal reviews, Priya accepts by email
→
Matter opens itself
A new citizenship matter, opened and started automatically
Story D — Amara's path to citizenship, computed and filed
Eligibility computed
Five-year rule, presence days, filing date
→
Documents uploaded
Green card, tax returns, travel history
→
Priya approves
The N-400 filing, by email
→
Filed & tracked
USCIS receipt received, interview date tracked
About this walkthrough
Every screen below is a real, unedited screenshot from live, automated runs of Regisseur, captured on July 11, 2026 — not a mock-up or a staged demonstration. Alderbrook Immigration Law, Fabrikam Robotics, Priya Raman, Tomás Rivera, Anika Sharma, Jordan Lee, "Mateo H.", Devika Nair, and Amara Osei are fictional; all data shown is illustrative.
The USCIS and Department of Labor responses you'll see — receipt numbers, certification numbers, case status, the Request for Evidence — come from demonstration stand-ins built for this walkthrough, not a real government filing system. In production, the same configuration surface connects to the real government systems Alderbrook already uses. This applies to the citizenship filing in "Citizenship, by the numbers" exactly as it does to the H-1B petition.
The attorney's approval really arrives by email, and the platform's reading, sender-verification, and confirmation exchange are the product's real code, running live — only the inbound reply's delivery transport is simulated in this environment rather than sent from a live mail client.
The generated I-129 is a labeled demonstration reproduction of the form's key sections — not the official USCIS form. A firm's own current I-129 template can be substituted directly. The same is true of the generated N-400 in "Citizenship, by the numbers."
Deadline detection in the "deadline guardian" chapter runs on an hourly check in production; for this capture, that same check was triggered on demand rather than waiting out the clock. The platform detects lateness against dates it's already tracking — it does not run a visible countdown.
Calendar booking of hearing dates is a real, supported capability, but no calendar was connected in this demonstration environment.
In "From consultation to matter," when the attorney accepts a consultation, the platform genuinely opens and starts a brand-new matter using its own case-management tools — the same tools an operator could configure for any other automatic hand-off. Nothing about that hand-off is staged for this walkthrough.
In "Citizenship, by the numbers," the interview date shown as tracked is set when the matter is activated, for the purposes of this walkthrough. In production that date arrives from the applicant's actual USCIS interview notice; the platform tracks it exactly the same way either way.
The platform tracks dates, chases evidence, assembles packets, and escalates lateness; attorneys decide everything.
Chapter 0
The firm
Alderbrook's own public site, before any matter exists — no login, just what a visitor sees.
The firm, before any client
Before any matter exists, before any login — Alderbrook's own public site: the firm's practice areas (Employment Immigration, Removal Defense, Citizenship), the two attorneys of record, and the two ways in: begin an employment petition, or request a consultation.
Alderbrook's second public front door — for anyone who isn't already sure which petition they need. A name, an email, a matter type, and a plain description of the situation is all it asks for.
Chapter 1
A petition arrives
Alderbrook's own public site — no login, no phone tag — a matter number and a status link in under a minute.
Under a minute — no phone call, no login
Fabrikam Robotics' HR contact lands on Alderbrook Immigration Law's public H-1B Extension Request page — no login, no attorney on the phone yet, just the firm's own site.
Jordan Lee, HR contact at Fabrikam Robotics, completes the full request on one page: the employer's details, beneficiary Anika Sharma's current status documents, and her degree evidence — everything the attorney will need to start the extension.
The request is submitted. Jordan receives a matter number and a link to check status at any time — Alderbrook's team has already been notified.
Chapter 2
The pipeline wakes up
Behind the scenes, the case opens automatically and a secure document request goes out — every step a discrete, auditable action.
Automatically, the moment the request lands
Seconds after Jordan submitted, the matter appears in Alderbrook's operations view — already active. No paralegal manually opened a file or routed the intake.
Petition Intake and the Beneficiary Document Request have already completed automatically — Alderbrook has already emailed Anika a secure link requesting her passport, I-94, current I-797, paystubs, and degree evidence.
Chapter 3
Chasing the documents
A secure upload link — no email attachments — and a deterministic read of the filing deadline the moment the documents are in.
A secure link, not an email attachment
Jordan follows the link from the confirmation screen to check where things stand — no login, no phone call to the firm.
Anika's document bundle, attached and ready to submit through the same secure, single-use link Alderbrook emailed her — no email attachment, no manual intake.
The Status & Deadline Verification agent computes the days remaining until Anika's I-94 expires and classifies the filing urgency — a deterministic calculation, with the LLM writing only the plain-language narrative on top of it.
Chapter 4
Forms that fill themselves
The labor certification, the paralegal's confirmation, and the petition itself — generated, reviewed, and filed as real documents on the case.
Generated the moment the case is ready
The LCA Preparation agent calls the Department of Labor's certification service (a demonstration stand-in in this environment) and receives back a certified LCA number for Anika's extension.
Alderbrook's Posting Notice agent has drafted the LCA worksite posting text and paused — this step requires a human paralegal to confirm it before the case can move on to filing the I-129.
LCA Preparation, the Posting Notice confirmation, and I-129 Petition Generation have all completed — the case now sits at the one gate a human must clear: Attorney Review.
The Case Record's Artifacts view lists the demo-reproduction I-129, stamped with the node that generated it (this step) and when. The same agent also drafted an employer support-letter narrative, stored as case data rather than a second document artifact.
The actual PDF Alderbrook's platform generated for Anika's extension — the same AcroForm-fill engine used everywhere else in the platform, reproducing the I-129's key parts. The footer plainly labels it a demo reproduction, not the official USCIS form.
Chapter 5
A human decides
The attorney gets a real email and replies APPROVE — the platform verifies the sender, asks for confirmation, and advances the case, with the whole exchange on the record.
One inbox, one reply, the whole exchange on record
Every message Alderbrook has sent on Anika's matter so far, on the record — and the Attorney Review task has just been assigned to Priya Raman, the managing attorney. Her real assignment email is on its way.
The petition is ready to file — but nothing goes to USCIS without the attorney's sign-off. Every upstream step is complete; this step is the single node waiting on a person.
Priya Raman, the attorney, approved the filing the same way she'd answer any other work email: she replied APPROVE, confirmed with YES, and the gate closed — attributable and auditable, no application login required.
Chapter 6
The government answers
The petition is filed, a request for additional evidence comes back, the evidence is re-chased and re-filed, and the petition is approved.
Filed, questioned, answered, approved
Alderbrook's Filing Package agent assembles the filing-readiness summary and submits the petition to USCIS (a demonstration stand-in in this environment) — the receipt number and filing date come back and are now on the matter's record.
The Case Status Check agent's Review tab, showing the case context it read before calling USCIS's case-status service (a demonstration stand-in in this environment) — the next screen shows where that check actually routed the case.
The RFE Determination condition node read the case status and routed automatically into the RFE branch — the deadline tracker, the evidence request, and the evidence-wait node are now live; the No-RFE fast path was never taken.
The paralegal's own "My Work" inbox shows the RFE Deadline node with a real computed due date — the platform tracks it; nothing about the response itself is decided automatically.
Fabrikam Robotics and Anika supply the additional evidence USCIS requested — through the identical portal-link pattern used for the original document request.
The RFE response narrative, assembled from the newly-uploaded evidence and approved by the attorney — the case now proceeds to the shared Approval & Notifications step.
Every node in Anika's matter: intake through document verification, LCA, posting notice, I-129 generation, attorney review, filing, the RFE branch, and approval — all complete. The No-RFE fast path (this step) never ran; it was pruned the moment USCIS returned an RFE.
The full communications trail for Anika's matter: the document request, the RFE evidence request, and now the petition-approved notification — every outbound message timestamped and attributed.
Chapter 7
The deadline guardian
A hearing filing deadline, tracked from the moment the matter opens — flagged the instant it's missed, escalated automatically, and resolved the moment the paralegal acts.
Detected, escalated, and resolved — not a countdown
The removal-defense matter's raw case record: the NTA number, the master-calendar and individual hearing dates, and the attorney (Priya Raman) and paralegal (Tomás Rivera) of record — every fact the deadline guardian will track.
Matter Intake and the master-calendar scheduling step have completed; the Evidence Collection & Chase agent has already sent Mateo a secure upload link, and the Filing Deadline node beyond it is the one that matters most in this chapter.
The client uploads his hearing evidence package through the same secure, single-use link pattern used across every Alderbrook matter.
The paralegal's own inbox flags the Filing Deadline node OVERDUE the instant its deadline passes — this is derived directly from the deadline set at case activation, no coordinator sweep required to see it here.
Alderbrook's operations dashboard: the SLA Breaches tile reflects the real the escalation record row the coordinator sweep just wrote for Mateo's Filing Deadline — a genuine breach detection, not a countdown timer.
Expanded on Mateo's matter page: the SLA Breach escalation the coordinator sweep wrote for the Filing Deadline node, with its severity, timestamp, and a direct link back to the case.
The moment Tomás completes the Filing Deadline node, the SLA breach resolves on the record — the same escalation feed, now showing "No open escalations — All caught up." for this matter.
The Hearing-Prep Packet agent assembles the document bundle and drafts a cover narrative summarizing the evidence — a factual summary only; no legal strategy or outcome prediction.
The same reply-to-approve loop as the H-1B matter: the attorney replies APPROVE, confirms YES, and the hearing-prep packet gate closes — on the record.
The attorney's factual decision entry, on this node's own history — the platform records who entered it, when, and the plain outcome text; it never characterizes or predicts the legal result. The 30-day BIA appeal window activated the instant this was recorded.
The full removal-defense journey: intake, evidence chase, the filing deadline (breached, detected, and resolved), the hearing-prep packet, the attorney's approval, the decision recorded, the 30-day BIA appeal window, and Matter Closed.
Chapter 8
From consultation to matter
A general consultation request, reviewed and accepted, opens a brand-new matter automatically — no one clicks "New Case."
One accepted consultation, one matter opened automatically
Devika describes her situation in her own words and picks "Citizenship / naturalization" as her matter type — the same public form anyone can reach from Alderbrook's homepage.
Devika gets a matter number and a status link immediately — no phone call, no waiting for a callback to even begin.
Seconds after Devika submitted, the Consultation Intake & Classification agent has already run and Tomás Rivera's paralegal review is the next step.
Tomás signs in as himself and sees the pending Paralegal Review task directly on the node — the same Complete Task panel every human node in this platform uses.
Priya Raman decides whether the firm takes on Devika's matter — the same accept/decline gate every prospective client passes through, completed the same reply-to-approve way as every other attorney gate in this package.
Priya replies APPROVE, confirms YES, and the gate closes — the same real reply-to-approve command loop, on the record.
Filtered to the matter's own attributes: the practice area, the accepted status, and — the proof this really happened — the matter-opened status and the new matter's own job id, written by the platform's Matter Spawn step, not typed in by a person.
A new case — "Devika Nair - Naturalization (N-400)" — already in Alderbrook's own case list. Nobody clicked "New Case": the consultation pipeline's Matter Spawn step opened it the instant Priya accepted.
One case created another, entirely through the platform's own tools — no human ever opened it by hand: Devika's own name, email, and situation carried straight into her new matter, so the Document Request step could actually reach her real address this time. Her eligibility determination honestly reads "insufficient data" — a consultation never collects immigration history, and the platform doesn't pretend otherwise.
The classification agent's own Review tab — its actual task record, not an empty placeholder: the practice area it read and the plain-language summary it wrote, now with genuine agent provenance behind it.
Chapter 9
Citizenship, by the numbers
A five-year eligibility rule, a physical-presence day count, and a filing date — computed, not guessed, then filed and tracked to the interview.
Computed eligibility, filed, and tracked to the interview
Seconds after the matter opened, the platform already read Amara's LPR date and travel history and computed her eligibility — the Document Request step has already gone out.
The five-year rule, the physical-presence day count, and the earliest-filing date — all computed by a deterministic calculation on this node, not an LLM's judgment call.
Filtered to the matter's own attributes: the eligibility category, the physical-presence day count, the continuous-residence flag, the earliest filing date, and the overall filing-eligibility flag — every one of them written by the transform chain, not typed in by a person.
The same secure, single-use portal-link pattern used across every Alderbrook matter — no email attachment, no manual intake.
Document Received and the N-400 Form Fill step have both completed — the case now sits at the one gate a human must clear before filing.
The Artifacts view lists the demo-reproduction N-400, stamped with the node that generated it and when.
The actual PDF the platform generated for Amara's naturalization filing — the same AcroForm-fill engine used everywhere else in the platform, reproducing the N-400's key parts. The footer plainly labels it a demo reproduction, not the official USCIS form (the same labeling discipline as the I-129).
Every message on Amara's matter so far, plus the just-fired real assignment email to Priya Raman for the Attorney Review Gate.
The same reply-to-approve loop, one more time: Priya replies APPROVE, confirms YES, and the filing gate closes.
The Filing agent submits the N-400 to USCIS (a demonstration stand-in in this environment) and the receipt number and filing date come back onto the matter's record.
The interview date sits in the paralegal's own "My Work" list with a genuine future due date — tracked, not overdue. The removal-defense chapter is the one that shows what a missed deadline looks like; this one shows what on-time tracking looks like.
