Assist passport renewal with owner-handled sensitive entry

Why use this

1. A person renewing a passport may want help navigating an unfamiliar online sequence while retaining control of identity information and official declarations. Assistance becomes risky if navigation is confused with permission to enter sensitive data or finalize an application.

2. A bounded session plan could identify the next nonsensitive navigation step and the points where the owner must take over. It should preserve uncertainty about eligibility, saved fields and submission state rather than imply a completed renewal.

Why an agent / simpler alternative

Useful judgment

Explain visible navigation choices and recognize sensitive-entry or declaration boundaries.

Simpler alternative

Follow the official site’s checklist directly when the owner can navigate comfortably.

Unsuitable when

The owner cannot handle sensitive information, attestations or required government agreements.

Proposed inputs

1. Name

   Renewal-session goal

   Owner

   Applicant

   Minimum scope

   Nonsensitive description of the help needed and official service destination

   Quality check

   Confirm the intended government service without collecting identifiers.

2. Name

   Redacted screen context

   Owner

   Applicant

   Minimum scope

   Visible page labels with personal fields omitted

   Quality check

   Check that no identifier, photo or authentication secret is included.

Access and setup — proposed or unknown

Proposed minimum

1. Public official instructions or redacted screen descriptions before any authenticated session.

Compatibility unknowns

1. Unknown: exact runtime, browser access, current renewal flow and applicant eligibility.

External actions requiring approval

1. Any session action beyond authorized navigation; owner handles sensitive entry, photo upload and final attestations.

Expected deliverable and review checks

Proposed artifact

Navigation notes and an explicit owner-handoff checklist.

Critical checks

1. Sensitive fields are never filled from inference or stored notes.

2. Progress language distinguishes navigation, saved state and verified submission.

Missing output evidence

No new form inspection or application-state verification occurs; source outcome limits remain referenced.

Failure signals and proposed responses

1. Signal

   The page requests an identity number or photograph.

   Why it matters

   Continuing would cross the owner-handled boundary.

   Proposed response

   Stop before entry or upload and return control to the owner.

2. Signal

   A screen implies acceptance of official declarations.

   Why it matters

   Navigation could create consequential legal assertions.

   Proposed response

   Have the owner read and complete that step directly.

Effort and cost — unknown

Setup work

1. Verify the official destination and assistance boundaries.

Ongoing review

1. Confirm owner handoffs and clearly report session state.

Unknowns

1. Unknown: current fees, eligibility, browser compatibility and processing outcome.

First check — proposed, unexecuted

Status

proposed_unexecuted

Synthetic fixture

An invented page sequence moves from general instructions to an identity field and an attestation screen.

Acceptance checks

1. Assistance stops before both sensitive entry and attestation.

2. No completed-renewal claim is generated.

Stop conditions

1. Real personal data, account access or a government submission is required.

Limits

1. Editorial navigation aid; no application completion, acceptance or issuance is established.