# Dwellmark

Premium residency defense and documentation platform prototype for people who need to prove where they lived, worked, traveled, and maintained domicile ties.

## Public Prototype

- Prototype: /
- Prototype absolute URL: https://www.dwellmark.io/
- Design handoff brief: /design-handoff
- Design handoff brief absolute URL: https://www.dwellmark.io/design-handoff
- Prototype route map: /prototype
- Prototype route map absolute URL: https://www.dwellmark.io/prototype
- Markdown handoff brief: /api/design-handoff/markdown
- JSON handoff manifest: /api/design-handoff/demo
- Current Owner Command Center: https://www.dwellmark.io/

## Current Owner Command Center Review URLs

- Overview: https://www.dwellmark.io/ -- First-paint comprehension, readiness seal, KPI strip, readiness chain, advisor/packet next action.
- Day counts: https://www.dwellmark.io/?tab=daycounts -- Presence by month, recent day ledger, weak-day Add proof prompts, Minnesota watch rail.
- Evidence: https://www.dwellmark.io/?tab=evidence -- Evidence confidence summary, filters, quality column, detail drawer, add-evidence modal.
- Financial evidence filter: https://www.dwellmark.io/?tab=evidence&filter=financial -- Stable filtered evidence state for advisor and packet blocker review.
- Packet: https://www.dwellmark.io/?tab=packet -- Six-section manifest, financial ties blocker, packet readiness rail, auditor-receives list.
- Advisor: https://www.dwellmark.io/?tab=advisor -- Permissioned advisor review, access scope, response flow, sign-off status, city-level privacy copy.
- Archived packet state: https://www.dwellmark.io/?tab=packet&year=2025 -- Read-only filed-year banner and disabled assemble/edit actions.
- Weak evidence persona: https://www.dwellmark.io/?tab=daycounts&persona=weak_evidence -- Thin day proof, adaptive proof prompts, mobile capture action, and packet consequences.
- Advisor review persona: https://www.dwellmark.io/?tab=advisor&persona=advisor_review -- Advisor queue, issue response, access scope, city-level privacy, and sign-off readiness.
- Packet ready persona: https://www.dwellmark.io/?tab=packet&persona=packet_ready -- Completed packet sections, clean integrity state, approved advisor export, and premium ready-state language.
- Privacy review persona: https://www.dwellmark.io/?tab=advisor&persona=privacy_review -- Exact-location redaction, advisor export permission, retention language, and non-alarming owner controls.
- Florida domicile persona: https://www.dwellmark.io/?tab=packet&persona=florida_domicile -- Florida domicile ties, declarations, vehicle/licensing proof, and advisor-compatible packet sections.
- Act 60 persona: https://www.dwellmark.io/?persona=act60_user -- Act 60 as one supported module inside broader residency defense, not the default product identity.
- Former Act 60 persona: https://www.dwellmark.io/?persona=former_act60&year=2025 -- Archived former-resident state, read-only retention language, and post-move documentation context.
- Mobile privacy capture state: https://www.dwellmark.io/?tab=evidence&persona=privacy_review -- Mobile proof capture prompt, evidence confidence, exact-location boundary, and small-screen review entry.

## Review Boundaries

- No login wall. This manifest describes seeded prototype routes only.
- No real user data, secrets, private evidence files, exact coordinates, or service-role values are returned.
- Dwellmark provides records, workflows, and educational context; it does not provide tax or legal advice.

## Design Handoff URL Guide

- Public prototype (start): https://www.dwellmark.io/. Usage: Primary seeded product experience with no login wall. Reviewer action: Open this first when a design tool needs to crawl the full product surface from the live app shell. Examples: https://www.dwellmark.io/, https://www.dwellmark.io/?persona=weak_evidence#workspace
- Prototype handoff panel (start): https://www.dwellmark.io/#design-handoff. Usage: In-product orientation panel with persona buttons, route links, readiness, and review checklist state. Reviewer action: Use this when reviewing the product from the owner command-center context. Examples: https://www.dwellmark.io/#design-handoff, https://www.dwellmark.io/?persona=advisor_review#design-handoff
- Design handoff brief (brief): https://www.dwellmark.io/design-handoff. Usage: External UX review brief with guardrails, scorecard, acceptance kit, runbook, and return template. Reviewer action: Use this as the canonical starting brief for Stitch, Claude, or human UX review. Examples: https://www.dwellmark.io/design-handoff, https://www.dwellmark.io/design-handoff#scorecard, https://www.dwellmark.io/design-handoff#acceptance-kit
- Prototype route map (index): https://www.dwellmark.io/prototype. Usage: Crawlable index of every public screen alias, persona state, journey start, and seeded API. Reviewer action: Use this when a tool needs one page that exposes every public review entrypoint. Examples: https://www.dwellmark.io/prototype, https://www.dwellmark.io/prototype#screens, https://www.dwellmark.io/prototype#personas
- Screen alias pattern (pattern): https://www.dwellmark.io/prototype/[screen]. Usage: Route-style URL for a single prototype screen when hash anchors are less reliable for a design tool. Reviewer action: Replace `[screen]` with the screen id from the route map or JSON manifest. Examples: https://www.dwellmark.io/prototype/workspace, https://www.dwellmark.io/prototype/ledger-review-center, https://www.dwellmark.io/prototype/packet-builder
- Persona alias pattern (pattern): https://www.dwellmark.io/prototype/persona/[persona]. Usage: Route-style URL for opening a seeded persona state directly. Reviewer action: Replace `[persona]` with a persona id before starting a state-specific review. Examples: https://www.dwellmark.io/prototype/persona/weak_evidence, https://www.dwellmark.io/prototype/persona/advisor_review, https://www.dwellmark.io/prototype/persona/packet_builder
- Persona plus screen query (pattern): https://www.dwellmark.io/prototype/[screen]?persona=[persona]. Usage: Route-style URL for opening a specific screen under a specific seeded persona. Reviewer action: Use this format for route-level findings so engineering can reproduce the exact state. Examples: https://www.dwellmark.io/prototype/workspace?persona=weak_evidence, https://www.dwellmark.io/prototype/advisor-resolution-center?persona=advisor_review, https://www.dwellmark.io/prototype/mobile-capture-center?persona=privacy_review
- JSON handoff manifest (machine-readable): https://www.dwellmark.io/api/design-handoff/demo. Usage: Machine-readable handoff package with personas, routes, journeys, URL guide, acceptance kit, and boundaries. Reviewer action: Use this when a design or AI tool can ingest structured JSON. Examples: https://www.dwellmark.io/api/design-handoff/demo
- Markdown handoff brief (machine-readable): https://www.dwellmark.io/api/design-handoff/markdown. Usage: Text-focused handoff brief for tools that prefer Markdown over rendered pages or JSON. Reviewer action: Use this for copy review, design notes, and AI-assisted synthesis. Examples: https://www.dwellmark.io/api/design-handoff/markdown
- LLM review guide (machine-readable): https://www.dwellmark.io/llms.txt. Usage: Concise LLM-readable product context, boundaries, handoff artifacts, public APIs, and assumptions to avoid. Reviewer action: Use this as the context file for AI design review tools. Examples: https://www.dwellmark.io/llms.txt
- Discovery files (crawl-support): https://www.dwellmark.io/sitemap.xml. Usage: Sitemap and robots policy help external tools discover public handoff URLs while avoiding private API surfaces. Reviewer action: Use these files when a crawler or design tool needs URL discovery hints. Examples: https://www.dwellmark.io/sitemap.xml, https://www.dwellmark.io/robots.txt

## UX Handoff Coverage Matrix

