Desktop

Product-host boundary

NexusScholar.Desktop owns process startup, the main window, file and folder pickers, the operator view model, rendering, and explicit confirmation interactions. It owns no scientific rule and references no Core domain package or ResearchWorkspace directly.

The host reaches local behavior exclusively through NexusScholar.Desktop.AppServices. UI selection, focus, row order, labels, and local paths never become scientific identity.

The desktop may invoke an accepted, authority-checked application command. The desktop itself does not grant authority: FE-02 policy assignment authorizes the named human actor and role.

Current researcher workflows

• Open an existing local workspace, including an optional startup path.
• Initialize a selected folder after reviewing exact local effects.
• Import one user-selected Scopus, Web of Science, Google Scholar, OpenAlex, Semantic Scholar, or Other export in CSV, RIS, or BibTeX format.
• Verify local inputs and surface parser warnings, skipped records, and attention states.
• Analyze imported evidence after previewing publication of a new local generation.
• Load an authority-aware FE-02 review queue; choose an exact target, policy action/reason, actor, role, rationale, and superseded decision; inspect effects; then explicitly confirm.
• Run title/abstract Screening review, correction, adjudication, and terminal handoff against the exact durable authority package.
• Attach candidate-local Full Text bytes, preserve extraction evidence, and conduct human full-text review.
• Generate deterministic reports, exact-inventory Bundle v2 output, and append-only export-ledger records with round-trip verification.

Every scientific mutation remains actor-, policy-, evidence-, protocol-, criteria-, generation-, and expected-state-bound. The host exposes accepted FE-08 workflows; it does not author Protocols/criteria, operate providers, or invent authority when a required package is absent.

Implementation map

Program / App
    |
    v
MainWindow  ---- file/folder pickers, three-column shell
    |
    v
DesktopWorkspaceViewModel
    |
    v
Desktop command and workflow facades
    |
    v
verified ResearchWorkspace operations

• MainWindow builds the navigation, workspace, status, and effect-inspector regions in Avalonia controls.
• DesktopWorkspaceViewModel owns transient operator state, one pending preview, current overview, and review queue.
• App applies the version-aligned Fluent theme and opens the classic desktop lifetime.

Confirmation and failure experience

Every admitted write first fills the right-side effect inspector with exact effects and a confirmation token. Confirm submits that immutable preview; cancel clears it without mutation. Scientific actions retain actor and role plus the exact snapshot, criteria, policy, journal, artifact, report, or export bindings required by that workflow.

Status color distinguishes failed, stale, recovery-required, and attention states from success. The view model updates overview or queue only when the facade returns a structured result; it does not infer success from a completed event handler.

Dependencies and customization

The host references Avalonia, Avalonia.Desktop, Avalonia Fluent theme, Avalonia Blocks, Desktop.AppServices, and UiContracts. Core projects do not reference it. New controls should stay presentation-only and invoke typed facade operations; domain reconstruction, filesystem transactions, and policy checks do not belong in the host.

The current shell is programmatic C# UI. Accessibility certification, cross-platform qualification, durable layout/settings, navigation completion, installer behavior, and updater behavior are not yet established.

Tests and release evidence

Desktop tests cover view-model state, confirmation, deduplication, Screening, Full Text, reporting/export routing, and reusable-control safety. Native Windows visual QA covers the three-column shell and explicit automation names for critical review actions.

See Slices 1–2 evidence, Slice 3 evidence, Slice 4 evidence, and Slices 5–9 closeout.

Run and nonclaims

dotnet run --project src/NexusScholar.Desktop/NexusScholar.Desktop.csproj -c Release

No installer, updater, deployment, accessibility certification, authentication, identity provider, multi-user collaboration, provider/network acquisition, AI, plugin runtime, database/API/cloud, telemetry, crash upload, PHP compatibility, or production-security claim is made.