The CodeTwin ML workflow

How It Works

From a local repository to a searchable Software Digital Twin, evidence-backed findings, and user-approved fixes — see the workflow step by step.

Local-firstFour clear stepsEvidence before verification
  1. Illustrative CodeTwin ML interface showing local repository selection and a project overview
    Illustrative interface · not a live scan or verification result
    STEP 01

    Add your repository

    Start with a codebase on your own computer.

    Choose a local project folder. CodeTwin ML discovers supported languages and builds a persistent project index without running your application or uploading its source.

    • Select a local project folder
    • Track indexing coverage
    • Re-index only changed files
  2. Illustrative dependency graph linking a sample project to modules, symbols, dependencies, and change impact
    Illustrative interface · not a live scan or verification result
    STEP 02

    Build the Software Digital Twin

    Understand connections before making changes.

    CodeTwin links supported files, symbols, imports, and dependencies into a searchable digital twin. Explore relationships, change impact, and unresolved evidence rather than assuming every link is known.

    • Explore files and symbol relationships
    • Trace dependencies and impact
    • Keep source evidence connected
  3. Illustrative findings interface with security categories, source lines, and review evidence
    Illustrative interface · not a live scan or verification result
    STEP 03

    Analyze findings

    Find potential problems with the evidence behind them.

    Review code quality, static security, dependency, runtime, database, and QA findings. Each finding can carry source locations and traceable context; passive test discovery is not presented as a test pass.

    • Review findings by category
    • Inspect source-linked evidence
    • Distinguish confirmed and inconclusive results
  4. Illustrative patch review comparing proposed changes and a post-apply retest step
    Illustrative interface · not a live scan or verification result
    STEP 04

    Approve, fix, and verify

    Stay in control of every source-code change.

    Review an exact patch and approve it before CodeTwin writes files. Source hashes and backups protect the change, while post-apply indexing and retesting determine whether the issue is actually fixed.

    • Inspect and approve exact diffs
    • Preserve backups and rollback options
    • Verify through independent retesting