- Full public product prototype (Phase 1, covered): Requirement: Expose the complete Dwellmark product experience without login walls for design tools and external reviewers. Coverage: The public app shell, design handoff brief, route map, screen aliases, persona aliases, sitemap, robots policy, Markdown brief, llms.txt, and JSON manifest are public seeded routes. Evidence: no auth redirect, public route aliases, crawlable discovery files. Reviewer action: Open `/design-handoff`, `/prototype`, and the JSON manifest from a clean browser session before visual review. Links: https://www.dwellmark.io/, https://www.dwellmark.io/design-handoff, https://www.dwellmark.io/prototype, https://www.dwellmark.io/api/design-handoff/demo
- Broad residency-defense positioning (Phase 1, covered): Requirement: Lead with residency defense, documentation, domicile ties, evidence quality, advisor review, and audit packets rather than only Act 60. Coverage: The prototype includes general domicile, Florida move, former-resident documentation, Act 60, multi-state exposure, business presence, advisor review, and audit packet workflows. Evidence: Act 60 is one module, multi-state scenarios, packet and evidence language. Reviewer action: Review copy in the route map, packet builder, track router, and Act 60 binder for balanced product positioning. Links: https://www.dwellmark.io/prototype/residency-track-router, https://www.dwellmark.io/prototype/domicile-workbench, https://www.dwellmark.io/prototype/act60-user?persona=act60_user, https://www.dwellmark.io/design-handoff#review-rubric
- Seeded data and privacy boundary (Phase 1, covered): Requirement: Use seeded demo data only and avoid exposing secrets, real evidence, exact coordinates, or private auth records. Coverage: Handoff guardrails, acceptance kit, smoke tests, and manifest boundaries all state seeded data only, no real evidence files, no exact coordinates, and no service-role values. Evidence: data boundary, secret smoke checks, privacy redaction center. Reviewer action: Preserve privacy and seeded-data boundaries during design changes; move real uploads and auth into a later production phase. Links: https://www.dwellmark.io/design-handoff#guardrails, https://www.dwellmark.io/design-handoff#acceptance-kit, https://www.dwellmark.io/prototype/privacy-redaction-center?persona=privacy_review, https://www.dwellmark.io/llms.txt
- Owner, advisor, evidence, and packet workflow depth (Phase 1, covered): Requirement: Show dashboard, day ledger, evidence vault, domicile binder, residency tracks, business ledger, mobile device QA, advisor queue, privacy controls, and audit packet builder as functional public prototype flows. Coverage: Stable screen aliases and journey scripts cover owner command center, ledger review, evidence requests, mobile capture with iOS device QA, domicile workbench, business presence, advisor resolution, claim review, packet command, and packet integrity flows. Evidence: journey scripts, screen inventory, packet index. Reviewer action: Walk the owner, advisor, packet, and privacy/business journeys and return route-level findings with persona and viewport context. Links: https://www.dwellmark.io/design-handoff#runbook, https://www.dwellmark.io/prototype#journeys, https://www.dwellmark.io/prototype/advisor-resolution-center?persona=advisor_review, https://www.dwellmark.io/prototype/packet-builder?persona=packet_builder
- Stable design-review URLs (Phase 2, covered): Requirement: Provide stable URLs for every major screen, state, persona, and handoff artifact so design tools can access them directly. Coverage: The URL guide, route map, screen aliases, persona aliases, persona plus screen query pattern, Markdown brief, llms.txt, and JSON manifest expose canonical relative and absolute URLs. Evidence: URL guide, absolute canonical URLs, route alias patterns. Reviewer action: Use the URL guide for every returned finding so engineering can reproduce the exact public state. Links: https://www.dwellmark.io/design-handoff#url-guide, https://www.dwellmark.io/prototype#url-guide, https://www.dwellmark.io/prototype/persona/advisor_review, https://www.dwellmark.io/prototype/workspace?persona=weak_evidence
- Mobile device QA handoff (Phase 2, covered): Requirement: Expose the seeded iOS device QA checklist, signoff status, and next action alongside mobile capture readiness for UX review. Coverage: The mobile capture center and demo mobile API surface the iOS device QA summary, checklist rows, physical-device signoff status, and remaining next action without real uploads or exact coordinates. Evidence: iOS device QA checklist, mobile demo API, mobile viewport matrix. Reviewer action: Review `/prototype/mobile-capture-center?persona=privacy_review` at mobile width and compare the visible checklist with `/api/mobile/demo/capture`. Links: https://www.dwellmark.io/prototype/mobile-capture-center?persona=privacy_review, https://www.dwellmark.io/api/mobile/demo/capture, https://www.dwellmark.io/design-handoff#viewport-matrix
- Persona and scenario coverage (Phase 2, covered): Requirement: Expose clean user, weak evidence, advisor review, packet ready, business exposure, Act 60, former Act 60, Florida domicile, privacy, and packet-builder states. Coverage: The persona catalog and route aliases expose 10 seeded states with deep links, absolute URLs, and route-map cards for direct design review. Evidence: persona aliases, persona route map, state-specific journeys. Reviewer action: Start with weak evidence, advisor review, privacy review, and packet-builder personas before visual polish. Links: https://www.dwellmark.io/prototype#personas, https://www.dwellmark.io/prototype/persona/weak_evidence, https://www.dwellmark.io/prototype/persona/advisor_review, https://www.dwellmark.io/prototype/persona/packet_builder
- Review return loop (Phase 2, covered): Requirement: Give reviewers a clear way to inspect, redesign, and return actionable findings without guessing what engineering needs. Coverage: The runbook, prompt pack, feedback worksheet, response template, packet index, and acceptance kit define review order, expected outputs, return fields, severity, and preserved boundaries. Evidence: runbook, response template, feedback worksheet. Reviewer action: Return findings using route, persona, viewport, severity, recommendation, and boundary impact fields. Links: https://www.dwellmark.io/design-handoff#runbook, https://www.dwellmark.io/design-handoff#feedback-worksheet, https://www.dwellmark.io/design-handoff#response-template, https://www.dwellmark.io/design-handoff#packet-index
- Deferred production integration (Phase 3, deferred): Requirement: Keep auth, real uploads, private storage, billing, advisor invites, and production role gates out of the public UX handoff until design is approved. Coverage: The decision register, readiness scorecard, acceptance kit, guardrails, and llms.txt all preserve public prototype mode and explicitly defer auth/real-data work. Evidence: deferred auth decision, production integration score, no private data in smoke checks. Reviewer action: Do not add signup, login, billing, private uploads, exact-location display, or role-based gates during UX refinement. Links: https://www.dwellmark.io/design-handoff#decision-register, https://www.dwellmark.io/design-handoff#scorecard, https://www.dwellmark.io/design-handoff#guardrails, https://www.dwellmark.io/llms.txt

## UX Handoff QA Matrix

