Poland Stay Residence Xopoko

---
name: poland-stay-residence-xopoko
title: Poland Stay and Residence
description: Stay and residence. Use for Polish visas, legal stay, temporary residence, or residence cards; not protection, citizenship, or appeals.
author: Xopoko
author_url: https://github.com/Xopoko/poland/tree/main/skills/poland-stay-residence
license: MIT
version: 0.1.0
execution_mode: open
jurisdiction: pl
practice: immigration
language: en
---

# Poland Stay and Residence

Use for third-country entry, legal-stay, visa, temporary-residence, residence-card, and
purpose-of-stay procedure routing. EU/EEA/Swiss free movement belongs to
`poland-eu-mobility`.

Collect only route-changing categories: citizenship group, inside or outside
Poland, current stated basis and end date if known, intended purpose,
voivodeship, target date, and whether a case or official letter already exists.
Do not request identifiers, credentials, scans, or a personal narrative.

Use current Office for Foreigners, MOS, Gov.pl, and competent voivodeship source
records. Keep possible routes separate when a fact is unknown. Build phases for
status continuity, competent authority, evidence categories, current channel,
official landing-page handoff, and user-owned follow-up. Verify deadlines, forms,
fees, and public channel descriptions at action time. Never conclude eligibility
or predict an outcome.

For requested MOS or appointment help, apply
`../../references/automation-playbook.md`. The applicant handles authentication,
signature, truth attestations, final payment authorization, biometrics, and
original-passport presentation. Explicit task scope permits minimum record and
document inspection plus necessary form filling. Draft creation, booking,
upload, download, payment initiation, or submission requires fresh action-time
confirmation and a visible receipt check.

For filing-channel questions, use `udsc-mos-electronic-residence`: from 27 April
2026 its public guidance makes MOS the general electronic route for temporary,
permanent, and long-term EU resident applications while preserving listed paper
exceptions. Classify the exact purpose-of-stay branch before applying that rule.
Keep applicant filing, any employer or university attachment, and the later
voivode-controlled fingerprints, signature specimen, and original-passport
stage separate. Obtain authority from the actor who owns each account or
attachment before assisting; the applicant cannot authorize actions in an
employer or university account on that actor's behalf.

For highly qualified employment, combine `mos-eu-blue-card` with the MOS channel
and `poland-work-authorization`. Separate applicant, employer, and voivode
responsibilities and live-verify the threshold, qualification pathway, contract
conditions, mobility or employer-change rules, evidence, fees, and deadlines.
Never freeze a salary amount or infer EU Blue Card eligibility from a role name.

Route protection to `poland-protection-referral`, permanent/long-term status or
citizenship to `poland-citizenship-long-term`, and an adverse decision or delay
to `poland-appeals-review`. Work permission belongs to
`poland-work-authorization`; foreign-document chains belong to
`poland-foreign-documents`. Read
`../../references/immigration-status-map.md`.