SofiCore
Log inGet started
SOFTWARE ENGINEERING INTELLIGENCE

See what’s built.
Know what
needs review.

Bring requirements, code, tests and CI into one workspace. Inspect the evidence behind delivery claims—and make the next release decision with clarity.

Explore the live case See core features
Source-linked findingsHuman acceptance stays explicit
SOFICORE / WORKSPACE
n.
Nano IDIndependent public repository study
OverviewRequirementsRelease review

Release evidence

Review required
—Evidence inventory
—Verified requirements
NANO-003Custom alphabet and size
Implementation awaiting dataTest records awaiting dataAcceptance pending
Captured sourceJavaScript
Loading the captured source…
Owner acceptance remains explicitInspect source and CI records before the review.
Captured revisionSource stays inspectable
REAL PROJECT DATA · CAPTURED NANO ID REVISION
ONE CONNECTED WORKFLOW
RequirementsSource & testsCI evidenceOwner review
Explore the platform
APPLIED TO A REAL REPOSITORYNano ID Independent study · captured 28 Oct 2026
requirements
—
captured files
—
named test declarations
—
recorded CI runs
—
THE PRODUCT, AT A GLANCE

Core features.

One place to connect what you planned, what the repository contains, and what still needs review.

Turn the plan into a reviewable map.

Bring requirements and acceptance criteria into the same view as the code. See the candidate implementation and tests behind each one.

  • Follow a requirement straight to source.
  • Keep acceptance review visible and explicit.
Explore requirement mappingPreviewed with the captured public case
Saved case analysis

Waiting for the saved analysis.

The product preview uses captured source records. You can also open the working workspace.

Open workspace

The details that keep review moving.

Included in the workflow

Requirement import

Bring your checklist into a connected workspace.

Dependency view

Trace connections between indexed files and imports.

Source permalinks

Inspect the exact revision behind an evidence match.

Exportable reports

Download the analysis with evidence and provenance.

AI & TECHNOLOGY

How the AI works.

Start with source evidence. Make the reasoning inspectable. Keep the final acceptance decision with a person.

Evidence mode comes first

Inspect the Azure model review record below. Live Copilot defaults to evidence retrieval; model explanation is an optional, separate setting.

RECORDED AZURE REVIEW

Loading the saved review record…

Reading the saved review status and any recorded response. This does not start a model request.

This recorded review is separate from the live workspace’s optional model setting. No completed result is assumed from configuration.

FROM REPOSITORY TO ANSWEROne captured revision
  1. 01 / INPUT

    Source at a
    pinned commit

    Read the supported files from one immutable revision.

    Code is read, never executed
  2. 02 / PARSE

    TypeScript
    source parser

    Extract symbols, imports and named test declarations.

    JavaScript + TypeScript
  3. 03 / MAP

    Requirements
    ↔ evidence

    Match criteria with candidate source and test records.

    Paths · lines · source snippets
  4. 04 / EXPLAIN

    Record retrieval,
    cited answer

    The assistant answers from the saved analysis records.

    Default · no model call
Human review is a separate gate.

Implementation, matching tests, confirmed criteria and passing CI for the same commit are all required for “verified.” The explanation mode cannot approve a requirement.

See the review rules
EXPLORE THE TWO EXPLANATION PATHS

The records supply the answer.

Deterministic retrieval uses the analysis already on record. It can locate requirement evidence, explain missing checks and return citations without calling a language model.

  • No language model call in the default path.
  • Source instructions are treated as untrusted data.
  • Interactive public Copilot uses this mode for every answer.

This switch explains the options; it does not enable a provider or send source.

A TRANSPARENT EVIDENCE SCORE

You can see what counts.

Coverage measures the presence of evidence. It does not estimate the probability that software is correct.

Implementation
40 points
Criteria mapped
20 points
Tests present
25 points
Exact-commit CI
15 points
100 points can coexist with zero reviewed requirements.
BUILT FOR YOUR REVIEW

Who is SofiCore for?

For the people who need to explain what the software does—and what still needs checking.

CHOOSE YOUR PERSPECTIVE

Different review perspectives. One evidence workflow.

FOR THE ENGINEERING LEADNANO ID · CAPTURED CASE

Before the release review.

Bring the delivery conversation back to inspectable evidence.

THE QUESTION YOU NEED TO ANSWER

“What still needs acceptance before we call this ready?”

A green CI result is one part of the decision. You also need to see the requirements, their supporting evidence, and the review still open.

  1. 01

    Open the release view

    Read the recorded CI result alongside the reasons that keep the project under review.

    Inspect evidence
  2. 02

    Inspect the supporting records

    Follow a requirement to its candidate implementation and named test declarations.

    Inspect evidence
  3. 03

    Keep acceptance with the reviewer

    The Nano ID checklist remains unreviewed. Passing recorded CI does not approve it.

    Review needed