- Public route automation (automated, covered): Check: Production smoke loads the public handoff brief, route map, discovery files, Markdown brief, llms.txt, route aliases, and seeded demo APIs without auth. Proof: apps/web/scripts/smoke-web.mjs fetches the built Next app and asserts public handoff content, canonical URLs, forbidden secret strings, and seeded API responses. Reviewer action: Treat this as automated route-access evidence, then use the visual QA rows for hierarchy, density, and interaction notes. Links: https://www.dwellmark.io/design-handoff, https://www.dwellmark.io/prototype, https://www.dwellmark.io/llms.txt, https://www.dwellmark.io/api/design-handoff/demo
- Workflow contract automation (automated, covered): Check: Static workflow verification confirms that each public handoff artifact remains wired into source, render surfaces, and smoke checks. Proof: apps/web/scripts/verify-workflows.mjs checks manifest fields, page sections, Markdown and llms.txt sections, smoke assertions, and stable route patterns. Reviewer action: Use this as drift protection when requesting changes to handoff structure, route aliases, or review artifacts. Links: https://www.dwellmark.io/api/design-handoff/demo, https://www.dwellmark.io/api/design-handoff/markdown, https://www.dwellmark.io/design-handoff#coverage-matrix
- Roadmap contract automation (automated, covered): Check: Feature and product-scope verifiers require each named UX handoff artifact to have source, route, smoke, and documentation evidence. Proof: scripts/verify-feature-map.mjs and scripts/verify-product-scope.mjs now include the response template, scorecard, acceptance kit, URL guide, coverage matrix, and QA matrix. Reviewer action: Use this as proof that the handoff package maps back to the roadmap, not only the current UI. Links: https://www.dwellmark.io/design-handoff#coverage-matrix, https://www.dwellmark.io/prototype#coverage-matrix, https://www.dwellmark.io/api/design-handoff/markdown
- Viewport visual review (manual, needs-design-review): Check: Designer or reviewer should inspect desktop, tablet, and mobile route starts for layout density, overflow, hierarchy, scanability, and device-QA comprehension. Proof: The viewport matrix lists desktop owner command center, tablet advisor review, mobile capture/privacy with iOS device QA, and packet-builder review states with stable URLs. Reviewer action: Return route, persona, viewport, issue, recommendation, and severity for every visual finding. Links: https://www.dwellmark.io/design-handoff#viewport-matrix, https://www.dwellmark.io/prototype#viewports, https://www.dwellmark.io/prototype/mobile-capture-center?persona=privacy_review
- Mobile device QA review (manual, needs-design-review): Check: Designer or reviewer should verify that the iOS device QA checklist, signoff state, blocker count, and next action are understandable on mobile. Proof: The mobile capture center renders Device QA, iOS device signoff checklist, and iOS device QA next action from seeded readiness data. Reviewer action: Return small-screen findings for checklist hierarchy, signoff language, blocked-state copy, and whether physical-device QA feels distinct from production uploads. Links: https://www.dwellmark.io/prototype/mobile-capture-center?persona=privacy_review, https://www.dwellmark.io/api/mobile/demo/capture, https://www.dwellmark.io/design-handoff#feedback-worksheet
- Component system review (manual, needs-design-review): Check: Designer should refine cards, status pills, metric blocks, ledgers, route links, privacy controls, and dense review tables consistently. Proof: The component inventory and review rubric identify reusable UI primitives and what product boundaries must be preserved. Reviewer action: Return reusable component recommendations with responsive behavior and states. Links: https://www.dwellmark.io/design-handoff#components, https://www.dwellmark.io/design-handoff#review-rubric, https://www.dwellmark.io/prototype#screens
- Auth and production deferral QA (guardrail, deferred): Check: Auth, real uploads, private storage, billing, advisor invites, and role gates remain intentionally outside the public UX handoff. Proof: The decision register, scorecard, coverage matrix, acceptance kit, and smoke secret checks all preserve seeded public mode. Reviewer action: Flag any design recommendation that requires signup, private data, exact location, or production persistence before UX approval. Links: https://www.dwellmark.io/design-handoff#decision-register, https://www.dwellmark.io/design-handoff#scorecard, https://www.dwellmark.io/design-handoff#acceptance-kit, https://www.dwellmark.io/llms.txt

## Design Review Scenario Matrix

- Owner command center scenario: Persona: weak_evidence. Start: https://www.dwellmark.io/prototype/workspace?persona=weak_evidence. Mission: Decide whether a first-time owner can understand their residency risk, weak days, evidence confidence, and packet readiness in one scan. Success: Residency defense category is clear, Packet readiness is prominent, Weak-day next actions feel specific. Failure: Metrics feel decorative, Act 60 feels like the default product identity, Evidence gaps do not connect to packet impact. Expected findings: first-screen hierarchy, copy changes, route sequencing, component density
- Advisor issue loop scenario: Persona: advisor_review. Start: https://www.dwellmark.io/prototype/advisor-resolution-center?persona=advisor_review. Mission: Walk the advisor from open issue to comment, evidence request, claim decision, and packet blocker review. Success: Open issues are scannable, Advisor requests stay tied to proof gaps, Packet blockers remain attached to claims. Failure: Advisor actions are buried, Comments feel detached from evidence, Export readiness is unclear. Expected findings: workflow order, missing context, advisor action label, packet blocker hierarchy
- Mobile privacy scenario: Persona: privacy_review. Start: https://www.dwellmark.io/prototype/mobile-capture-center?persona=privacy_review. Mission: Review mobile capture, iOS device QA signoff, evidence-source consent, exact-location redaction, advisor permission, and retention language on a small screen. Success: No horizontal scrolling, Device QA next action is clear, Privacy controls are explicit, Consent and redaction language feels calm. Failure: Device QA looks like production upload work, Controls look like production uploads, Exact-location risk feels hidden, Retention or deletion states are ambiguous. Expected findings: mobile layout, device QA hierarchy, privacy wording, control grouping, trust-building copy
- Packet export scenario: Persona: packet_builder. Start: https://www.dwellmark.io/prototype/packet-builder?persona=packet_builder. Mission: Judge whether the audit packet feels like the hero workflow across manifest sections, blockers, privacy choices, integrity, and export history. Success: Packet object dominates the workflow, Blockers and readiness appear together, Integrity language is understandable. Failure: Artifact links feel secondary, Blockers are separated from proof context, Export state sounds like a guarantee. Expected findings: packet hierarchy, blocker language, artifact grouping, integrity copy
- Residency track breadth scenario: Persona: former_act60. Start: https://www.dwellmark.io/prototype/residency-track-router?persona=former_act60. Mission: Confirm the product reads as broad residency defense across domicile, Florida, former-resident, Act 60, multi-state, and business exposure tracks. Success: Act 60 is one module, Former-resident and Florida paths feel first-class, Business exposure is separated from personal domicile proof. Failure: Puerto Rico language dominates, Track routing feels like taxonomy instead of guidance, Multi-state exposure lacks consequence. Expected findings: track naming, module hierarchy, missing scenario, positioning language
- Component system scenario: Persona: packet_builder. Start: https://www.dwellmark.io/design-handoff#components. Mission: Normalize repeated cards, status pills, ledgers, route links, privacy controls, and packet artifacts into reusable design-system guidance. Success: Status semantics are consistent, Dense cards compare cleanly, Route links and actions are visually distinct. Failure: Status colors conflict, Cards rely on copy weight alone, Links, pills, and actions compete for attention. Expected findings: component state, responsive behavior, spacing rule, reuse recommendation

## Handoff Readiness Report

- Public review access (ready): The prototype, handoff brief, route map, screen aliases, and persona aliases are public seeded routes with no auth redirect. Review links: https://www.dwellmark.io/, https://www.dwellmark.io/design-handoff, https://www.dwellmark.io/prototype, https://www.dwellmark.io/prototype/packet-builder, https://www.dwellmark.io/prototype/persona/advisor_review
- Machine-readable package (ready): JSON, Markdown, sitemap, robots, and llms.txt handoff surfaces expose the same canonical URLs and review boundaries. Review links: https://www.dwellmark.io/api/design-handoff/demo, https://www.dwellmark.io/api/design-handoff/markdown, https://www.dwellmark.io/sitemap.xml, https://www.dwellmark.io/robots.txt, https://www.dwellmark.io/llms.txt
- Persona and screen coverage (ready): Design review covers seeded owner, advisor, packet, business, privacy, Act 60, former Act 60, and Florida domicile states across the full screen inventory. Review links: https://www.dwellmark.io/prototype/persona/weak_evidence, https://www.dwellmark.io/prototype/persona/advisor_review, https://www.dwellmark.io/prototype/persona/privacy_review, https://www.dwellmark.io/prototype/persona/packet_builder
- Workflow review depth (ready): Owner, advisor, packet export, and business/privacy journeys each have start states, expected outcomes, and route-style review URLs. Review links: https://www.dwellmark.io/prototype/residency-intake-center?persona=weak_evidence, https://www.dwellmark.io/prototype/advisor-resolution-center?persona=advisor_review, https://www.dwellmark.io/prototype/packet-builder?persona=packet_builder, https://www.dwellmark.io/prototype/business-presence-center?persona=business_exposure
- Viewport and feedback loop (ready): Desktop, tablet, and mobile viewport passes, prompt pack entries, and structured worksheet questions are all available from public routes. Review links: https://www.dwellmark.io/prototype/workspace?persona=weak_evidence, https://www.dwellmark.io/prototype/advisor-resolution-center?persona=advisor_review, https://www.dwellmark.io/prototype/mobile-capture-center?persona=privacy_review, https://www.dwellmark.io/prototype/packet-builder?persona=packet_builder
- Product boundary safety (ready): The handoff package preserves seeded data, no secrets, no private evidence, no exact coordinates, Act 60 as one module, and no tax/legal advice. Review links: https://www.dwellmark.io/design-handoff#guardrails, https://www.dwellmark.io/design-handoff#acceptance, https://www.dwellmark.io/design-handoff#review-rubric, https://www.dwellmark.io/llms.txt

