Deep Git Integration
NeoArc wraps Git with architecture-first concepts: checkpoints instead of commits, tracks instead of branches, baselines instead of tags. Semantic diff, conflict resolution, drift analytics, and shelving provide a complete governance workflow.
NeoArc Studio does not just store files in Git. It wraps Git with architecture-first concepts that make version control meaningful for architects. Every Git operation is translated into architectural language, and every change is analysed for its structural significance rather than treated as a line-level diff.
Architecture-First Terminology
NeoArc replaces Git jargon with terms that make sense for architecture teams:
| NeoArc Term | Git Concept | Description |
|---|---|---|
| Checkpoint | Commit | A saved snapshot of architectural work |
| Track | Branch | A parallel line of architectural evolution |
| Baseline | File-based snapshot | Named, immutable reference point with integrity hashing |
| Shelved Work | Stash | Temporarily set aside in-progress changes |
| Reconcile | Merge | Combine changes from different tracks |
| Sync | Push/Pull | Synchronise with remote repository |
Key Capabilities
Git Command Transparency
Every operation logs the equivalent Git CLI command. Architects see exactly what ran, building trust and enabling troubleshooting without leaving the application.
Workspace Scoping
All analytics and operations are automatically scoped to the current workspace directory. This enables monorepo support where multiple architecture projects live in a single repository.
Learn More
NeoArc analyses changes as architectural decisions, not line-level diffs. Every change is classified as structural or cosmetic, giving architects a meaningful view of what actually matters.
File-based baselines provide defence-grade reproducibility with SHA-256 integrity hashing. Unlike Git tags, baselines survive squash merges and rebases, go through PR review, and work in air-gapped environments.
When merge conflicts occur, NeoArc presents them as architectural choices rather than raw JSON diffs. A three-way merge GUI with Accept Yours and Accept Theirs buttons makes conflict resolution meaningful.
Monitor how far your architecture has drifted from a governance-approved baseline. Visual gauges, hotspot detection, change frequency heatmaps, and a chronological change feed give architects full visibility into architectural evolution.
Temporarily set aside in-progress architectural changes without creating a checkpoint. Shelved work can be listed, restored, and deleted, enabling clean context switching between tasks.