Skip to main content
TERMINAL-NATIVE REPOSITORY REASONING • MIT OPEN SOURCE

Intelligence for
safer software.

Octate combines repository-aware analysis, deterministic checks, and evidence-backed AI reasoning to help engineering teams understand software changes with genuine confidence.

• Analyze clearly • Validate deeply • Ship confidently
octate-kernel-v1 — valence_reaction_pipeline.svg
LIVE REACTION | 8 NODES INTERCEPTED
$ npx octate review --staged --deep-ast
Tree-sitter AST Graph • Evidence-Backed

A diff is not a codebase.

Most AI code review systems inspect only the isolated lines changed in a pull request. But real vulnerabilities, contract violations, and state regressions rarely exist in the diff alone—they explode outward into uncalled callers, corrupted invariants, and implicit dependencies.

01

Hidden AI-Generated Risk

LLMs write convincing syntactical code that subtly violates domain security policies, session lifecycles, and multi-tenant isolation boundaries.

> Syntactic elegance ≠ Semantic safety
02

Static Analysis Noise

Traditional linters and heuristic scanners flood developers with hundreds of low-priority warnings, burying high-consequence defects under alert fatigue.

> 80%+ irrelevant noise ignored
03

Unverified AI Guesses

Generic review bots hallucinate nonexistent APIs or comment on styling trivia. Developers need cryptographic proof and concrete code trajectories.

> Proof required, not prose
04

Defect vs. Safe Code

Review systems must deterministically distinguish intentional pattern shifts from critical authentication bypasses and race conditions.

> Deterministic risk gating
Context Expansion Engine

From raw lines changed to surrounding architectural invariants

git diff → AST Graph Resolution → Evidence Envelope
INPUT: LOCAL GIT SCOPE
@@ -182,3 +182,5 @@
- return session.isActive()
+ return session.tokenStatus
// 1 line change in auth/session.ts

Shallow AI models stop here, guessing intent without caller context.

OCTATE REPOSITORY REVEAL
Callers mapped 14 upstream services
Symbol resolution Tree-sitter strict AST
Adversarial gate Falsification check

Discovers that downstream worker pools assume revoked tokens throw exceptions.

OUTCOME: VERIFIED FINDING
CRITICAL: Auth Bypass Trajectory

Proves silent fallback in middleware.ts:72 allows unauthenticated request flow.

SARIF 2.1.0 output ready for developer terminal or CI gate.

The Octate Review Pipeline.

A deterministic multi-stage sequence engineered to eliminate hallucinations, suppress frivolous noise, and isolate verifiable security defects.

01

Repository

Git diff scope, uncommitted staged buffers, or commit range indexing.

Tree-sitter WASM
02

Analysis

Symbol table resolution, caller-callee propagation, AST tokenization.

In-Memory Graph
03

Context

Builds the minimal sufficient evidence envelope without dumping whole repos.

Relevance Bound
04

AI Review

Specialized reviewers evaluate structural, semantic, and security paths in parallel.

3x Fan-out DAG
05

The Critic

Adversarially falsifies drafted assertions; drops unprovable findings.

Falsification Check
06

Risk Gate

Deterministic thresholding separates blocking defects from notes.

CI Exit Status
07

Actionable Proof

Direct line numbers, call stack evidence, and remediation patch paths.

SARIF 2.1.0 JSON

Understands the codebase first. Reasons second.

The model provider is replaceable. Repository intelligence, context windowing, and adversarial critique are the product.

Tree-sitter WASM TypeScript 5.x SARIF Compliant

Architected for high-signal security.

Octate replaces probabilistic guesses with deterministic repo-aware evidence. Every capability is designed to integrate cleanly into modern engineering workflows.

<01>

AI-Assisted Code Review

Designed to understand subtle business logic regressions, silent state mutations, and concurrency vulnerabilities that escape typical linters.

<02>

Context-Aware Analysis

Traverses the full import hierarchy, abstract syntax trees, and interface contracts to evaluate changes within true runtime relationships.

<03>

Evidence-Backed Findings

Every critical alert comes attached with exact source code references, call site proofs, and logical falsification arguments.

<04>

False-Positive Reduction

An internal Adversarial Critic actively attempts to refute drafted issues before they ever notify developers, suppressing spurious noise.

<05>

Risk-Based Decision Gates

Categorizes issues by deterministic impact, enabling clean non-zero CI exit codes strictly when high-confidence security invariants break.

<06>

GitHub & PR Integration

Seamlessly surfaces review summaries, inline diff annotations, and SARIF upload pipelines directly within native GitHub pull requests.

<07>

Auditability & Traceability

Export structured JSON logs capturing every reviewer thesis, symbol lookup trajectory, and verification step for internal compliance audits.

<08>

Review Status Transparency