## Handoff Packet Index

- Orientation package: Understand the category, boundaries, public routes, personas, and expected review outputs before changing screens. Deliverable: A brief notes page confirming the product promise, no-auth review mode, sensitive-data boundaries, and open questions. Links: https://www.dwellmark.io/design-handoff, https://www.dwellmark.io/api/design-handoff/markdown, https://www.dwellmark.io/llms.txt, https://www.dwellmark.io/api/design-handoff/demo
- First-pass product review: Improve category clarity, owner comprehension, dashboard hierarchy, day-count confidence, and packet-readiness scanning. Deliverable: Annotated desktop and mobile recommendations for the first owner pass, with copy that preserves the legal and privacy boundaries. Links: https://www.dwellmark.io/prototype/workspace?persona=weak_evidence, https://www.dwellmark.io/prototype/residency-intake-center?persona=weak_evidence, https://www.dwellmark.io/prototype/ledger-review-center?persona=weak_evidence
- Advisor and packet review: Refine advisor issue review, claim decisions, evidence requests, packet blockers, and export-readiness language. Deliverable: Advisor-review flow notes, packet hierarchy recommendations, and unresolved workflow questions before auth is introduced. Links: https://www.dwellmark.io/prototype/advisor-resolution-center?persona=advisor_review, https://www.dwellmark.io/prototype/claim-review-board?persona=advisor_review, https://www.dwellmark.io/prototype/packet-builder?persona=packet_builder
- Mobile privacy review: Check capture readiness, iOS device QA signoff, exact-location redaction, evidence-source consent, advisor export permission, and small-screen density. Deliverable: Mobile layout notes, device-QA signoff recommendations, and privacy wording that avoid real upload, signup, or exact-coordinate assumptions. Links: https://www.dwellmark.io/prototype/mobile-capture-center?persona=privacy_review, https://www.dwellmark.io/prototype/evidence-source-workbench?persona=privacy_review, https://www.dwellmark.io/prototype/privacy-redaction-center?persona=privacy_review, https://www.dwellmark.io/api/mobile/demo/capture
- Component system review: Normalize dense operational cards, status pills, ledgers, route links, privacy controls, and packet artifact states. Deliverable: Component notes covering hierarchy, spacing, responsive behavior, status semantics, and reusable patterns for later implementation. Links: https://www.dwellmark.io/design-handoff#components, https://www.dwellmark.io/design-handoff#review-rubric, https://www.dwellmark.io/prototype#screens
- Return package: Return findings in a format that engineering can apply after the design pass without losing product boundaries. Deliverable: A prioritized list of UX findings, revised route/screen references, viewport notes, copy changes, and preserved-boundary notes. Links: https://www.dwellmark.io/design-handoff#feedback-worksheet, https://www.dwellmark.io/design-handoff#viewport-matrix, https://www.dwellmark.io/design-handoff#prompt-pack

## Design Decision Register

- Product category (locked): Dwellmark is a residency defense and documentation platform, not an Act 60-only product. Design implication: Lead with residency defense and packet readiness; keep Act 60 as one supported module inside the track system. Links: https://www.dwellmark.io/prototype/workspace?persona=weak_evidence, https://www.dwellmark.io/prototype/residency-track-router?persona=weak_evidence, https://www.dwellmark.io/prototype/binders?persona=act60_user
- Public prototype mode (locked): The complete product prototype remains public and no-auth until UX refinement is approved. Design implication: Do not add signup walls, private redirects, billing gates, or real upload requirements to the review experience. Links: https://www.dwellmark.io/, https://www.dwellmark.io/design-handoff, https://www.dwellmark.io/prototype, https://www.dwellmark.io/prototype/persona/advisor_review
- Sensitive data boundary (locked): Design review uses seeded data only and must not expose real evidence, secrets, exact coordinates, or service-role values. Design implication: Keep privacy language explicit and calm; preserve owner-controlled redaction and permissioned advisor access. Links: https://www.dwellmark.io/prototype/privacy-redaction-center?persona=privacy_review, https://www.dwellmark.io/prototype/evidence-source-workbench?persona=privacy_review, https://www.dwellmark.io/design-handoff#guardrails
- Dashboard hierarchy (open): The first screen still needs design judgment on hierarchy, density, and where packet readiness should dominate. Design implication: Return recommendations for first-viewport hierarchy, metric grouping, weak-day prompts, and packet-readiness emphasis. Links: https://www.dwellmark.io/prototype/workspace?persona=weak_evidence, https://www.dwellmark.io/prototype/ledger-review-center?persona=weak_evidence, https://www.dwellmark.io/design-handoff#feedback-worksheet
- Advisor and packet flow (open): The advisor issue queue, claim review, and packet builder need UX review before role-based auth is wired. Design implication: Return flow notes for comments, evidence requests, packet blockers, claim decisions, and export-ready states. Links: https://www.dwellmark.io/prototype/advisor-resolution-center?persona=advisor_review, https://www.dwellmark.io/prototype/claim-review-board?persona=advisor_review, https://www.dwellmark.io/prototype/packet-builder?persona=packet_builder
- Auth and real data (deferred): Login, real evidence uploads, storage persistence, billing, and role-based production flows come after UX approval. Design implication: Do not design around account creation as the first screen; preserve public demo/design mode as a separate surface. Links: https://www.dwellmark.io/design-handoff#acceptance, https://www.dwellmark.io/design-handoff#review-rubric, https://www.dwellmark.io/llms.txt

## Design Handoff Runbook

- 1. Intake orientation: Confirm the product category, public prototype mode, sensitive-data boundary, and review package before redesign work starts. Output: Notes on product comprehension, missing context, and any boundary questions that must be resolved before visual exploration. Start: https://www.dwellmark.io/design-handoff
- 2. Owner command center pass: Review first-screen clarity, day counts, weak evidence prompts, proof strategy, and packet-readiness hierarchy. Output: Desktop and mobile recommendations for owner comprehension, hierarchy, copy, and route sequencing. Start: https://www.dwellmark.io/prototype/workspace?persona=weak_evidence
- 3. Advisor and packet pass: Review advisor comments, evidence requests, claim decisions, packet blockers, and export-ready language. Output: Advisor workflow notes and packet-builder recommendations that preserve the no-advice boundary. Start: https://www.dwellmark.io/prototype/advisor-resolution-center?persona=advisor_review
- 4. Mobile and privacy pass: Review mobile capture, iOS device QA signoff, evidence-source consent, exact-location redaction, advisor export permission, and retention language. Output: Mobile layout notes, device-QA signoff recommendations, privacy copy recommendations, and any small-screen component fixes. Start: https://www.dwellmark.io/prototype/mobile-capture-center?persona=privacy_review
- 5. Component system pass: Normalize cards, ledgers, status pills, route links, privacy controls, packet artifacts, and dense operational patterns. Output: Component inventory notes with reusable patterns, state semantics, and responsive behavior recommendations. Start: https://www.dwellmark.io/design-handoff#components
- 6. Return design package: Return design findings in a format engineering can act on after UX approval. Output: Prioritized findings with route references, viewport notes, copy changes, preserved boundaries, and deferred-auth notes. Start: https://www.dwellmark.io/design-handoff#feedback-worksheet

