Struct Store 

pub struct Store { /* private fields */ }

Synthesist / lattice adapter over a project’s claims/ directory.

Writes go through Store::append; reads go through Store::query. Every append syncs the view before returning so follow-up reads see the write.

Implementations

impl Store

pub fn discover() -> Result<Self>

Open (or initialize) a Store.

Resolution order:

1. SYNTHESIST_DIR env var (set by --data-dir in the CLI, or exported directly). Points at the directory CONTAINING claims/. An explicit override that doesn’t resolve to an existing store is a hard error — silent fallback would mask misconfiguration (e.g. a typo yielding an empty estate).
2. Parent-directory walk from cwd. Opens the first ancestor containing claims/genesis.amc.
3. If none, initialize a fresh store at cwd/claims/ (unless a v1 .synth/main.db is in scope, in which case we refuse and name the migrator).

pub fn discover_from(start: &Path) -> Result<Self>

Like Self::discover but starts from a given path.

Walk-up order:

1. Any ancestor with a claims/genesis.amc → open it.
2. Otherwise, if any ancestor has a v1 .synth/main.db, bail with a prescriptive migration error. Silently creating an empty v2 estate alongside legacy data orphans the user’s work; we refuse.
3. Otherwise, initialize a fresh v2 estate at start/claims/.

pub fn open_at(claims_dir: &Path) -> Result<Self>

Open at an explicit claims/ directory. The directory must already contain a genesis.amc.

pub fn init_at(claims_dir: &Path) -> Result<Self>

Initialize a fresh Store at claims_dir.

pub fn discover_for(session: &Option<String>) -> Result<Self>

Discover and scope the asserter with an optional session id.

When a session id is given, subsequent appends assert as user:local:<user>:<session> — giving us attribution without cryptographic identity (see IDENTITY.md for the v0.2 roadmap).

pub fn with_asserter(self, asserted_by: impl Into<String>) -> Self

Override the asserter prefix. Reserved for tests and for future callers that set asserter from a parsed Session claim (e.g. beacon sync, rather than $USER).

pub fn append( &mut self, claim_type: ClaimType, props: Value, supersedes: Option<ClaimId>, ) -> Result<ClaimId>

Append a typed claim and synchronize the SQLite view.

Both the workflow layer and the substrate are type-agnostic for validation purposes since claim 0.2.0 / workflow 0.2.0: per-type schema validation is the consumer’s responsibility, applied at its API boundary (typically a CLI or library entrypoint) BEFORE calling this method. Consumers compose nomograph_claim::validation helpers with their own per-type validators; see synthesist::schema for a worked example. This method assumes the caller has already validated props for the given claim_type.

pub fn query(&self, sql: &str, params: &[&dyn ToSql]) -> Result<Vec<Value>>

Run a read-only SQL query over the SQLite view.

pub fn root(&self) -> &Path

The claims/ directory backing this store.

pub fn sync_view(&mut self) -> Result<()>

Force a view rebuild. Most callers don’t need this; append syncs automatically.

pub fn inner(&mut self) -> &mut ClaimStore

Access the underlying claim store (for session handles, compact, merge). Most callers should not need this.