Provides complete clarity into completed, advisory, rejected, and incomplete evaluations with zero opaque black-box verdicts.

AI proposes. Evidence verifies.
Octate decides.

We never accept an AI review assertion that cannot demonstrate its exact code trajectory. Every finding must survive rigorous adversarial falsification.

Step 01

Model Candidates

Specialized AI models draft potential risks across structural, semantic, and security domains.

Unverified Drafts
Step 02

Independent Evidence

AST symbol links, imported schemas, and caller chains are assembled as verifiable proof bounds.

Deterministic AST
Adversarial Filter
Step 03

The Critic Review

An adversarial agent attempts to disprove the issue using existing repository invariants and tests.

Hallucination Dropped
Step 04

Deterministic Validation

Verifies whether proposed code trajectories can actually be triggered in production execution.

Reachability Test
Step 05

Risk Classification

Final verified finding emitted with jump-to-definition evidence and confidence metrics.

SARIF / CI Pass or Block
Our Honest Engineering Commitment: Octate is built to drastically reduce review noise and false alarms. We do not claim zero false positives or perfect universal detection. Software verification is a collaborative discipline where transparent evidence supports human developer agency.

Pull Request Intelligence Interface

Simulated Octate PR Review • Pull #418
PR #418 feat(auth): migrate distributed session token revocation to redis cache
1 Blocking Issue 2 Advisory
Changed files (4): src/auth/session.ts src/auth/middleware.ts src/config/redis.ts
CRITICAL: ACTION REQUIRED STATUS: REJECTED FROM MERGE
CRITICAL

Unbounded Token Invalidation Race

Confidence: 96% • Verified via AST Reachability
Target: src/auth/session.ts:184 (Impacts 14 downstream API gateway routes)
What is wrong?

The updated rotateKey() handler marks the previous token status as REVOKED asynchronously without a transactional lock, leaving an unmitigated 140ms window where revoked tokens are accepted by worker cache.

Why does it matter?

Replay attacks against payment authorization can reuse compromised bearer tokens during token rotation bursts, breaking the zero-trust invariants mandated by PCI-DSS requirement 6.5.10.

Verified Trajectory Proof 3 multi-file references mapped
142 auth-orchestrator.ts await cache.set('token:' + id, raw, { TTL: 300 });
143 auth-orchestrator.ts void this.ledger.markInvalid(previousId); // CRITICAL: unawaited background task
088 payment-worker.ts const valid = await cache.get('token:' + id); // Consumes stale key

Your code stays yours. Full boundary control.

Octate operates as a local-first analysis tool. We do not clone your entire repository into remote cloud databases or train foundation models on private intellectual property.

Local Runtime Boundary

On-Machine Static Extraction

All index building, Tree-sitter AST syntax parsing, graph construction, symbol matching, and source parsing happen strictly on the executing CPU container. Your source code files never leave your environment during local phases.

  • ✓ Local Git working tree & buffer parsing
  • ✓ Tree-sitter AST symbol trees stay in local memory
  • ✓ Zero remote indexing of uncommitted files
Minimal Envelope Perimeter

Zero-Retention Context Engine

When deep reasoning is requested, only the minimal extracted context envelope is transmitted to selected inference endpoints. We support Bring Your Own API Key (BYOK) and strictly enforce zero-retention data agreements.

  • ✓ BYOK support: NVIDIA Nemotron, OpenAI, or local vLLM
  • ✓ Strict zero-retention training policy guarantees
  • ✓ Ephemeral, sanitized context windows only

A measured path to safer software

We build incrementally from grounded facts. Each layer expands intelligence and reach only after the foundational verification layer proves reliable in production codebases.

Phase 01 Released / Stable

Terminal-Native Review

octate review

Deterministic repository discovery, Tree-sitter WASM parsing, Context Engine, Nemotron DAG, two-stage critic, interactive TUI, SARIF v2.1.0 and JSON outputs.

Phase 02 In Development

Repository Intelligence

octate index • octate ask • octate explain

Persistent repository knowledge graph. Conversational codebase understanding, impact analysis for anticipated refactors, and symbol dependency exploration.

Phase 03 Planned

Continuous Analysis

octate scan

Background daemon watching filesystem changes. Real-time architectural rule enforcement and early detection of drift before commit time.

Phase 04 Planned

Controlled Remediation

octate fix <finding-id>

Deterministic patch generation with local test validation. Human-in-the-loop review and approval before any change touches the working tree.

Phase 05 Future Vision

Governed Agentic Engineering

octate govern

Safe, bounded agentic workflows with strict cryptographic policy boundaries, audit logging, and human sovereignty over automated execution.

Build with confidence.

Bring evidence-driven intelligence to every code review. Stop reviewing blind diffs and start validating software with cryptographic certainty.

$ npx octate review
TypeScript 5.x • Tree-sitter • Node.js LTS • MIT License