## Design Review Response Template

- Executive summary (required): Summarize whether the public prototype is ready for visual refinement, what changed in the recommended UX direction, and what still blocks handoff. Include: overall readiness, top three UX opportunities, risks or blockers, recommended next pass
- Route-level findings (required): Return findings tied to stable public routes, persona states, and viewport context so engineering can apply changes without guessing. Include: route URL, persona state, viewport, issue, recommendation, severity
- Copy and positioning changes (required): Identify language that should change or stay fixed, especially around residency defense, Act 60 as one module, privacy, advisor review, and tax/legal boundaries. Include: current copy, recommended copy, reason, boundary preserved
- Component system notes (recommended): Document reusable patterns for cards, ledgers, status pills, privacy controls, route links, packet artifacts, and dense operational panels. Include: component, state, recommended pattern, responsive behavior, reuse notes
- Viewport QA notes (required): Report desktop, tablet, and mobile review results against the viewport matrix and call out any layout, density, or readability problems. Include: viewport, route, what works, what breaks, recommended adjustment
- Preserved boundaries (required): Confirm the redesign preserves public prototype access, seeded data only, no exact coordinates, no tax/legal advice, and deferred auth or real-data work. Include: boundary, status, supporting route, risk if changed
- Deferred production work (recommended): List ideas that belong after UX approval, such as auth, real uploads, private storage, billing, advisor invites, or role-based permissions. Include: deferred item, reason deferred, dependency, suggested phase

## UX Handoff Readiness Scorecard

- Public access (ready, 100): The prototype, handoff brief, route map, aliases, Markdown, llms.txt, sitemap, and public demo APIs are reachable without auth. Next action: Use public routes for Stitch, Claude, and human review. Links: https://www.dwellmark.io/, https://www.dwellmark.io/design-handoff, https://www.dwellmark.io/prototype, https://www.dwellmark.io/llms.txt
- Review coverage (ready, 100): Personas, route aliases, journeys, viewport matrix, prompt pack, packet index, decision register, runbook, and response template cover the UX pass. Next action: Run the handoff runbook and return findings in the response template. Links: https://www.dwellmark.io/design-handoff#runbook, https://www.dwellmark.io/design-handoff#response-template, https://www.dwellmark.io/prototype#personas
- Product boundaries (ready, 100): The handoff package preserves residency-defense positioning, seeded data, no exact coordinates, Act 60 as one module, and no tax/legal advice. Next action: Preserve locked decisions while changing hierarchy, layout, copy, and interaction patterns. Links: https://www.dwellmark.io/design-handoff#decision-register, https://www.dwellmark.io/design-handoff#review-rubric, https://www.dwellmark.io/design-handoff#acceptance
- Designer actionability (ready, 95): The package gives designers concrete routes, personas, expected outputs, done criteria, and return fields. Next action: Start with owner command center, advisor/packet flow, mobile privacy, and component system passes. Links: https://www.dwellmark.io/design-handoff#packet-index, https://www.dwellmark.io/design-handoff#runbook, https://www.dwellmark.io/design-handoff#response-template
- Visual polish (review, 70): The product workflows are complete enough for design review, but visual hierarchy, density, typography, and responsive polish should be refined by the design pass. Next action: Return route-level visual and interaction recommendations before auth integration. Links: https://www.dwellmark.io/design-handoff#viewport-matrix, https://www.dwellmark.io/design-handoff#components, https://www.dwellmark.io/prototype/workspace?persona=weak_evidence
- Production integration (deferred, 40): Auth, real uploads, private storage, billing, advisor invites, and production role gates remain intentionally deferred until UX approval. Next action: Keep production integrations out of the design-tool handoff and preserve demo mode separately. Links: https://www.dwellmark.io/design-handoff#decision-register, https://www.dwellmark.io/llms.txt, https://www.dwellmark.io/api/design-handoff/demo

## Handoff Acceptance Kit

- Public route preflight (ready): Owner confirmation: All handoff routes can be opened from a clean browser session without login, private cookies, or real user data. Reviewer action: Open the visible brief, route map, Markdown brief, llms.txt guide, and JSON manifest before starting visual review. Proof: Public prototype mode, Stable route aliases, Crawlable discovery files. Links: https://www.dwellmark.io/design-handoff, https://www.dwellmark.io/prototype, https://www.dwellmark.io/api/design-handoff/markdown, https://www.dwellmark.io/llms.txt, https://www.dwellmark.io/api/design-handoff/demo
- Persona and state preflight (ready): Owner confirmation: The handoff includes clean, weak-evidence, advisor-review, packet-ready, business, Act 60, former Act 60, Florida, privacy, and packet-builder states. Reviewer action: Use the persona aliases and route map before requesting any new seeded states. Proof: 10 demo personas, Direct persona URLs, Route-style aliases for design tools. Links: https://www.dwellmark.io/prototype#personas, https://www.dwellmark.io/prototype/persona/weak_evidence, https://www.dwellmark.io/prototype/persona/advisor_review, https://www.dwellmark.io/prototype/persona/packet_builder
- Workflow depth preflight (ready): Owner confirmation: Owner, advisor, evidence, privacy, business, mobile capture, iOS device QA, annual review, and packet export flows have stable review routes. Reviewer action: Walk the runbook and return route-level findings using the response template. Proof: Runbook steps, Packet index, Journey scripts. Links: https://www.dwellmark.io/design-handoff#runbook, https://www.dwellmark.io/design-handoff#packet-index, https://www.dwellmark.io/design-handoff#response-template
- Boundary preflight (ready): Owner confirmation: The prototype stays in seeded-data mode, avoids tax/legal advice, avoids exact coordinates, and keeps Act 60 as one supported track. Reviewer action: Preserve locked boundaries while redesigning hierarchy, density, copy, and responsive behavior. Proof: Decision register, Review rubric, Acceptance checks. Links: https://www.dwellmark.io/design-handoff#decision-register, https://www.dwellmark.io/design-handoff#review-rubric, https://www.dwellmark.io/design-handoff#acceptance
- Return package preflight (review): Owner confirmation: The engineering team can apply findings when they include route, persona, viewport, severity, recommendation, and boundary impact. Reviewer action: Return the executive summary, route-level findings, copy notes, viewport QA, preserved boundaries, and deferred production items. Proof: Feedback worksheet, Response template, Viewport matrix. Links: https://www.dwellmark.io/design-handoff#feedback-worksheet, https://www.dwellmark.io/design-handoff#response-template, https://www.dwellmark.io/design-handoff#viewport-matrix

## Copy And Tone Matrix

