Documentationv1.4.0

Security & Privacy Standards

Architectural security guarantees built specifically for enterprise repositories.

Zero-LLM, Deterministic Guarantee

gitresolve strictly does NOT use Large Language Models (LLMs), probabilistic neural networks, or external AI APIs. Conflict resolution is performed entirely locally through Abstract Syntax Tree (AST) grammar checks, deterministic type unification, and formal policy rules.

100% OfflineZero Data LeakageBit-Identical Reproducibility

Enterprise Hardening Mechanisms

Every operation follows defence-in-depth isolation principles.

CWE-22 Rooted Path Sandboxing

Mandatory os.Root directory confinement guarantees that all file reading and resolution writes are mathematically restricted within the repository boundaries, preventing path traversal exploits (CVE / CWE-22 mitigation).

POSIX Atomic File Writes

All auto-resolutions are written first to isolated temporary staging buffers and flushed with fsync() before an atomic os.Rename(). A sudden system crash or kernel panic will never leave files half-written or corrupted.

Post-Write Syntax Verification Gate

No auto-resolved code file is ever finalized on disk unless it passes native language compiler AST verification (Go syntax, JSON/YAML parser). If syntax fails, changes roll back immediately to manual review.

Immutable SQLite Audit Ledger

Every decision made by the engine is recorded with timestamp, commit hashes, matched rules, and confidence metrics in .gitresolve/audit.db in WAL mode for forensic auditability.