TAKE INTO THE REVIEW

A release summary with evidence and unresolved review reasons.

Inspect the release evidenceTrace a requirement
HOW IT FITS

Your task tracker records the plan. CI records a run. SofiCore connects requirements to the captured evidence and review state. This MVP supports one owner and one repository; these are intended uses, not separate permission roles.

Explore the supported scope
RESULTS / NANO ID

Real results.
Open to inspection.

We applied SofiCore to a real public JavaScript repository. These findings come from one captured revision, with every review decision still visible.

—

Evidence inventory

Implementation, criteria mappings, named tests and recorded CI contribute to this score.

—verified requirements
—awaiting acceptance
The evidence is available. Review is still required.

This is a traceable review result. It is not a claim of defects in Nano ID or approval from its maintainers.

THE REVIEW REGISTERLoading captured results

Reading the saved requirement findings…

42 application checks passedRecorded 28 Oct 2026 · engine and server tests
See what was validated
LIVE CASE STUDY / TRY IT YOURSELF

Don’t take the summary
on trust. Open the evidence.

Select a documented behavior, inspect the source and tests, then verify the saved files. You’re using the same captured record as the full workspace.

Loading the captured evidence…

Preparing source links, requirement matches and the file receipt.

Independent public-source analysis. Criteria are derived from Nano ID’s README and remain unreviewed; the maintainers have not endorsed this study.

Read the full case study
GO DEEPER / NANO-003Follow one requirement, from documentation to review.

The trail becomes available when the captured case finishes loading.

YOUR NEXT PROJECT

Start with a project
that fits.

Explore the public workspace first. The MVP is designed for one owner reviewing one small JavaScript or TypeScript repository.

JavaScript & TypeScriptOne repository per workspace500 files · 128 KB each · 2 MB totalManual or Markdown requirements

Read-only analysis

Source is parsed as data. Imported code, scripts and dependencies are never executed.

Owner-scoped records

Saved workspace access is checked on the server. The owner controls active source records.

Explicit model choice

Default Copilot uses project records. Optional external model requests require configuration and consent.

What needs setup before I connect my own repository?

The repository adapter and owner workspace are implemented. Hosted account and deployed import acceptance are still pending; private access needs a registered GitHub App. AWS infrastructure is documented but not provisioned. The public case is available in this evaluation build.

View current configuration
Take the product tour Read the security and data boundaries
QUESTIONS, ANSWERED

Know what
you’re looking at.

Clear definitions make the evidence useful.

Explore the cases
How can coverage be 100% while nothing is verified?

Coverage measures the evidence inventory: candidate implementation, mapped criteria, test declarations, and recorded CI. Verification also requires explicit acceptance review. In the Nano ID snapshot, all seven requirements have evidence, and all seven still await that review.

Is Nano ID a customer or an endorsed case study?

No. This is SofiCore’s independent analysis of public open-source files at one immutable commit. SofiCore derived the checklist from the upstream README. The maintainers have not supplied or approved the checklist, findings, or release decision.

Were all 55 Nano ID tests run by SofiCore?

No. The analyzer found 55 active named test declarations in source. It does not execute the imported repository. Four successful GitHub Actions runs were separately recorded for the captured commit; they are linked in the case study.

Does refreshing the demo pull the latest GitHub code?

No. Reanalysis reads the saved snapshot and updates the analysis time. The source capture date and commit stay fixed. Observing a newer upstream revision requires a new import or capture; this MVP does not provide continuous synchronization.

What does the evidence verification button prove?

It compares the saved file contents with the SHA-256 hashes recorded in the receipt. A match proves consistency with that receipt. It does not establish human approval, upstream authenticity, CI execution, or production readiness.

Does Copilot send my source to an external AI model?

Default evidence mode does not. An operator can configure an optional model adapter; using it requires explicit opt-in and sends a bounded evidence packet. The public demo stays in evidence mode. Read the security and privacy pages for retention and provider boundaries.

Can I connect my production repository today?

The repository adapter and owner workspace are implemented, with setup documented in the source package. This preview has not completed hosted account and deployed repository-import acceptance. Private access also needs a registered GitHub App. Start with the public case and check Operational status before planning a deployment.

What does the Atlas example demonstrate?

Atlas Commerce is a separate, runnable training application with deliberately incomplete requirements. It helps demonstrate gaps and blocked review states. It is not a customer project, and its remote CI is unknown.

A CLEARER RELEASE CONVERSATION STARTS HERE

Bring one question.
Leave with the evidence.

Explore a real project. Follow a requirement. See what still needs review.

Open SofiCore Take the guided tour
No personal repository needed to explore the case