- Category positioning copy: Surface: Owner command center and route map. Guidance: Lead with residency defense, day tracking, documentation, domicile ties, advisor review, and audit packets. Preserve: residency defense, documentation platform, audit packet readiness. Avoid: Act 60-only product language, tax savings language, guaranteed residency outcomes. Example: Dwellmark builds the residency defense file your CPA wishes you had kept all year. Links: https://www.dwellmark.io/prototype/workspace?persona=weak_evidence, https://www.dwellmark.io/design-handoff#review-rubric
- Packet hero copy: Surface: Packet builder, command center, and integrity lab. Guidance: Make the audit packet feel like the central product object while keeping export readiness factual. Preserve: packet readiness, blockers, manifest sections, integrity checks. Avoid: approved by authorities, audit-proof, guaranteed acceptance. Example: Export-ready means the seeded packet has resolved blockers, citations, integrity checks, and advisor-compatible sections. Links: https://www.dwellmark.io/prototype/packet-builder?persona=packet_builder, https://www.dwellmark.io/prototype/packet-integrity-lab?persona=packet_builder
- Evidence quality copy: Surface: Ledger, proof matrix, request center, and evidence vault. Guidance: Connect weak days and proof gaps to concrete next evidence requests without sounding punitive. Preserve: evidence confidence, weak-day prompts, source readiness, packet impact. Avoid: blame language, surveillance tone, black-box scoring. Example: This day needs stronger proof before it should support a packet claim. Links: https://www.dwellmark.io/prototype/ledger-review-center?persona=weak_evidence, https://www.dwellmark.io/prototype/evidence-source-workbench?persona=privacy_review
- Privacy control copy: Surface: Mobile capture, iOS device QA, evidence sources, privacy redaction, and advisor export. Guidance: Keep privacy and device-QA language calm, explicit, and owner-controlled while avoiding exact-location exposure. Preserve: owner-controlled redaction, advisor export permission, retention review, seeded data only. Avoid: hidden tracking, exact coordinates, automatic advisor sharing. Example: Exact location stays hidden by default; advisors see only the packet detail you explicitly approve. Links: https://www.dwellmark.io/prototype/mobile-capture-center?persona=privacy_review, https://www.dwellmark.io/prototype/privacy-redaction-center?persona=privacy_review
- Advisor review copy: Surface: Advisor workbench, issue queue, claim board, and defense brief. Guidance: Make advisor actions clear while preserving the boundary that Dwellmark provides records and workflows, not legal advice. Preserve: advisor-compatible review, evidence request, claim decision, review status. Avoid: legal conclusion, tax opinion, advisor access without permission. Example: Advisor review can request stronger evidence, comment on claims, and mark packet issues ready for owner review. Links: https://www.dwellmark.io/prototype/advisor-resolution-center?persona=advisor_review, https://www.dwellmark.io/prototype/claim-review-board?persona=advisor_review
- Act 60 balance copy: Surface: Residency tracks, binders, and Act 60 modules. Guidance: Treat Act 60 as one supported residency module inside a broader domicile and day-count defense platform. Preserve: one supported track, Puerto Rico requirements, broader domicile context. Avoid: Act 60 as product identity, tax-avoidance framing, specialized module hiding other tracks. Example: Act 60 is one residency track; Dwellmark also supports Florida domicile, former-resident files, and multi-state exposure. Links: https://www.dwellmark.io/prototype/residency-track-router?persona=former_act60, https://www.dwellmark.io/prototype/binders?persona=act60_user

## Design Review Intake Board

- First-viewport hierarchy (critical): Owner question: What should dominate the first screen: residency status, weak-day risk, packet readiness, or the next evidence action? Design task: Return a proposed desktop and mobile hierarchy for the owner command center that preserves packet readiness as a primary product object. Decision needed: Final first-screen information architecture before auth and real-data flows are wired. Expected return: Annotated layout or written hierarchy with primary, secondary, and tertiary sections. Routes: https://www.dwellmark.io/prototype/workspace?persona=weak_evidence, https://www.dwellmark.io/prototype/ledger-review-center?persona=weak_evidence
- Packet hero layout (critical): Owner question: How should packet sections, blockers, integrity, privacy choices, and export history sit together without feeling busy? Design task: Redesign the packet path so blockers, manifest sections, integrity checks, and export readiness are visible in one coherent workflow. Decision needed: Packet-builder structure before production export, signed files, and advisor signoff are made real. Expected return: Packet workflow recommendation with blocker placement, artifact hierarchy, and export-state language. Routes: https://www.dwellmark.io/prototype/packet-builder?persona=packet_builder, https://www.dwellmark.io/prototype/packet-command-center?persona=packet_builder
- Advisor review order (high): Owner question: Should advisors start with open issues, claim decisions, evidence requests, or packet readiness? Design task: Return the preferred advisor review sequence and any copy/action labels needed for comments, requests, and claim decisions. Decision needed: Advisor workflow order before permissioned advisor accounts are introduced. Expected return: Advisor journey notes with route order, action labels, and missing context. Routes: https://www.dwellmark.io/prototype/advisor-resolution-center?persona=advisor_review, https://www.dwellmark.io/prototype/claim-review-board?persona=advisor_review
- Mobile privacy trust (high): Owner question: How should mobile capture, iOS device QA signoff, exact-location redaction, consent, and advisor export permission be explained without alarming users? Design task: Review the mobile privacy and device-QA path and return copy/layout guidance for owner-controlled capture and redaction. Decision needed: Small-screen trust language before real mobile capture and private storage are connected. Expected return: Mobile privacy and device-QA notes with copy changes, control grouping, and any responsive layout issues. Routes: https://www.dwellmark.io/prototype/mobile-capture-center?persona=privacy_review, https://www.dwellmark.io/prototype/privacy-redaction-center?persona=privacy_review
- Residency track balance (high): Owner question: Does the product feel broad enough for non-Act 60 users while still making Act 60 users feel supported? Design task: Review track routing, domicile workflows, former-resident flows, Florida domicile, Act 60, and multi-state exposure as one coherent system. Decision needed: Track naming and hierarchy before onboarding/auth asks users to choose a path. Expected return: Track-system recommendation with naming, order, and any missing scenario notes. Routes: https://www.dwellmark.io/prototype/residency-track-router?persona=former_act60, https://www.dwellmark.io/prototype/binders?persona=act60_user
- Dense component system (medium): Owner question: Which repeated cards, ledgers, status pills, actions, and route links need a reusable component language before visual polish? Design task: Normalize repeated operational UI patterns so the prototype can be redesigned consistently across owner, advisor, packet, and privacy surfaces. Decision needed: Reusable component guidance before UX changes are implemented across dozens of public prototype sections. Expected return: Component notes with state semantics, spacing rules, responsive behavior, and reuse guidance. Routes: https://www.dwellmark.io/design-handoff#components, https://www.dwellmark.io/prototype#screens

## Design Tool Launch Checklist

- Google Stitch visual exploration (Google Stitch): Entry: https://www.dwellmark.io/design-handoff. Context: https://www.dwellmark.io/prototype, https://www.dwellmark.io/api/design-handoff/markdown, https://www.dwellmark.io/llms.txt. Prompt: Redesign the public Dwellmark prototype for premium residency defense UX. Preserve no-auth access, seeded data, packet-first workflows, privacy boundaries, advisor-safe language, and Act 60 as one supported module. Boundaries: No login wall, No real uploads, No exact coordinates, No tax or legal advice. Expected output: Visual hierarchy and responsive layout recommendations for owner, advisor, packet, mobile privacy, iOS device QA, and track-breadth flows.
- Claude UX critique (Claude design review): Entry: https://www.dwellmark.io/api/design-handoff/markdown. Context: https://www.dwellmark.io/design-handoff#intake-board, https://www.dwellmark.io/design-handoff#scenario-matrix, https://www.dwellmark.io/design-handoff#copy-tone. Prompt: Critique the Dwellmark public prototype using the intake board, scenario matrix, copy and tone matrix, and response template. Return route-level findings with persona, viewport, severity, recommendation, and boundary impact. Boundaries: Preserve residency-defense positioning, Keep Act 60 balanced, Avoid outcome guarantees, Defer auth and production data. Expected output: Prioritized UX findings in the design review response template format.
- Human product review (Founder, advisor, or product reviewer): Entry: https://www.dwellmark.io/design-handoff#runbook. Context: https://www.dwellmark.io/prototype/workspace?persona=weak_evidence, https://www.dwellmark.io/prototype/advisor-resolution-center?persona=advisor_review. Prompt: Walk the runbook in order and answer the intake-board questions before commenting on visual polish. Focus on comprehension, advisor usefulness, packet trust, privacy clarity, and product positioning. Boundaries: Review seeded data only, Keep advisor permission explicit, Do not request production auth changes yet, Flag legal-advice risk. Expected output: Decision notes for the intake board plus route-specific UX blockers.
- Copy and positioning pass (Copy reviewer or AI writing pass): Entry: https://www.dwellmark.io/design-handoff#copy-tone. Context: https://www.dwellmark.io/llms.txt, https://www.dwellmark.io/prototype/residency-track-router?persona=former_act60, https://www.dwellmark.io/prototype/packet-builder?persona=packet_builder. Prompt: Review Dwellmark copy for premium, calm, advisor-compatible residency defense language. Preserve packet-first framing, privacy clarity, and Act 60 balance while removing tax-advice or guarantee language. Boundaries: No tax savings claims, No guarantee language, No surveillance tone, No Act 60-only positioning. Expected output: Current copy, recommended copy, reason, and preserved-boundary notes.
- Engineering handoff return (Design-to-engineering handback): Entry: https://www.dwellmark.io/design-handoff#response-template. Context: https://www.dwellmark.io/design-handoff#acceptance-kit, https://www.dwellmark.io/design-handoff#qa-matrix, https://www.dwellmark.io/design-handoff#coverage-matrix. Prompt: Return accepted design recommendations in implementation-ready shape. Include route, persona, viewport, severity, component impact, copy changes, preserved boundaries, and deferred production work. Boundaries: Keep public demo mode separate, Do not require auth before UX approval, Preserve verifiable handoff URLs, Call out any data/privacy risks. Expected output: Implementation queue suitable for engineering to apply without guessing.

