Skip to content

Rulvar API reference


Rulvar API reference / @rulvar/rulvar / lastRunSettle

Function: lastRunSettle()

ts
function lastRunSettle(entries): 
  | {
  acceptedArtifactRef?: number;
  citationAuditMeta?: Record<string, unknown>;
  claimConsistencyMeta?: Record<string, unknown>;
  completion?: "partial" | "rejected" | "complete";
  deliverableAccepted?: boolean;
  outputHash?: string;
  rejectedFinishCandidates?: RejectedFinishCandidate[];
  resultAvailable?: boolean;
  runStatus: RunStatus;
  semanticTerminalVerdict?: Record<string, unknown>;
  seq: number;
}
  | undefined;

Defined in: packages/core/dist/index.d.ts

The last journaled run settle of a journal, if any. outputHash is present when that settle recorded the result digest (RV-209; settles written before it, or over undefined/non-serializable results, carry none).

Parameters

ParameterType
entriesreadonly JournalEntry[]

Returns

Type Literal

ts
{
  acceptedArtifactRef?: number;
  citationAuditMeta?: Record<string, unknown>;
  claimConsistencyMeta?: Record<string, unknown>;
  completion?: "partial" | "rejected" | "complete";
  deliverableAccepted?: boolean;
  outputHash?: string;
  rejectedFinishCandidates?: RejectedFinishCandidate[];
  resultAvailable?: boolean;
  runStatus: RunStatus;
  semanticTerminalVerdict?: Record<string, unknown>;
  seq: number;
}
NameTypeDescriptionDefined in
acceptedArtifactRef?number-packages/core/dist/index.d.ts
citationAuditMeta?Record&lt;string, unknown&gt;The citation audit meta and the one-word semantic verdict the settle recorded (RV4403), read back the same defensive way: the seventh comparison run's restart reader could not see the ten unsupported citations its own failure named. Absence means NOT RECORDED, never a verdict.packages/core/dist/index.d.ts
claimConsistencyMeta?Record&lt;string, unknown&gt;-packages/core/dist/index.d.ts
completion?"partial" | "rejected" | "complete"-packages/core/dist/index.d.ts
deliverableAccepted?booleanThe semantic outcome the settle recorded (RV3304), read back the same defensive way: the acceptance verdict, the deliverable presence, the acceptance ref and the judge meta, so a restarted reader recovers the facts a live consumer gated on. Absent on journals written before the lift carried them; absence means NOT RECORDED, never a verdict.packages/core/dist/index.d.ts
outputHash?string-packages/core/dist/index.d.ts
rejectedFinishCandidates?RejectedFinishCandidate[]The rejected finish candidates the settle recorded (RV2507), read back for offline readers (RV2605). The settle persists the whole completion lift, so this needs no re-fold and no validator re-run; it is parsed defensively, exactly like completion, so a foreign or older journal reads as "not recorded" rather than as a claim.packages/core/dist/index.d.ts
resultAvailable?boolean-packages/core/dist/index.d.ts
runStatusRunStatus-packages/core/dist/index.d.ts
semanticTerminalVerdict?Record&lt;string, unknown&gt;-packages/core/dist/index.d.ts
seqnumber-packages/core/dist/index.d.ts

undefined