Expand description
VCS backend abstraction and Lore VCS type system.
Lore — a centralized VCS with global revision numbers, file-level metadata, dependency graphs, and style branching.
The VcsBackend trait is the low-level seam between NAP and any VCS.
LoreBackend is the only production
implementation. Higher-level workflows (context docs, permissions) live in [RepoService].
§Architecture
Consumer code → RepoService (stable boundary)
│
▼
VcsBackend trait
│
LoreBackend (adapter)
│
LoreProcessRunner (CLI executor)
│
loreserver (authoritative store)Structs§
- Commit
Info - Metadata about a single VCS commit, returned by
log(). Kept for backward compatibility with existing callers. - Context
Document - A contextual document tracked in the Lore VCS with associated metadata and dependency edges for AI context-graph assembly.
- Permission
- A directory- or file-level access-control entry.
- Repository
- A Lore repository identity — analogous to a remote, but with a workspace-scoped multi-tenant owner.
- Revision
- A single revision (commit) in the Lore VCS.
- Workspace
- A local working copy of a Lore repository.
Enums§
- Access
Level - Access level for a permission entry.
- Workspace
Mode - How a workspace tracks state locally.
Traits§
- VcsBackend
- Low-level abstraction over a version control system.