First-paint comprehension, readiness seal, KPI strip, readiness chain, advisor/packet next action.
/https://www.dwellmark.io/Review boundary
Ready for external UX review
Current Product Surface
Owner Command Center review URLs
Use these public, no-login URLs for the current Dwellmark experience. The older prototype route map remains available for broader workflow context, but these are the primary review states for the redesigned homepage.
Presence by month, recent day ledger, weak-day Add proof prompts, Minnesota watch rail.
/?tab=daycountshttps://www.dwellmark.io/?tab=daycountsEvidence confidence summary, filters, quality column, detail drawer, add-evidence modal.
/?tab=evidencehttps://www.dwellmark.io/?tab=evidenceStable filtered evidence state for advisor and packet blocker review.
/?tab=evidence&filter=financialhttps://www.dwellmark.io/?tab=evidence&filter=financialSix-section manifest, financial ties blocker, packet readiness rail, auditor-receives list.
/?tab=packethttps://www.dwellmark.io/?tab=packetPermissioned advisor review, access scope, response flow, sign-off status, city-level privacy copy.
/?tab=advisorhttps://www.dwellmark.io/?tab=advisorRead-only filed-year banner and disabled assemble/edit actions.
/?tab=packet&year=2025https://www.dwellmark.io/?tab=packet&year=2025Thin day proof, adaptive proof prompts, mobile capture action, and packet consequences.
/?tab=daycounts&persona=weak_evidencehttps://www.dwellmark.io/?tab=daycounts&persona=weak_evidenceAdvisor queue, issue response, access scope, city-level privacy, and sign-off readiness.
/?tab=advisor&persona=advisor_reviewhttps://www.dwellmark.io/?tab=advisor&persona=advisor_reviewCompleted packet sections, clean integrity state, approved advisor export, and premium ready-state language.
/?tab=packet&persona=packet_readyhttps://www.dwellmark.io/?tab=packet&persona=packet_readyExact-location redaction, advisor export permission, retention language, and non-alarming owner controls.
/?tab=advisor&persona=privacy_reviewhttps://www.dwellmark.io/?tab=advisor&persona=privacy_reviewFlorida domicile ties, declarations, vehicle/licensing proof, and advisor-compatible packet sections.
/?tab=packet&persona=florida_domicilehttps://www.dwellmark.io/?tab=packet&persona=florida_domicileAct 60 as one supported module inside broader residency defense, not the default product identity.
/?persona=act60_userhttps://www.dwellmark.io/?persona=act60_userArchived former-resident state, read-only retention language, and post-move documentation context.
/?persona=former_act60&year=2025https://www.dwellmark.io/?persona=former_act60&year=2025Mobile proof capture prompt, evidence confidence, exact-location boundary, and small-screen review entry.
/?tab=evidence&persona=privacy_reviewhttps://www.dwellmark.io/?tab=evidence&persona=privacy_reviewUX Handoff Readiness Scorecard
Ready, review, and deferred handoff states
The prototype, handoff brief, route map, aliases, Markdown, llms.txt, sitemap, and public demo APIs are reachable without auth.
Use public routes for Stitch, Claude, and human review.Personas, route aliases, journeys, viewport matrix, prompt pack, packet index, decision register, runbook, and response template cover the UX pass.
Run the handoff runbook and return findings in the response template.The handoff package preserves residency-defense positioning, seeded data, no exact coordinates, Act 60 as one module, and no tax/legal advice.
Preserve locked decisions while changing hierarchy, layout, copy, and interaction patterns.The package gives designers concrete routes, personas, expected outputs, done criteria, and return fields.
Start with owner command center, advisor/packet flow, mobile privacy, and component system passes.The product workflows are complete enough for design review, but visual hierarchy, density, typography, and responsive polish should be refined by the design pass.
Return route-level visual and interaction recommendations before auth integration.Auth, real uploads, private storage, billing, advisor invites, and production role gates remain intentionally deferred until UX approval.
Keep production integrations out of the design-tool handoff and preserve demo mode separately.UX Handoff Coverage Matrix
Roadmap requirements mapped to public review proof
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.
Reviewer action: Open `/design-handoff`, `/prototype`, and the JSON manifest from a clean browser session before visual review.The prototype includes general domicile, Florida move, former-resident documentation, Act 60, multi-state exposure, business presence, advisor review, and audit packet workflows.
Reviewer action: Review copy in the route map, packet builder, track router, and Act 60 binder for balanced product positioning.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.
Reviewer action: Preserve privacy and seeded-data boundaries during design changes; move real uploads and auth into a later production phase.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.
Reviewer action: Walk the owner, advisor, packet, and privacy/business journeys and return route-level findings with persona and viewport context.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.
Reviewer action: Use the URL guide for every returned finding so engineering can reproduce the exact public state.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.
Reviewer action: Review `/prototype/mobile-capture-center?persona=privacy_review` at mobile width and compare the visible checklist with `/api/mobile/demo/capture`.The persona catalog and route aliases expose 10 seeded states with deep links, absolute URLs, and route-map cards for direct design review.
Reviewer action: Start with weak evidence, advisor review, privacy review, and packet-builder personas before visual polish.The runbook, prompt pack, feedback worksheet, response template, packet index, and acceptance kit define review order, expected outputs, return fields, severity, and preserved boundaries.
Reviewer action: Return findings using route, persona, viewport, severity, recommendation, and boundary impact fields.The decision register, readiness scorecard, acceptance kit, guardrails, and llms.txt all preserve public prototype mode and explicitly defer auth/real-data work.
Reviewer action: Do not add signup, login, billing, private uploads, exact-location display, or role-based gates during UX refinement.UX Handoff QA Matrix
Automated coverage and visual review responsibilities
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.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.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.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.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.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.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.Design Review Scenario Matrix
Route-specific missions and success signals
Decide whether a first-time owner can understand their residency risk, weak days, evidence confidence, and packet readiness in one scan.
Walk the advisor from open issue to comment, evidence request, claim decision, and packet blocker review.
Review mobile capture, iOS device QA signoff, evidence-source consent, exact-location redaction, advisor permission, and retention language on a small screen.
Judge whether the audit packet feels like the hero workflow across manifest sections, blockers, privacy choices, integrity, and export history.
Confirm the product reads as broad residency defense across domicile, Florida, former-resident, Act 60, multi-state, and business exposure tracks.
Normalize repeated cards, status pills, ledgers, route links, privacy controls, and packet artifacts into reusable design-system guidance.
Handoff Acceptance Kit
Preflight confirmations before external UX review
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.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.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.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.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.Design Review Response Template
Return findings in this engineering-ready shape
Summarize whether the public prototype is ready for visual refinement, what changed in the recommended UX direction, and what still blocks handoff.
Return findings tied to stable public routes, persona states, and viewport context so engineering can apply changes without guessing.
Identify language that should change or stay fixed, especially around residency defense, Act 60 as one module, privacy, advisor review, and tax/legal boundaries.
Document reusable patterns for cards, ledgers, status pills, privacy controls, route links, packet artifacts, and dense operational panels.
Report desktop, tablet, and mobile review results against the viewport matrix and call out any layout, density, or readability problems.
Confirm the redesign preserves public prototype access, seeded data only, no exact coordinates, no tax/legal advice, and deferred auth or real-data work.
List ideas that belong after UX approval, such as auth, real uploads, private storage, billing, advisor invites, or role-based permissions.
Design Handoff Runbook
Step-by-step UX review sequence
Confirm the product category, public prototype mode, sensitive-data boundary, and review package before redesign work starts.
Notes on product comprehension, missing context, and any boundary questions that must be resolved before visual exploration.
Review first-screen clarity, day counts, weak evidence prompts, proof strategy, and packet-readiness hierarchy.
Desktop and mobile recommendations for owner comprehension, hierarchy, copy, and route sequencing.
Review advisor comments, evidence requests, claim decisions, packet blockers, and export-ready language.
Advisor workflow notes and packet-builder recommendations that preserve the no-advice boundary.
Review mobile capture, iOS device QA signoff, evidence-source consent, exact-location redaction, advisor export permission, and retention language.
Mobile layout notes, device-QA signoff recommendations, privacy copy recommendations, and any small-screen component fixes.
Normalize cards, ledgers, status pills, route links, privacy controls, packet artifacts, and dense operational patterns.
Component inventory notes with reusable patterns, state semantics, and responsive behavior recommendations.
Return design findings in a format engineering can act on after UX approval.
Prioritized findings with route references, viewport notes, copy changes, preserved boundaries, and deferred-auth notes.
Design Decision Register
Locked, open, and deferred UX decisions
Dwellmark is a residency defense and documentation platform, not an Act 60-only product.
The UX must support broader domicile, day tracking, advisor review, evidence quality, and audit packet workflows.Lead with residency defense and packet readiness; keep Act 60 as one supported module inside the track system.
The complete product prototype remains public and no-auth until UX refinement is approved.
External design tools and reviewers need stable URLs before login, private storage, and role gates are introduced.Do not add signup walls, private redirects, billing gates, or real upload requirements to the review experience.
Design review uses seeded data only and must not expose real evidence, secrets, exact coordinates, or service-role values.
Residency proof, exact location, advisor access, evidence files, and audit metadata are sensitive product surfaces.Keep privacy language explicit and calm; preserve owner-controlled redaction and permissioned advisor access.
The first screen still needs design judgment on hierarchy, density, and where packet readiness should dominate.
The prototype has the needed data, but UX review should decide the clearest premium command-center structure.Return recommendations for first-viewport hierarchy, metric grouping, weak-day prompts, and packet-readiness emphasis.
The advisor issue queue, claim review, and packet builder need UX review before role-based auth is wired.
Advisor review must feel useful to CPAs, attorneys, and other reviewers without implying legal or tax advice.Return flow notes for comments, evidence requests, packet blockers, claim decisions, and export-ready states.
Login, real evidence uploads, storage persistence, billing, and role-based production flows come after UX approval.
Design tools need public access now, and production security should be wired only after the target UX is stable.Do not design around account creation as the first screen; preserve public demo/design mode as a separate surface.
Handoff Packet Index
What designers should inspect and return
Understand the category, boundaries, public routes, personas, and expected review outputs before changing screens.
A brief notes page confirming the product promise, no-auth review mode, sensitive-data boundaries, and open questions.
Improve category clarity, owner comprehension, dashboard hierarchy, day-count confidence, and packet-readiness scanning.
Annotated desktop and mobile recommendations for the first owner pass, with copy that preserves the legal and privacy boundaries.
Refine advisor issue review, claim decisions, evidence requests, packet blockers, and export-readiness language.
Advisor-review flow notes, packet hierarchy recommendations, and unresolved workflow questions before auth is introduced.
Check capture readiness, iOS device QA signoff, exact-location redaction, evidence-source consent, advisor export permission, and small-screen density.
Mobile layout notes, device-QA signoff recommendations, and privacy wording that avoid real upload, signup, or exact-coordinate assumptions.
Normalize dense operational cards, status pills, ledgers, route links, privacy controls, and packet artifact states.
Component notes covering hierarchy, spacing, responsive behavior, status semantics, and reusable patterns for later implementation.
Return findings in a format that engineering can apply after the design pass without losing product boundaries.
A prioritized list of UX findings, revised route/screen references, viewport notes, copy changes, and preserved-boundary notes.
Readiness Report
Evidence that this prototype is ready for UX handoff
The prototype, handoff brief, route map, screen aliases, and persona aliases are public seeded routes with no auth redirect.
Open the prototype and route map directly from an external design tool before changing UX structure.JSON, Markdown, sitemap, robots, and llms.txt handoff surfaces expose the same canonical URLs and review boundaries.
Use the JSON or Markdown package when a tool needs structured context instead of the rendered page.Design review covers seeded owner, advisor, packet, business, privacy, Act 60, former Act 60, and Florida domicile states across the full screen inventory.
Start with weak evidence, advisor review, privacy review, and packet-builder personas before visual polish.Owner, advisor, packet export, and business/privacy journeys each have start states, expected outcomes, and route-style review URLs.
Walk each journey once and return blockers through the UX feedback worksheet.Desktop, tablet, and mobile viewport passes, prompt pack entries, and structured worksheet questions are all available from public routes.
Run the viewport matrix first, then use the prompt pack and worksheet fields for design notes.The handoff package preserves seeded data, no secrets, no private evidence, no exact coordinates, Act 60 as one module, and no tax/legal advice.
Preserve these boundaries while redesigning hierarchy, density, copy, and navigation.Canonical URLs
Copy-ready links for external design tools
Primary public app experience with seeded data and no auth redirect.
Handoff panelhttps://www.dwellmark.io/First in-product design review panel with personas, routes, and checklist state.
Prototype route maphttps://www.dwellmark.io/prototypeComplete screen, persona, journey, and public API route inventory.
JSON manifesthttps://www.dwellmark.io/api/design-handoff/demoMachine-readable handoff package for crawlers, design tools, and automated checks.
Markdown briefhttps://www.dwellmark.io/api/design-handoff/markdownPlain-text handoff brief for tools that prefer Markdown over rendered pages.
AI review guidehttps://www.dwellmark.io/llms.txtConcise LLM-readable product context, boundaries, personas, journeys, and API surfaces.
Design Handoff URL Guide
Canonical routes, patterns, and examples for review tools
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.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.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.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.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.Route-style URL for opening a seeded persona state directly.
Reviewer action: Replace `[persona]` with a persona id before starting a state-specific review.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.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.Open URLText-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.Open URLConcise 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.Open URLSitemap 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.Open URLReview Guardrails
Do not redesign these product boundaries away
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.
Stable screen aliases use https://www.dwellmark.io/prototype/[screen]; persona states use https://www.dwellmark.io/prototype/persona/[persona].
Viewport QA Matrix
Review these states across desktop, tablet, and mobile
Dashboard hierarchy, dense metrics, weak-day prompts, and first-pass owner comprehension.
- /prototype/workspacehttps://www.dwellmark.io/prototype/workspace
- /prototype/residency-intake-centerhttps://www.dwellmark.io/prototype/residency-intake-center
- /prototype/ledger-review-centerhttps://www.dwellmark.io/prototype/ledger-review-center
- /prototype/requestshttps://www.dwellmark.io/prototype/requests
Advisor issue queue, comments, request flow, claim decisions, and packet review density.
- /prototype/advisor-resolution-centerhttps://www.dwellmark.io/prototype/advisor-resolution-center
- /prototype/claim-review-boardhttps://www.dwellmark.io/prototype/claim-review-board
- /prototype/residency-defense-briefhttps://www.dwellmark.io/prototype/residency-defense-brief
- /prototype/packet-builderhttps://www.dwellmark.io/prototype/packet-builder
Mobile capture readiness, iOS device QA signoff, privacy controls, evidence-source consent, and redaction language.
- /prototype/mobile-capture-centerhttps://www.dwellmark.io/prototype/mobile-capture-center
- /prototype/evidence-source-workbenchhttps://www.dwellmark.io/prototype/evidence-source-workbench
- /prototype/privacy-redaction-centerhttps://www.dwellmark.io/prototype/privacy-redaction-center
- /prototype/ledgerhttps://www.dwellmark.io/prototype/ledger
Audit packet builder, command center, integrity lab, annual review, and export-readiness state.
- /prototype/packet-builderhttps://www.dwellmark.io/prototype/packet-builder
- /prototype/packet-command-centerhttps://www.dwellmark.io/prototype/packet-command-center
- /prototype/packet-integrity-labhttps://www.dwellmark.io/prototype/packet-integrity-lab
- /prototype/annual-review-centerhttps://www.dwellmark.io/prototype/annual-review-center
Design Tool Prompt Pack
Copy these prompts into Stitch, Claude, or a human UX brief
Improve first-time owner comprehension of Dwellmark as a residency defense platform without adding login, billing, or real-data flows.
Redesign the public Dwellmark prototype starting from the owner command center. Preserve the product contract: residency defense, seeded data only, no auth wall, no tax/legal advice, Act 60 as one supported track, and audit packet as the hero object. Improve hierarchy, scanability, and the path from day counts to evidence gaps to packet readiness.
- /https://www.dwellmark.io/
- /?tab=daycountshttps://www.dwellmark.io/?tab=daycounts
- /?tab=evidencehttps://www.dwellmark.io/?tab=evidence
- /?tab=evidence&filter=financialhttps://www.dwellmark.io/?tab=evidence&filter=financial
- /?tab=packethttps://www.dwellmark.io/?tab=packet
- /?tab=advisorhttps://www.dwellmark.io/?tab=advisor
- /?tab=packet&year=2025https://www.dwellmark.io/?tab=packet&year=2025
- /?tab=daycounts&persona=weak_evidencehttps://www.dwellmark.io/?tab=daycounts&persona=weak_evidence
- /?tab=advisor&persona=advisor_reviewhttps://www.dwellmark.io/?tab=advisor&persona=advisor_review
- /?tab=packet&persona=packet_readyhttps://www.dwellmark.io/?tab=packet&persona=packet_ready
- /?tab=advisor&persona=privacy_reviewhttps://www.dwellmark.io/?tab=advisor&persona=privacy_review
- /?tab=packet&persona=florida_domicilehttps://www.dwellmark.io/?tab=packet&persona=florida_domicile
- /?persona=act60_userhttps://www.dwellmark.io/?persona=act60_user
- /?persona=former_act60&year=2025https://www.dwellmark.io/?persona=former_act60&year=2025
- /?tab=evidence&persona=privacy_reviewhttps://www.dwellmark.io/?tab=evidence&persona=privacy_review
- /prototype/workspacehttps://www.dwellmark.io/prototype/workspace
- /prototype/residency-intake-centerhttps://www.dwellmark.io/prototype/residency-intake-center
- /prototype/proof-strategy-plannerhttps://www.dwellmark.io/prototype/proof-strategy-planner
- /prototype/ledger-review-centerhttps://www.dwellmark.io/prototype/ledger-review-center
Make advisor issue review, evidence requests, claim decisions, and packet blockers easier to scan before authenticated advisor flows are added.
Redesign the advisor review path for a CPA, attorney, or SALT advisor. Keep advisor access explicitly permissioned, keep exact location redacted by default, and avoid turning the prototype into legal or tax advice. Improve the issue queue, comments, evidence requests, claim review board, and packet export gates.
- /https://www.dwellmark.io/
- /?tab=daycountshttps://www.dwellmark.io/?tab=daycounts
- /?tab=evidencehttps://www.dwellmark.io/?tab=evidence
- /?tab=evidence&filter=financialhttps://www.dwellmark.io/?tab=evidence&filter=financial
- /?tab=packethttps://www.dwellmark.io/?tab=packet
- /?tab=advisorhttps://www.dwellmark.io/?tab=advisor
- /?tab=packet&year=2025https://www.dwellmark.io/?tab=packet&year=2025
- /?tab=daycounts&persona=weak_evidencehttps://www.dwellmark.io/?tab=daycounts&persona=weak_evidence
- /?tab=advisor&persona=advisor_reviewhttps://www.dwellmark.io/?tab=advisor&persona=advisor_review
- /?tab=packet&persona=packet_readyhttps://www.dwellmark.io/?tab=packet&persona=packet_ready
- /?tab=advisor&persona=privacy_reviewhttps://www.dwellmark.io/?tab=advisor&persona=privacy_review
- /?tab=packet&persona=florida_domicilehttps://www.dwellmark.io/?tab=packet&persona=florida_domicile
- /?persona=act60_userhttps://www.dwellmark.io/?persona=act60_user
- /?persona=former_act60&year=2025https://www.dwellmark.io/?persona=former_act60&year=2025
- /?tab=evidence&persona=privacy_reviewhttps://www.dwellmark.io/?tab=evidence&persona=privacy_review
- /prototype/advisor-resolution-centerhttps://www.dwellmark.io/prototype/advisor-resolution-center
- /prototype/claim-review-boardhttps://www.dwellmark.io/prototype/claim-review-board
- /prototype/residency-defense-briefhttps://www.dwellmark.io/prototype/residency-defense-brief
- /prototype/packet-builderhttps://www.dwellmark.io/prototype/packet-builder
Refine mobile capture, iOS device QA signoff, evidence source consent, privacy redaction, and data-control language for small screens.
Review the mobile capture and privacy surfaces at mobile width, including the iOS device QA checklist and signoff next action. Keep privacy language calm and explicit, avoid exact coordinates, and make consent, evidence-source readiness, redaction, advisor export permission, and deletion/retention review easy to understand. Do not introduce real upload or signup flows.
- /https://www.dwellmark.io/
- /?tab=daycountshttps://www.dwellmark.io/?tab=daycounts
- /?tab=evidencehttps://www.dwellmark.io/?tab=evidence
- /?tab=evidence&filter=financialhttps://www.dwellmark.io/?tab=evidence&filter=financial
- /?tab=packethttps://www.dwellmark.io/?tab=packet
- /?tab=advisorhttps://www.dwellmark.io/?tab=advisor
- /?tab=packet&year=2025https://www.dwellmark.io/?tab=packet&year=2025
- /?tab=daycounts&persona=weak_evidencehttps://www.dwellmark.io/?tab=daycounts&persona=weak_evidence
- /?tab=advisor&persona=advisor_reviewhttps://www.dwellmark.io/?tab=advisor&persona=advisor_review
- /?tab=packet&persona=packet_readyhttps://www.dwellmark.io/?tab=packet&persona=packet_ready
- /?tab=advisor&persona=privacy_reviewhttps://www.dwellmark.io/?tab=advisor&persona=privacy_review
- /?tab=packet&persona=florida_domicilehttps://www.dwellmark.io/?tab=packet&persona=florida_domicile
- /?persona=act60_userhttps://www.dwellmark.io/?persona=act60_user
- /?persona=former_act60&year=2025https://www.dwellmark.io/?persona=former_act60&year=2025
- /?tab=evidence&persona=privacy_reviewhttps://www.dwellmark.io/?tab=evidence&persona=privacy_review
- /prototype/mobile-capture-centerhttps://www.dwellmark.io/prototype/mobile-capture-center
- /prototype/evidence-source-workbenchhttps://www.dwellmark.io/prototype/evidence-source-workbench
- /prototype/privacy-redaction-centerhttps://www.dwellmark.io/prototype/privacy-redaction-center
- /prototype/ledgerhttps://www.dwellmark.io/prototype/ledger
Make the packet builder, blocker list, integrity checks, and annual export history feel like a premium, trustworthy audit file workflow.
Redesign the audit packet workflow so the packet is clearly the hero object. Preserve seeded artifacts, export-readiness language, privacy choices, integrity checks, annual review, and advisor-compatible citations. Do not imply Dwellmark guarantees a tax or residency outcome.
- /https://www.dwellmark.io/
- /?tab=daycountshttps://www.dwellmark.io/?tab=daycounts
- /?tab=evidencehttps://www.dwellmark.io/?tab=evidence
- /?tab=evidence&filter=financialhttps://www.dwellmark.io/?tab=evidence&filter=financial
- /?tab=packethttps://www.dwellmark.io/?tab=packet
- /?tab=advisorhttps://www.dwellmark.io/?tab=advisor
- /?tab=packet&year=2025https://www.dwellmark.io/?tab=packet&year=2025
- /?tab=daycounts&persona=weak_evidencehttps://www.dwellmark.io/?tab=daycounts&persona=weak_evidence
- /?tab=advisor&persona=advisor_reviewhttps://www.dwellmark.io/?tab=advisor&persona=advisor_review
- /?tab=packet&persona=packet_readyhttps://www.dwellmark.io/?tab=packet&persona=packet_ready
- /?tab=advisor&persona=privacy_reviewhttps://www.dwellmark.io/?tab=advisor&persona=privacy_review
- /?tab=packet&persona=florida_domicilehttps://www.dwellmark.io/?tab=packet&persona=florida_domicile
- /?persona=act60_userhttps://www.dwellmark.io/?persona=act60_user
- /?persona=former_act60&year=2025https://www.dwellmark.io/?persona=former_act60&year=2025
- /?tab=evidence&persona=privacy_reviewhttps://www.dwellmark.io/?tab=evidence&persona=privacy_review
- /prototype/packet-builderhttps://www.dwellmark.io/prototype/packet-builder
- /prototype/packet-command-centerhttps://www.dwellmark.io/prototype/packet-command-center
- /prototype/packet-integrity-labhttps://www.dwellmark.io/prototype/packet-integrity-lab
- /prototype/annual-review-centerhttps://www.dwellmark.io/prototype/annual-review-center
UX Feedback Worksheet
Return findings in this structured format
Can a first-time owner understand that Dwellmark is for residency defense, evidence quality, and audit packet readiness within the first screen?
Can an advisor quickly see open issues, request evidence, comment on claims, and understand what blocks packet export?
Do mobile device QA, privacy, exact-location redaction, evidence-source consent, and advisor export controls feel explicit without becoming alarming?
Does the packet builder clearly communicate readiness, blockers, manifest sections, integrity checks, and export history as the hero workflow?
Does Act 60 read as one supported module inside a broader residency-defense product, not as the whole product identity?
Acceptance Checks
What must stay true during UX refinement
Every review screen opens from `/` with a stable hash URL and no auth redirect.
Clean, weak evidence, advisor review, packet ready, business exposure, Act 60, former Act 60, Florida domicile, privacy, and packet-builder states are selectable.
Owner, advisor, packet export, and business/privacy journeys each have a start screen, step sequence, and expected outcome.
Prototype content uses seeded data only and does not expose secrets, real evidence files, exact coordinates, or service-role values.
Residency defense is the category; Act 60 appears as one supported module rather than the product identity.
The visible review pack and `/api/design-handoff/demo` manifest expose the same personas, journeys, screens, review lanes, and boundaries.
Review Rubric
What to preserve, redesign, and avoid
Keep public prototype access, seeded data, URL-addressable personas, packet-first workflow language, and residency-defense positioning intact.
Improve hierarchy, density, grouping, mobile scanability, and review flow clarity without changing the underlying prototype state model.
Keep copy premium, calm, privacy-forward, and advisor-compatible while avoiding tax/legal advice or outcome guarantees.
Do not introduce login, billing, real storage uploads, exact-location display, or private-route assumptions during UX review.
Component Inventory
UI primitives to refine consistently
Readable ok, review, blocked, public, and ready states across dense operational panels.
Compact counts and percentages that show readiness without feeling like marketing tiles.
Repeated task, issue, evidence, claim, and packet cards that can be scanned and compared quickly.
Stable links that let design tools jump into screens, personas, API surfaces, and packet artifacts.
Dense day, evidence, risk, business, and packet review data that must stay readable on desktop and mobile.
Owner-controlled redaction, advisor permission, retention, and data-control UI that should feel explicit and calm.
Copy And Tone Matrix
Language to preserve and avoid during UX redesign
Lead with residency defense, day tracking, documentation, domicile ties, advisor review, and audit packets.
Dwellmark builds the residency defense file your CPA wishes you had kept all year.Make the audit packet feel like the central product object while keeping export readiness factual.
Export-ready means the seeded packet has resolved blockers, citations, integrity checks, and advisor-compatible sections.Connect weak days and proof gaps to concrete next evidence requests without sounding punitive.
This day needs stronger proof before it should support a packet claim.Keep privacy and device-QA language calm, explicit, and owner-controlled while avoiding exact-location exposure.
Exact location stays hidden by default; advisors see only the packet detail you explicitly approve.Make advisor actions clear while preserving the boundary that Dwellmark provides records and workflows, not legal advice.
Advisor review can request stronger evidence, comment on claims, and mark packet issues ready for owner review.Treat Act 60 as one supported residency module inside a broader domicile and day-count defense platform.
Act 60 is one residency track; Dwellmark also supports Florida domicile, former-resident files, and multi-state exposure.Design Review Intake Board
Open UX decisions to answer before design approval
Return a proposed desktop and mobile hierarchy for the owner command center that preserves packet readiness as a primary product object.
Final first-screen information architecture before auth and real-data flows are wired.
Annotated layout or written hierarchy with primary, secondary, and tertiary sections.Redesign the packet path so blockers, manifest sections, integrity checks, and export readiness are visible in one coherent workflow.
Packet-builder structure before production export, signed files, and advisor signoff are made real.
Packet workflow recommendation with blocker placement, artifact hierarchy, and export-state language.Return the preferred advisor review sequence and any copy/action labels needed for comments, requests, and claim decisions.
Advisor workflow order before permissioned advisor accounts are introduced.
Advisor journey notes with route order, action labels, and missing context.Review the mobile privacy and device-QA path and return copy/layout guidance for owner-controlled capture and redaction.
Small-screen trust language before real mobile capture and private storage are connected.
Mobile privacy and device-QA notes with copy changes, control grouping, and any responsive layout issues.Review track routing, domicile workflows, former-resident flows, Florida domicile, Act 60, and multi-state exposure as one coherent system.
Track naming and hierarchy before onboarding/auth asks users to choose a path.
Track-system recommendation with naming, order, and any missing scenario notes.Normalize repeated operational UI patterns so the prototype can be redesigned consistently across owner, advisor, packet, and privacy surfaces.
Reusable component guidance before UX changes are implemented across dozens of public prototype sections.
Component notes with state semantics, spacing rules, responsive behavior, and reuse guidance.Design Tool Launch Checklist
How to start Stitch, Claude, and human UX review
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.
Visual hierarchy and responsive layout recommendations for owner, advisor, packet, mobile privacy, iOS device QA, and track-breadth flows.
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.
Prioritized UX findings in the design review response template format.
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.
Decision notes for the intake board plus route-specific UX blockers.
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.
Current copy, recommended copy, reason, and preserved-boundary notes.
Return accepted design recommendations in implementation-ready shape. Include route, persona, viewport, severity, component impact, copy changes, preserved boundaries, and deferred production work.
Implementation queue suitable for engineering to apply without guessing.
Design Handoff Completion Audit
Ready, review, and deferred states before UX handoff
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.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.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.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.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.Demo States
Persona starting points
Strong day evidence and owner controls.
Weak evidence/prototype/persona/weak_evidencehttps://www.dwellmark.io/prototype/persona/weak_evidence/?persona=weak_evidence&tab=daycountshttps://www.dwellmark.io/?persona=weak_evidence&tab=daycountsLow-confidence days, adaptive proof prompts, and unresolved packet blockers.
Advisor review/prototype/persona/advisor_reviewhttps://www.dwellmark.io/prototype/persona/advisor_review/?persona=advisor_review&tab=advisorhttps://www.dwellmark.io/?persona=advisor_review&tab=advisorAccepted advisor access, issue notes, requests, and review gates.
Packet ready/prototype/persona/packet_readyhttps://www.dwellmark.io/prototype/persona/packet_ready/?persona=packet_ready&tab=packethttps://www.dwellmark.io/?persona=packet_ready&tab=packetEvidence, domicile, business, privacy, and audit checks prepared for export.
Business exposure/prototype/persona/business_exposurehttps://www.dwellmark.io/prototype/persona/business_exposure/?persona=business_exposurehttps://www.dwellmark.io/?persona=business_exposureFounder/operator business-presence events with evidence gaps.
Act 60 track/prototype/persona/act60_userhttps://www.dwellmark.io/prototype/persona/act60_user/?persona=act60_userhttps://www.dwellmark.io/?persona=act60_userPuerto Rico Act 60 readiness as one supported residency module.
Former Act 60/prototype/persona/former_act60https://www.dwellmark.io/prototype/persona/former_act60/?persona=former_act60&year=2025https://www.dwellmark.io/?persona=former_act60&year=2025Former Puerto Rico resident documenting a cleaner post-move file.
Florida domicile/prototype/persona/florida_domicilehttps://www.dwellmark.io/prototype/persona/florida_domicile/?persona=florida_domicile&tab=packethttps://www.dwellmark.io/?persona=florida_domicile&tab=packetFlorida move, domicile ties, northern-home exposure, and closer connection.
Privacy review/prototype/persona/privacy_reviewhttps://www.dwellmark.io/prototype/persona/privacy_review/?persona=privacy_review&tab=advisorhttps://www.dwellmark.io/?persona=privacy_review&tab=advisorOwner-controlled exact-location redaction, advisor export permission, and deletion review.
Packet builder/prototype/persona/packet_builderhttps://www.dwellmark.io/prototype/persona/packet_builder/?persona=packet_builder&tab=packethttps://www.dwellmark.io/?persona=packet_builder&tab=packetManifest sections, blockers, artifacts, integrity, and delivery state.
Priority Groups
Review these groups before visual polish
These screens define the first impression, evidence logic, packet hero object, and trust boundary.
These screens prove the advisor review loop and export workflow are coherent before auth.
These screens show that Dwellmark is broader than Act 60 while still supporting specialized modules.
These screens define capture, iOS device QA, source trust, household controls, validation, launch, and public API review.
Journey Scripts
Walk the core product paths
Owner can see risk, weak evidence, next proof requests, and packet impact in one pass.
- /prototype/design-handoff?persona=weak_evidencehttps://www.dwellmark.io/prototype/design-handoff?persona=weak_evidence
- /prototype/residency-intake-center?persona=weak_evidencehttps://www.dwellmark.io/prototype/residency-intake-center?persona=weak_evidence
- /prototype/ledger-review-center?persona=weak_evidencehttps://www.dwellmark.io/prototype/ledger-review-center?persona=weak_evidence
- /prototype/requests?persona=weak_evidencehttps://www.dwellmark.io/prototype/requests?persona=weak_evidence
- /prototype/packet-command-center?persona=weak_evidencehttps://www.dwellmark.io/prototype/packet-command-center?persona=weak_evidence
Advisor can identify open issues, ask for evidence, review claims, and understand export gates.
- /prototype/advisor-resolution-center?persona=advisor_reviewhttps://www.dwellmark.io/prototype/advisor-resolution-center?persona=advisor_review
- /prototype/claim-review-board?persona=advisor_reviewhttps://www.dwellmark.io/prototype/claim-review-board?persona=advisor_review
- /prototype/proof-strategy-planner?persona=advisor_reviewhttps://www.dwellmark.io/prototype/proof-strategy-planner?persona=advisor_review
- /prototype/residency-defense-brief?persona=advisor_reviewhttps://www.dwellmark.io/prototype/residency-defense-brief?persona=advisor_review
- /prototype/packet-builder?persona=advisor_reviewhttps://www.dwellmark.io/prototype/packet-builder?persona=advisor_review
Reviewer can follow manifest sections, privacy choices, integrity checks, and annual export history.
- /prototype/packet-builder?persona=packet_builderhttps://www.dwellmark.io/prototype/packet-builder?persona=packet_builder
- /prototype/packet-command-center?persona=packet_builderhttps://www.dwellmark.io/prototype/packet-command-center?persona=packet_builder
- /prototype/privacy-redaction-center?persona=packet_builderhttps://www.dwellmark.io/prototype/privacy-redaction-center?persona=packet_builder
- /prototype/packet-integrity-lab?persona=packet_builderhttps://www.dwellmark.io/prototype/packet-integrity-lab?persona=packet_builder
- /prototype/annual-review-center?persona=packet_builderhttps://www.dwellmark.io/prototype/annual-review-center?persona=packet_builder
Reviewer can separate owner/operator facts from personal domicile proof and redacted export controls.
- /prototype/business-presence-center?persona=business_exposurehttps://www.dwellmark.io/prototype/business-presence-center?persona=business_exposure
- /prototype/risk-center?persona=business_exposurehttps://www.dwellmark.io/prototype/risk-center?persona=business_exposure
- /prototype/record-conflict-resolution-center?persona=business_exposurehttps://www.dwellmark.io/prototype/record-conflict-resolution-center?persona=business_exposure
- /prototype/privacy-redaction-center?persona=business_exposurehttps://www.dwellmark.io/prototype/privacy-redaction-center?persona=business_exposure
- /prototype/launch-operations-center?persona=business_exposurehttps://www.dwellmark.io/prototype/launch-operations-center?persona=business_exposure
Screen Inventory
Stable public URLs for design tools
Owner dashboard, day counts, evidence confidence, packet readiness.
Design handoff/prototype/design-handoffhttps://www.dwellmark.io/prototype/design-handoff/https://www.dwellmark.io/Persona switcher, route map, review pack, and public handoff notes.
Residency intake center/prototype/residency-intake-centerhttps://www.dwellmark.io/prototype/residency-intake-center/https://www.dwellmark.io/Owner facts routed into residency defense workflows.
Residency track router/prototype/residency-track-routerhttps://www.dwellmark.io/prototype/residency-track-router/https://www.dwellmark.io/Track routing across domicile, Florida, former resident, Act 60, and multi-state exposure.
Proof strategy planner/prototype/proof-strategy-plannerhttps://www.dwellmark.io/prototype/proof-strategy-planner/?tab=evidencehttps://www.dwellmark.io/?tab=evidencePrioritized evidence sprints before auth.
Claim review board/prototype/claim-review-boardhttps://www.dwellmark.io/prototype/claim-review-board/?tab=advisorhttps://www.dwellmark.io/?tab=advisorPacket claims, counterfacts, advisor questions, and include/revise/exclude decisions.
Mobile capture center/prototype/mobile-capture-centerhttps://www.dwellmark.io/prototype/mobile-capture-center/?tab=evidence&persona=privacy_reviewhttps://www.dwellmark.io/?tab=evidence&persona=privacy_reviewPassive capture health, iOS device QA checklist, and iOS/Android release readiness.
Residency tracks/prototype/trackshttps://www.dwellmark.io/prototype/tracks/https://www.dwellmark.io/General domicile, Florida move, former resident, Act 60, multi-state exposure, and business presence.
Residency risk center/prototype/risk-centerhttps://www.dwellmark.io/prototype/risk-center/?tab=daycountshttps://www.dwellmark.io/?tab=daycountsJurisdiction lanes, alerts, day-count thresholds, and evidence-driven risk review.
Risk narrative review/prototype/risk-narrative-reviewhttps://www.dwellmark.io/prototype/risk-narrative-review/?tab=packethttps://www.dwellmark.io/?tab=packetPacket executive summary, jurisdiction claims, proof support, and advisor questions.
Record conflict resolution center/prototype/record-conflict-resolution-centerhttps://www.dwellmark.io/prototype/record-conflict-resolution-center/?tab=evidencehttps://www.dwellmark.io/?tab=evidenceReplay conflicts, affected seeded records, and resolution readiness.
Jurisdiction module workbench/prototype/jurisdiction-module-workbenchhttps://www.dwellmark.io/prototype/jurisdiction-module-workbench/prototype#operator-screenshttps://www.dwellmark.io/prototype#operator-screensModule maturity across residency tracks and launch priorities.
Documentation workplan/prototype/workplanhttps://www.dwellmark.io/prototype/workplan/?tab=evidencehttps://www.dwellmark.io/?tab=evidenceDay proof, domicile, advisor review, business, Act 60, and packet blocker triage.
Track drilldowns/prototype/track-drilldownshttps://www.dwellmark.io/prototype/track-drilldowns/?tab=packethttps://www.dwellmark.io/?tab=packetTrack-specific proof plans, open gaps, advisor lens, and packet sections.
Residency scenarios/prototype/scenarioshttps://www.dwellmark.io/prototype/scenarios/https://www.dwellmark.io/Common owner situations mapped to day-count impact and packet consequences.
Defense calendar/prototype/defense-calendarhttps://www.dwellmark.io/prototype/defense-calendar/?tab=daycountshttps://www.dwellmark.io/?tab=daycountsYear-round evidence capture, domicile proof, advisor review, and retention checkpoints.
Proof matrix/prototype/proof-matrixhttps://www.dwellmark.io/prototype/proof-matrix/?tab=evidencehttps://www.dwellmark.io/?tab=evidenceClaim-by-claim proof quality across residency, advisor, packet, and privacy surfaces.
Proof gap workbench/prototype/proof-gap-workbenchhttps://www.dwellmark.io/prototype/proof-gap-workbench/?tab=evidencehttps://www.dwellmark.io/?tab=evidencePrioritized gaps, blockers, and proof readiness before auth.
Defense chronology center/prototype/defense-chronology-centerhttps://www.dwellmark.io/prototype/defense-chronology-center/?tab=daycountshttps://www.dwellmark.io/?tab=daycountsOrdered residence, travel, evidence, advisor, and packet events.
Residency defense brief/prototype/residency-defense-briefhttps://www.dwellmark.io/prototype/residency-defense-brief/?tab=packethttps://www.dwellmark.io/?tab=packetAdvisor-compatible findings, proof support, blockers, and export-ready language.
Audit response room/prototype/audit-response-roomhttps://www.dwellmark.io/prototype/audit-response-room/?tab=packethttps://www.dwellmark.io/?tab=packetInquiry responses, packet citations, blockers, and draft readiness.
Chain of custody center/prototype/chain-of-custody-centerhttps://www.dwellmark.io/prototype/chain-of-custody-center/?tab=evidencehttps://www.dwellmark.io/?tab=evidenceEvidence custody, source records, verification, and packet traceability.
Ledger review center/prototype/ledger-review-centerhttps://www.dwellmark.io/prototype/ledger-review-center/?tab=daycounts&persona=weak_evidencehttps://www.dwellmark.io/?tab=daycounts&persona=weak_evidenceWeak days, corrections, and evidence-linked day review.
Domicile workbench/prototype/domicile-workbenchhttps://www.dwellmark.io/prototype/domicile-workbench/?tab=packet&persona=florida_domicilehttps://www.dwellmark.io/?tab=packet&persona=florida_domicileOrdinary-life ties, closer connection, home records, and advisor review.
Public Demo APIs