HOW IT WORKS

From Repository to Release Gate

EVRSYN Trace connects to your codebase and generates a complete, living traceability chain. Every file is classified, every artifact is linked, and every change keeps the chain in sync.

THE PIPELINE

01

Connect Repository

OAuth handshake with GitHub, GitLab, or Bitbucket. Tokens are encrypted at rest. EVRSYN fetches your file tree, metadata, and branch structure — read-only access only.

  • OAuth 2.0 token exchange
  • File tree sync
  • Branch detection
  • Scope path configuration
02

Classify Source Code

Over 20 classifier rules analyze every file in your repository. Each file is categorized by its architectural role — API route, database model, authentication gate, UI page, service layer, CLI command, and more.

  • api_route — Express, FastAPI, Django, Gin handlers
  • db_model — Prisma, SQLAlchemy, ActiveRecord models
  • auth_gate — Middleware, guards, permission checks
  • ui_page — React pages, Vue components, templates
03

Generate Artifacts via Agent Swarms

Classified elements are dispatched to coordinated AI agent swarms for artifact generation. Each agent specializes in a chain segment — requirements extraction, objective derivation, or success criteria synthesis. The swarm architecture is model-agnostic: plug in Anthropic Agent SDK, OpenAI, local LLMs, or any provider.

  • REQ agent — Extracts SHALL statements from code semantics
  • OBJ agent — Derives verification objectives from requirements
  • SC agent — Synthesizes binary pass/fail conditions
  • EC agent — Aggregates exit criteria from module SCs
  • Quality gate — Validates agent output before persistence
04

Validate Chain Integrity

Every artifact must be linked. Every requirement must have at least one objective. Every objective must have at least one success criterion. Orphaned artifacts are flagged and reported.

  • REQ → OBJ linkage validation
  • OBJ → SC linkage validation
  • Orphan detection and reporting
  • Chain completeness scoring
05

Publish TRACE Documents

Per-module Markdown traceability documents are generated and stored. Each document contains the full chain for that module — requirements, objectives, success criteria, and exit criteria.

  • One TRACE doc per module
  • Full chain per document
  • Version-controlled artifacts
  • Export-ready for compliance audits
06

Monitor & Delta Regen

Every push to your repository triggers delta analysis. Changed files are mapped to impacted modules, and only the affected artifacts are regenerated. Your traceability chain is always current.

  • GitHub webhook integration
  • Diff-based impact analysis
  • Incremental regeneration
  • Change tracking with ArtifactChange records

AGENT ARCHITECTURE

Powered by agent swarms. Bring any model.

EVRSYN Trace doesn't lock you into a single AI provider. The generation engine is built on a model-agnostic agent swarm architecture — orchestrated specialists that collaborate to produce, validate, and refine every artifact in your traceability chain.

PROVIDER.01

Anthropic Agent SDK

First-class integration with Claude via the Anthropic Agent SDK. Multi-turn reasoning, tool use, and structured output for high-fidelity artifact generation.

PROVIDER.02

Local Swarms

Run generation entirely on-premise with local LLMs — Llama, Mistral, Qwen, or any GGUF-compatible model. Your code never leaves your infrastructure.

PROVIDER.03

Any Top Model

OpenAI, Google Gemini, Cohere, or any OpenAI-compatible API. Swap providers per pipeline stage — use the best model for each task.

HOW THE SWARM WORKS

Orchestrated Specialists

Each pipeline stage dispatches work to specialized agents. A classifier agent categorizes source files. A requirements agent extracts SHALL statements. A verification agent derives objectives. A criteria agent synthesizes pass/fail conditions. A quality gate agent validates the entire chain before persistence.

  • Parallel execution — agents work concurrently across modules
  • Cost guard — automatic fallback to rule-based when AI isn't needed
  • Quality gate — rejects low-confidence outputs, re-prompts or falls back
  • Deterministic scaffolding — AI enhances, rules guarantee structure

Model-Agnostic by Design

The agent layer abstracts the model provider behind a unified interface. Configure per-stage: use Claude for nuanced requirements extraction, a local model for high-volume classification, and GPT-4 for test case generation. Mix and match based on cost, latency, and quality requirements.

# pipeline.config

classify:  local/llama-3.3-70b

generate:  anthropic/claude-sonnet

validate:  anthropic/claude-opus

enhance:  openai/gpt-4o

fallback:  rules-only

Anthropic Agent SDKOpenAIGoogle GeminiLlamaMistralQwenOllamavLLM

If it serves tokens, we orchestrate it.

ARTIFACT TYPES

Four artifact types. One unbreakable chain.

REQ

Requirement

REQ-BE-AUTH-001

A statement of what the system SHALL do. Generated from route handlers, database models, authentication gates, and UI pages.

EXAMPLE

The system SHALL authenticate users via OAuth 2.0 and return a valid JWT upon successful login.

GENERATED FROM

Route handlers, models, auth gates

OBJ

Objective

OBJ-BE-AUTH-001

A verification intent for a requirement. Defines what needs to be tested to confirm the requirement is met.

EXAMPLE

Verify that OAuth token exchange succeeds and returns a valid, signed JWT with correct claims.

GENERATED FROM

Derived from parent REQ

SC

Success Criterion

SC-BE-AUTH-001

A binary pass/fail condition. Defines exactly what must be true for the objective to be considered verified.

EXAMPLE

POST /api/v1/auth/login with valid OAuth code returns 200 with { token: JWT, expiresIn: 3600 }.

GENERATED FROM

Derived from parent OBJ

EC

Exit Criterion

EC-SYS-RELEASE-001

A release gating rule. Defines what percentage of success criteria must pass before a release can proceed.

EXAMPLE

100% of authentication success criteria pass before release gate opens.

GENERATED FROM

Aggregated from module SCs

CHAIN RELATIONSHIPS

Every link is bidirectional

Navigate from any requirement to its verification objectives, success criteria, test cases, test runs, and defect reports. Navigate back from any defect to the requirement it violates.

REQ
OBJ
SC
TC
Test Run
DR
EC

The infrastructure that keeps $1B projects on track — now for every team.

We'll never share your email. Unsubscribe anytime.