Protected-main walkthrough

Validate the repository, inspect a local workspace, and open the desktop host

This path demonstrates current software boundaries using generated local fixtures. It does not create a publishable systematic review, contact providers, retrieve papers, or authorize scientific conduct for you.

1. Prerequisites

Windows, Linux, or macOS for the .NET repository and CLI.
The exact .NET SDK pinned by global.json.
Git and PowerShell 7 or Bash.
Windows for the current product-desktop validation target.

Baseline used by this tutorial Protected main at 805f3d6, where FE-01 through FE-07 and FE-08 slices 1–4 are complete.

2. Clone and bootstrap

git clone https://github.com/nexus-scholar-org/core-csharp.git
cd core-csharp
git switch main
git pull --ff-only origin main
pwsh ./scripts/bootstrap.ps1

On Bash, use bash scripts/bootstrap.sh. The bootstrap checks prerequisites and restores repository-local tools without turning the project into a globally installed product.

3. Verify before exploring

dotnet restore NexusScholar.Core.slnx
dotnet build NexusScholar.Core.slnx -c Release --no-restore
dotnet test NexusScholar.Core.slnx -c Release --no-build
dotnet format NexusScholar.Core.slnx --verify-no-changes --no-restore

For the repository-wide release baseline, run:

powershell -ExecutionPolicy Bypass -File ./scripts/verify.ps1

The full verifier adds release policy, locked restore, reproducible package builds, clean local-source package smoke, SBOM and release evidence, CLI smoke, and formatting checks.

4. Run the deterministic CLI smoke paths

dotnet run --project src/NexusScholar.Cli -- doctor
dotnet run --project src/NexusScholar.Cli -- sample
dotnet run --project src/NexusScholar.Cli -- demo

doctor reports the runtime and the human-authority policy reminder.
sample walks approved Protocol → compiled Workflow → Provenance → Bundle verification.
demo exercises deterministic local Search-import and Deduplication evidence from embedded sample bytes.

Demo output is not scientific authority The smoke commands prove code paths and contract behavior. They do not prove that a real review is complete, valid, or methodologically adequate.

5. Create a disposable Research Workspace

The repository includes generated fixture exports for onboarding. They resemble common export shapes but are not real Scopus, Web of Science, or Google Scholar evidence.

New-Item -ItemType Directory -Force .nexus-demo/workspace | Out-Null
Push-Location .nexus-demo/workspace

dotnet run --project ../../src/NexusScholar.Cli -- init --title "Nexus local demo"
dotnet run --project ../../src/NexusScholar.Cli -- import search ../../tests/NexusScholar.AppServices.Tests/Fixtures/App01GeneratedLocalBundles/bundles/FB07-combined-app01-demo/combined_scopus_like.csv --source scopus --format csv --query-id search-001 --query "systematic review screening software"
dotnet run --project ../../src/NexusScholar.Cli -- verify
dotnet run --project ../../src/NexusScholar.Cli -- analyze
dotnet run --project ../../src/NexusScholar.Cli -- status
dotnet run --project ../../src/NexusScholar.Cli -- review
dotnet run --project ../../src/NexusScholar.Cli -- clusters review

Pop-Location

This onboarding path produces inspectable Search and Deduplication projections. It does not manufacture the verified FE-01 authority package required to commit a deduplication decision.

6. Understand the command families

Family	Purpose	Authority posture
`init`, `import search`, `verify`, `analyze`	Local workspace and evidence operations.	Operational writes and projections; not final scientific decisions.
`review`, `clusters …`	Inspect deduplication evidence and review targets.	Read-only.
`dedup decide`	Preview and optionally commit an admitted FE-02 action.	Requires verified policy, actor/role assignment, exact authority generation, and explicit `--confirm`.
`screening status`	Inspect persisted Screening conduct artifacts when present.	Integrity status; does not invent or approve conduct.
`report verify`, `bundle verify`, `export verify/status`	Reopen and verify persisted FE-06 outputs.	Verification only.

Preview is not permission Supplying --actor or --role text does not grant authority. The command checks those values against the exact verified local policy and fails closed when the workspace cannot prove them.

7. Launch the FE-08 product desktop

The product host is distinct from the older sample renderer and read-only preview. It reaches local workspace behavior through NexusScholar.Desktop.AppServices and uses preview/confirm boundaries for admitted writes.

dotnet run --project src/NexusScholar.Desktop/NexusScholar.Desktop.csproj -c Release -- ".nexus-demo/workspace"

On the protected baseline, the desktop can:

open and verify a local workspace;
preview and confirm initialization, local Search import, and analysis;
display a verified deduplication authority queue and commit an authorized human decision after exact-effect confirmation;
report whether the durable title/abstract Screening authority package is ready after restart.

Most simple demo workspaces will show scientific decision paths as unavailable because they do not contain the verified authority chain. That is expected fail-closed behavior.

8. What to inspect

Can you distinguish evidence, a proposal, a preview, and an authoritative decision?
Does every failure explain what authority or evidence is missing?
Are file paths shown as local references rather than scientific identities?
Does confirmation expose the exact effects before a local mutation?
Can you find the record, digest, actor, and policy that justify a state?

9. Report useful feedback

Include the commit, operating system, SDK version, exact command or screen, expected behavior, actual behavior, and whether any local workspace files were produced.