docs/generated/vocabulary.mdgenerated from code

Reference · 5 min read

rule

Vocabulary: rule.

Which rule refused a request: the error's data.rule, present exactly when its code is rejected. Each rule has one recovery.

ValueMeaning
out_of_scopeNo grant the peer holds covers this path or operation.
grant_endedThe grant that covered the request has expired or was revoked.
quota_spentThe peer has used up the number of changes its grant allows.
protected_pathThe path is protected: a change to it reaches others only after checks pass and a holder of the approve capability approves it.
unattestedThe version the request names has not passed the project's checks yet.
policy_unknownThe project's rules for this path are not known yet on this daemon, because its grants have not synced.
not_syncedThe path is never shared: a control document under .lvcs/, a path the project never syncs (a .gitignore or .lvcsignore ignores it, or it is never-sync), a link or special file on the path, or a path outside every tree directory.
not_authorOnly the peer whose change is held may do this.
tree_file_authorThe tree directory writes as another peer, so this peer may not write through it.
not_a_repositoryNever answered by this release: the lvcs binary reads and writes no git repository (discussion:owner/456). It stays in the set because the JSON-RPC API is compatible from v0.1.0.
outcome_unknownAn earlier request with the same request id is still running or its answer was lost, so whether it applied is unknown. Read the document again and redo the change from what it holds now.
no_actionrun names no gated action: no approved [[actions]] entry in lvcs.toml with on = "manual" or on = { channel = ... } has that name (a change action runs on every change to main, never by run). Run an action the approved lvcs.toml gates, or add one and have its lvcs.toml change approved first.
not_eligibleThe frontier run names can't be run on by this action yet: its after channel doesn't hold it, and the action's channel holds no passed run of it; or no frontier was named and the after channel holds none, or several. Read the after channel to see which frontiers it holds, then wait for this one or name one it holds.
supersededThe frontier run names is behind the action's channel: the channel's value is a newer frontier that holds all of it, and the channel never passed a run of it, so running it would move the channel backward (discussion:owner/306). Read the channel and run the action on its value or a newer frontier; a rollback names a frontier the channel passed before.
git_rewriteNever answered by this release: LVCS maps no git branch ( discussion:owner/456). It stays in the set because the JSON-RPC API is compatible from v0.1.0.
action_refusedThe approval would put in force a set of actions that is refused: two declarations of one action, a GitHub workflow job LVCS can't run, or an lvcs.toml whose channel triggers name an unknown channel or form a cycle, which the reason names (reason names the action_refusal value). Fix the file, or list the job in lvcs.toml's [workflows] skip, as the reason says, and approve again.
stale_overlapA tree save or an edit was made from an older version of the file than the one it now holds, and the lines it changes overlap lines another peer changed since that version ( discussion:owner/296 and 310). It was not taken, and the file now holds the current version: read it again and redo the change from what it holds now. The reason names the overlapping lines and who changed them.
unproven_baseA tree save that no hook proved was read from a version of the file (a shell write, or an Edit whose read was lost) would replace or delete lines, and with no read proving which version its buffer held, that could revert a newer version, whoever wrote the lines (discussion:owner/732). It was not taken, and the file keeps its bytes, held back: make the change with the Edit tool after a Read, or land the bytes against main's heads (agentflare read --heads, then agentflare write --base).
not_durableNo document took a tree save while another save of the file was still out (discussion:owner/439), so its change was never committed, and the disk's bytes can't be saved again from a version no peer's change has moved past. The file keeps its bytes, held back: land them against main's heads (agentflare read --heads, then agentflare write --base).
device_scopeA paired device may not do this (discussion:owner/300): a read device only reads, a write device also coordinates (asks, answers, holds, says, runs gated actions), and no device edits files. Pair a device with the scope it needs (agentflare auth login --write), or do it from an agent or the CLI.
change_too_largeA save or an edit would make one change larger than CHANGE_MAX_BYTES (discussion:owner/611): no sync envelope could carry it, so it would never reach another node. It was not taken, and a tree save stays held. Ignore the file (.gitignore or .lvcsignore) if it is a build artifact, or split the edit.
purgedThe file's document was purged from the project by its owner (discussion:owner/614): every honest node dropped its content and refuses every read, sync, and restore of it. Nothing brings it back; name another file.
nodes_behindA connected node runs an lvcs release whose checks would refuse this change for good (discussion:owner/614): nothing was committed. Wait until every node the reason names runs the release it names, then ask again.
not_authorizedOnly the one process the op belongs to may ask it: a plugin's serve its keeper started, as the plugin's own key, says it is dormant (discussion:owner/790). Nothing changed; ask it from that process.

Cardinality: 24.