Audit-oriented research infrastructure

A research workflow you can reconstruct.

Nexus Scholar Core is a local-first .NET foundation for protocols, evidence, human decisions, workflow execution, provenance, and verifiable review outputs. It is designed so a result never has to stand apart from the history that produced it.

See what is implemented Run the local workflow Explore the modules

FE-01–FE-07completed local authority stack

FE-08 · 1–4completed desktop slices

906 testsrecorded at Slice 4 closeout

The product promise

Keep the review workflow honest—even when automation helps.

Nexus is not another chat interface over PDFs. Its job is to preserve the evidence, authority, decisions, and invalidation rules beneath research work.

For researchers

Know what happened

Import local evidence, resolve duplicate candidates, inspect screening authority, and export records whose identity can be checked later.

For supervisors and labs

Inspect the decision trail

Trace a review from approved protocol through snapshots, human decisions, full-text evidence, reporting, and portable bundles.

For developers

Integrate without redefining authority

Use inward-facing domain contracts, explicit application boundaries, canonical records, and verification-first adapters.

One coherent local stack

From protocol intent to independently checkable output

Protocol
approved conduct and authority

Workflow
compiled DAG and execution journal

Evidence
imports, snapshots, full text

Decisions
identified humans and conflicts

Output
reports and verifiable bundles

Authority boundary Automation, plugins, and model output may eventually propose or transform. They do not approve protocols or finalize scientific decisions.

Current protected-main baseline

Real local conduct, with narrow claims

23validation-only packages in the accepted topology

Localdurable workspaces without a database or cloud authority layer

Humanpolicy-bound authority for admitted scientific decisions

Digestcontent identity for authoritative and evidentiary records

Read the dated implementation status Understand what remains

Start at your altitude

Evaluate the idea, run the software, or inspect the contracts

The public narrative and developer reference are intentionally separate. Product pages explain why the system exists; module guides explain exactly where the authority and dependency boundaries live.