MYCO ENGINEERING ASSESSMENT · WORKING PROTOTYPE

Can a change pass every test and still be wrong?

Yes. A developer can satisfy the immediate ticket while breaking a caller, changing a business rule, or leaving critical behavior untested. Verity connects intent, implementation and executable evidence.

An independent engineering proposal by NANDAX. Explore NANDAX Publications and the developer's LinkedIn profile. Twelve controlled cases are in the private benchmark suite; the public preview shows one recorded case. Full-scale integrations are proposed for a custom pilot.

REVIEW SNAPSHOT MYCO-104
One requirement. Two contradictory signals.
✓
Existing test suiteThe current test misses the changed return type
PASSED
×
Checkout integrationNumeric caller receives a tuple instead
FAILED
THE QUESTION ISN'T “ARE TESTS GREEN?”What has actually been verified?
12Private tested case fixtures · 1 public
03Evidence-based diagrams
02Independent test suites per case
DESIGN PRINCIPLEFacts first. Reasoning second. Human judgment always.
01 / THE PROBLEM

Correctness has three sides.

Passing tests is only one observation. A trustworthy review also checks what the change was meant to do and what existing behavior it must preserve.

THE REASONING MODEL
INTENT / THE PROMISEStart with a concrete, testable requirement rather than guessing intended behavior from a code diff.See this in the workbench →
02 / THE METHOD

Six steps, one evidence trail.

From the original requirement to an auditable report. Select a step to see its information, tools and limitations.

INTERACTIVE PROCESS MAP
STAGE 01

Gather context

Collect the original requirements, code and tests.

OUTPUT ARTIFACT
03 / THE WORKING PROTOTYPE

Inspect the change. Challenge the tests.

Browse all twelve implemented benchmark cases. One is open with recorded evidence; eleven are private and offer a reviewer-access request on selection. The local Python edition executes trusted reference tests; this browser preview does not run Python or LLMs.

RECORDED RUN
ENGINEERING CASE CATALOGUE →
● 01 OPEN DEMO◆ 11 PRIVATE FIXTURES

Private cases are available for a guided evaluator review. Their original code, regression tests and reference corrections are not published here.

CASE 01 / 12

Return contract regression

A changed function disrupts checkout

Choose a case and select Analyze change.
NO ANALYSIS YET

Edits trigger fresh static analysis in local mode. Only bundled, byte-identical fixtures are executable.

BASELINE → CANDIDATE UNIFIED DIFF
REVIEWER'S QUESTION

What behavior changed beyond the original request?

04 / SYSTEM ARCHITECTURE

Follow the evidence, not the claim.

Explore the system architecture, the execution pipeline, and the links between requirements, changed code and tests. Every node has an explanation.

CLICKABLE SYSTEM MAPS
↓ four sources become one reviewable record
↓ two independent ways to review the facts
↓ validate citations; keep unanswered questions
NODE INSPECTORThe evidence pack

Select any node to examine its purpose and available evidence.

05 / RESPONSIBLE EXPANSION

A viable prototype. A credible path to scale.

The private prototype demonstrates controlled, executable tests. Scaling to a customer repository requires real integration and security work. Each phase below has an explicit acceptance gate.

FUTURE DEVELOPMENT
PHASE 01

Working assessment

06 / CUSTOM PROJECT ENGAGEMENT

From an assessment prototype to
your engineering workflow.

Verity is not a generic chatbot or a claim of a finished enterprise platform. The core is demonstrated on controlled Python cases. A custom Myco pilot would connect real repositories and requirements to that same evidence-first review process.

PROPOSED PILOT OUTCOMEA verifiable review of a real pull request.

One agreed repository, one clear requirement source, baseline CI evidence and independently checkable findings—with a documented false-positive review.

Discuss a custom pilot ↗

Capability map

Select any module to see what is built versus what needs custom project engineering.

PROTOTYPE BUILT

Evidence Core · Implemented

Python AST checks, benchmark fixtures and source-linked reports.

01 / DISCOVERAgree the pilot boundaryLanguages, data sources, security constraints and success measures
02 / INTEGRATEConnect one real workflowRead-only PR analysis, evidence ingestion and bounded AI options
03 / VALIDATEBenchmark against engineersGround truth, false positives, citation validity and review latency
04 / SCALEDecide with evidenceSecurity review, additional languages, CI gates and team rollout

Scope distinction: The public site contains a single recorded case. Twelve fixtures and the deterministic runner are in the separate private engineering build. GitHub/Jira integration, hosted LLM inference, secure execution of third-party code, multi-tenant SaaS and enterprise authentication are not deployed; they form the proposed custom-project work.

ENGINEERING PROPOSAL · NANDAX

Show the evidence.
Make the decision.

A serious review system is explicit about what was observed, what was inferred and what is still unknown.

PRIVATE EVALUATOR CASE · MYCO-219

The complete engineering case is available privately.

Private case

Controlled benchmark evidence and the implementation can be reviewed with NANDAX Engineering.

What a private review includesRequirement and original/changed source · independent executable regression tests · evidence and reference correction · technical discussion

This case exists in the private twelve-fixture assessment build. Public access is intentionally limited; no hidden scripts, test files or private source code are sent to this browser. Private access is arranged directly by NANDAX Engineering—not automatically granted by a vote.