## Design Handoff Completion Audit

- Handoff entrypoints (ready): Design tools have public, copy-ready starting points for the rendered brief, prototype route map, Markdown brief, JSON manifest, and LLM guide. Reviewer action: Start at `/design-handoff`, then use `/prototype` or `/api/design-handoff/markdown` when a tool needs a route index or text brief. Routes: https://www.dwellmark.io/design-handoff, https://www.dwellmark.io/prototype, https://www.dwellmark.io/api/design-handoff/markdown, https://www.dwellmark.io/api/design-handoff/demo, https://www.dwellmark.io/llms.txt
- Product surface readiness (ready): The public prototype covers owner dashboard, day ledger, evidence, domicile, residency tracks, business presence, advisor review, mobile device QA, privacy, and packet workflows. Reviewer action: Review owner, advisor, packet, privacy, business, Act 60, former Act 60, and Florida domicile states before proposing visual changes. Routes: https://www.dwellmark.io/prototype#screens, https://www.dwellmark.io/prototype#personas, https://www.dwellmark.io/design-handoff#scenario-matrix, https://www.dwellmark.io/design-handoff#runbook
- Review material readiness (ready): The handoff package includes prompts, intake questions, response template, copy guardrails, QA matrix, acceptance kit, and launch checklist. Reviewer action: Use the intake board and response template to return decisions that engineering can implement without guessing. Routes: https://www.dwellmark.io/design-handoff#intake-board, https://www.dwellmark.io/design-handoff#response-template, https://www.dwellmark.io/design-handoff#copy-tone, https://www.dwellmark.io/design-handoff#launch-checklist
- Manual UX review (needs-review): The workflows are ready for design inspection, but visual hierarchy, responsive density, component language, and first-screen comprehension still need human or design-tool judgment. Reviewer action: Return route-level findings with persona, viewport, severity, recommendation, and preserved-boundary notes. Routes: https://www.dwellmark.io/design-handoff#viewport-matrix, https://www.dwellmark.io/design-handoff#components, https://www.dwellmark.io/design-handoff#feedback-worksheet, https://www.dwellmark.io/prototype/workspace?persona=weak_evidence
- Production deferral (deferred): Auth, real evidence uploads, private Supabase storage, billing, advisor invites, role gates, and production data stay deferred until the UX direction is approved. Reviewer action: Flag any recommendation that would require login, private data, exact coordinates, real uploads, billing, or production persistence before UX approval. Routes: https://www.dwellmark.io/design-handoff#decision-register, https://www.dwellmark.io/design-handoff#coverage-matrix, https://www.dwellmark.io/design-handoff#qa-matrix, https://www.dwellmark.io/llms.txt

## High-Priority Review Paths

- Must review before UX handoff: https://www.dwellmark.io/prototype/design-handoff, https://www.dwellmark.io/prototype/workspace, https://www.dwellmark.io/prototype/residency-intake-center, https://www.dwellmark.io/prototype/ledger-review-center, https://www.dwellmark.io/prototype/packet-builder, https://www.dwellmark.io/prototype/privacy-redaction-center
- Advisor and packet depth: https://www.dwellmark.io/prototype/advisor-resolution-center, https://www.dwellmark.io/prototype/claim-review-board, https://www.dwellmark.io/prototype/residency-defense-brief, https://www.dwellmark.io/prototype/packet-command-center, https://www.dwellmark.io/prototype/packet-integrity-lab, https://www.dwellmark.io/prototype/annual-review-center
- Residency track breadth: https://www.dwellmark.io/prototype/residency-track-router, https://www.dwellmark.io/prototype/domicile-workbench, https://www.dwellmark.io/prototype/domicile-evidence-plan, https://www.dwellmark.io/prototype/business-presence-center, https://www.dwellmark.io/prototype/risk-center, https://www.dwellmark.io/prototype/jurisdiction-module-workbench
- Operations readiness: https://www.dwellmark.io/prototype/mobile-capture-center, https://www.dwellmark.io/prototype/evidence-source-workbench, https://www.dwellmark.io/prototype/household-operations-center, https://www.dwellmark.io/prototype/validation-pricing-center, https://www.dwellmark.io/prototype/launch-operations-center, https://www.dwellmark.io/prototype/server-operations

## Persona States

- Clean owner: https://www.dwellmark.io/prototype/persona/clean_user (https://www.dwellmark.io/?persona=clean_user)
- Weak evidence: https://www.dwellmark.io/prototype/persona/weak_evidence (https://www.dwellmark.io/?persona=weak_evidence&tab=daycounts)
- Advisor review: https://www.dwellmark.io/prototype/persona/advisor_review (https://www.dwellmark.io/?persona=advisor_review&tab=advisor)
- Packet ready: https://www.dwellmark.io/prototype/persona/packet_ready (https://www.dwellmark.io/?persona=packet_ready&tab=packet)
- Business exposure: https://www.dwellmark.io/prototype/persona/business_exposure (https://www.dwellmark.io/?persona=business_exposure)
- Act 60 track: https://www.dwellmark.io/prototype/persona/act60_user (https://www.dwellmark.io/?persona=act60_user)
- Former Act 60: https://www.dwellmark.io/prototype/persona/former_act60 (https://www.dwellmark.io/?persona=former_act60&year=2025)
- Florida domicile: https://www.dwellmark.io/prototype/persona/florida_domicile (https://www.dwellmark.io/?persona=florida_domicile&tab=packet)
- Privacy review: https://www.dwellmark.io/prototype/persona/privacy_review (https://www.dwellmark.io/?persona=privacy_review&tab=advisor)
- Packet builder: https://www.dwellmark.io/prototype/persona/packet_builder (https://www.dwellmark.io/?persona=packet_builder&tab=packet)

## Journey Starts

- Owner first pass: https://www.dwellmark.io/prototype/design-handoff?persona=weak_evidence
- Advisor review pass: https://www.dwellmark.io/prototype/advisor-resolution-center?persona=advisor_review
- Packet export pass: https://www.dwellmark.io/prototype/packet-builder?persona=packet_builder
- Business and privacy pass: https://www.dwellmark.io/prototype/business-presence-center?persona=business_exposure

## Viewport QA Matrix

