STATIC ANALYSIS + CLOSED-SET ROUTING

AST-aware governance

Understand what a code change affects, why it needs review, and what to check before merging.

1
Map the change
Read the diff and supplied symbol index to connect functions to callers.
2
Apply fixed rules
Check sensitive paths, public interfaces and related test updates first.
3
Classify uncertainty
Jev selects a fixed label. Low confidence goes to a human.
4
Review the evidence
Use the recommendation and linked hunks. No merge or test is executed.

Proposed change

Start with the seeded auth change or paste your own diff. “Analyze changes” runs local static checks; “Classify with Jev” sends only the relevant structured context.

What does “AST-aware” mean here?

An abstract syntax tree represents code as named structures such as functions, parameters and imports. This prototype uses a lightweight parser plus your manifest, not a full compiler or a live repository checkout.

The manifest lists known symbols (named code units), callers (code that uses them), and test mappings. Missing information stays unknown; the app does not discover your whole repository.

Demo story: createUser gains organizationId. The registration caller is updated, the invitation job is unchanged, and no tests are updated. Expect human review.

PR titleUnified diff

diff --git a/src/auth/service.ts b/src/auth/service.ts
--- a/src/auth/service.ts
+++ b/src/auth/service.ts
@@ -1,3 +1,3 @@
-export function createUser(email: string, password: string) {
-  return { email };
+export function createUser(email: string, password: string, organizationId: string) {
+  return { email, organizationId };
 }
diff --git a/src/routes/register.ts b/src/routes/register.ts
--- a/src/routes/register.ts
+++ b/src/routes/register.ts
@@ -1,3 +1,3 @@
-export function registerUser(email: string, password: string) {
-  return createUser(email, password);
+export function registerUser(email: string, password: string, organizationId: string) {
+  return createUser(email, password, organizationId);
 }

Description & repo policy

PR descriptionRepo policy JSON

[]

Optional array of rules with id, kind, paths, description. Built-in safety rules always apply.

Codebase manifest / symbol index

Manifest JSON

{
  "complete": true,
  "environmentHash": "demo-toolchain-v1",
  "symbols": [
    {
      "id": "src/auth/service.ts#createUser",
      "filePath": "src/auth/service.ts",
      "kind": "function",
      "name": "createUser",
      "parameters": [
        "email",
        "password"
      ],
      "calls": [],
      "exported": true,
      "hash": "mock-create-user-v1"
    },
    {
      "id": "src/routes/register.ts#registerUser",
      "filePath": "src/routes/register.ts",
      "kind": "function",
      "name": "registerUser",
      "parameters": [
        "email",
        "password"
      ],
      "calls": [
        "src/auth/service.ts#createUser"
      ],
      "exported": true,
      "hash": "mock-register-v1"
    },
    {
      "id": "src/jobs/invite.ts#inviteUser",
      "filePath": "src/jobs/invite.ts",
      "kind": "function",
      "name": "inviteUser",
      "parameters": [
        "email",
        "password"
      ],
      "calls": [
        "src/auth/service.ts#createUser"
      ],
      "exported": true,
      "hash": "mock-invite-v1"
    }
  ],
  "tests": [
    {
      "filePath": "tests/auth.test.ts",
      "symbolIds": [
        "src/auth/service.ts#createUser"
      ]
    },
    {
      "filePath": "tests/invite.test.ts",
      "symbolIds": [
        "src/jobs/invite.ts#inviteUser"
      ]
    }
  ]
}

Optional symbols, calls, hashes and test mappings. Missing context requires review.

Try Run mock demo for a complete walkthrough without API calls.

Minimum confidence

Both the selected-label probability and confidence must meet this threshold. A higher score never overrides a policy finding.

Governance decision

Follow the change through the codebase

Analyze a diff to see symbols, callers, activated policy and test scope.