- Desktop command center (1440 x 1100): https://www.dwellmark.io/prototype/workspace?persona=weak_evidence -- Dashboard hierarchy, dense metrics, weak-day prompts, and first-pass owner comprehension.
- Tablet advisor review (820 x 1180): https://www.dwellmark.io/prototype/advisor-resolution-center?persona=advisor_review -- Advisor issue queue, comments, request flow, claim decisions, and packet review density.
- Mobile owner capture (390 x 844): https://www.dwellmark.io/prototype/mobile-capture-center?persona=privacy_review -- Mobile capture readiness, iOS device QA signoff, privacy controls, evidence-source consent, and redaction language.
- Desktop packet export (1280 x 900): https://www.dwellmark.io/prototype/packet-builder?persona=packet_builder -- Audit packet builder, command center, integrity lab, annual review, and export-readiness state.

## Design Tool Prompt Pack

- Product comprehension redesign: https://www.dwellmark.io/ -- Improve first-time owner comprehension of Dwellmark as a residency defense platform without adding login, billing, or real-data flows.. Current app states: https://www.dwellmark.io/, https://www.dwellmark.io/?tab=daycounts, https://www.dwellmark.io/?tab=evidence, https://www.dwellmark.io/?tab=evidence&filter=financial, https://www.dwellmark.io/?tab=packet, https://www.dwellmark.io/?tab=advisor, https://www.dwellmark.io/?tab=packet&year=2025, https://www.dwellmark.io/?tab=daycounts&persona=weak_evidence, https://www.dwellmark.io/?tab=advisor&persona=advisor_review, https://www.dwellmark.io/?tab=packet&persona=packet_ready, https://www.dwellmark.io/?tab=advisor&persona=privacy_review, https://www.dwellmark.io/?tab=packet&persona=florida_domicile, https://www.dwellmark.io/?persona=act60_user, https://www.dwellmark.io/?persona=former_act60&year=2025, https://www.dwellmark.io/?tab=evidence&persona=privacy_review. Legacy prototype start: https://www.dwellmark.io/prototype/workspace?persona=weak_evidence
- Advisor review redesign: https://www.dwellmark.io/ -- Make advisor issue review, evidence requests, claim decisions, and packet blockers easier to scan before authenticated advisor flows are added.. Current app states: https://www.dwellmark.io/, https://www.dwellmark.io/?tab=daycounts, https://www.dwellmark.io/?tab=evidence, https://www.dwellmark.io/?tab=evidence&filter=financial, https://www.dwellmark.io/?tab=packet, https://www.dwellmark.io/?tab=advisor, https://www.dwellmark.io/?tab=packet&year=2025, https://www.dwellmark.io/?tab=daycounts&persona=weak_evidence, https://www.dwellmark.io/?tab=advisor&persona=advisor_review, https://www.dwellmark.io/?tab=packet&persona=packet_ready, https://www.dwellmark.io/?tab=advisor&persona=privacy_review, https://www.dwellmark.io/?tab=packet&persona=florida_domicile, https://www.dwellmark.io/?persona=act60_user, https://www.dwellmark.io/?persona=former_act60&year=2025, https://www.dwellmark.io/?tab=evidence&persona=privacy_review. Legacy prototype start: https://www.dwellmark.io/prototype/advisor-resolution-center?persona=advisor_review
- Mobile and privacy redesign: https://www.dwellmark.io/ -- Refine mobile capture, iOS device QA signoff, evidence source consent, privacy redaction, and data-control language for small screens.. Current app states: https://www.dwellmark.io/, https://www.dwellmark.io/?tab=daycounts, https://www.dwellmark.io/?tab=evidence, https://www.dwellmark.io/?tab=evidence&filter=financial, https://www.dwellmark.io/?tab=packet, https://www.dwellmark.io/?tab=advisor, https://www.dwellmark.io/?tab=packet&year=2025, https://www.dwellmark.io/?tab=daycounts&persona=weak_evidence, https://www.dwellmark.io/?tab=advisor&persona=advisor_review, https://www.dwellmark.io/?tab=packet&persona=packet_ready, https://www.dwellmark.io/?tab=advisor&persona=privacy_review, https://www.dwellmark.io/?tab=packet&persona=florida_domicile, https://www.dwellmark.io/?persona=act60_user, https://www.dwellmark.io/?persona=former_act60&year=2025, https://www.dwellmark.io/?tab=evidence&persona=privacy_review. Legacy prototype start: https://www.dwellmark.io/prototype/mobile-capture-center?persona=privacy_review
- Packet export redesign: https://www.dwellmark.io/ -- Make the packet builder, blocker list, integrity checks, and annual export history feel like a premium, trustworthy audit file workflow.. Current app states: https://www.dwellmark.io/, https://www.dwellmark.io/?tab=daycounts, https://www.dwellmark.io/?tab=evidence, https://www.dwellmark.io/?tab=evidence&filter=financial, https://www.dwellmark.io/?tab=packet, https://www.dwellmark.io/?tab=advisor, https://www.dwellmark.io/?tab=packet&year=2025, https://www.dwellmark.io/?tab=daycounts&persona=weak_evidence, https://www.dwellmark.io/?tab=advisor&persona=advisor_review, https://www.dwellmark.io/?tab=packet&persona=packet_ready, https://www.dwellmark.io/?tab=advisor&persona=privacy_review, https://www.dwellmark.io/?tab=packet&persona=florida_domicile, https://www.dwellmark.io/?persona=act60_user, https://www.dwellmark.io/?persona=former_act60&year=2025, https://www.dwellmark.io/?tab=evidence&persona=privacy_review. Legacy prototype start: https://www.dwellmark.io/prototype/packet-builder?persona=packet_builder

## UX Feedback Worksheet

- First impression and category clarity (critical): https://www.dwellmark.io/prototype/workspace?persona=weak_evidence -- Can a first-time owner understand that Dwellmark is for residency defense, evidence quality, and audit packet readiness within the first screen?
- Advisor review loop (high): https://www.dwellmark.io/prototype/advisor-resolution-center?persona=advisor_review -- Can an advisor quickly see open issues, request evidence, comment on claims, and understand what blocks packet export?
- Mobile privacy comprehension (high): https://www.dwellmark.io/prototype/privacy-redaction-center?persona=privacy_review -- Do mobile device QA, privacy, exact-location redaction, evidence-source consent, and advisor export controls feel explicit without becoming alarming?
- Packet confidence and export readiness (critical): https://www.dwellmark.io/prototype/packet-builder?persona=packet_builder -- Does the packet builder clearly communicate readiness, blockers, manifest sections, integrity checks, and export history as the hero workflow?
- Act 60 balance (medium): https://www.dwellmark.io/prototype/binders?persona=act60_user -- Does Act 60 read as one supported module inside a broader residency-defense product, not as the whole product identity?

## Public Demo APIs

- /api/design-handoff/demo
- /api/design-handoff/markdown
- /api/dashboard/demo
- /api/ledger/demo/days
- /api/advisor/demo/issue-queue
- /api/mobile/demo/capture
- /api/operations/demo
- /api/privacy/demo/controls
- /api/validation/demo/readiness
- /api/audit-packet/demo
- /api/backend/readiness
- /api/backend/production-readiness

## Public Demo API Absolute URLs

- https://www.dwellmark.io/api/design-handoff/demo
- https://www.dwellmark.io/api/design-handoff/markdown
- https://www.dwellmark.io/api/dashboard/demo
- https://www.dwellmark.io/api/ledger/demo/days
- https://www.dwellmark.io/api/advisor/demo/issue-queue
- https://www.dwellmark.io/api/mobile/demo/capture
- https://www.dwellmark.io/api/operations/demo
- https://www.dwellmark.io/api/privacy/demo/controls
- https://www.dwellmark.io/api/validation/demo/readiness
- https://www.dwellmark.io/api/audit-packet/demo
- https://www.dwellmark.io/api/backend/readiness
- https://www.dwellmark.io/api/backend/production-readiness

## Do Not Assume

- Do not assume login, signup, billing, real evidence uploads, or private storage are part of this public review mode.
- Do not treat Act 60 as the product identity; it is one supported residency track.
- Do not present Dwellmark as tax or legal advice, a residency guarantee, or a location-spoofing tool.