DICE API Documentation/com.embabel.dice.spi/RetiredProposition

RetiredProposition

data class RetiredProposition constructor(val propositionId: String, val priorStatus: PropositionStatus, val foldedGrounding: List<String> = emptyList(), val foldedProvenanceRefs: List<String> = emptyList(), val foldedSourceIds: List<String> = emptyList(), val foldedProvenanceEvidenceKeys: List<String> = emptyList())

One proposition that was folded into a survivor, and what a merging sweep would carry over from it (grounding, provenance and source ids) so the fold can be undone.

Constructors

RetiredProposition

constructor(propositionId: String, priorStatus: PropositionStatus, foldedGrounding: List<String> = emptyList(), foldedProvenanceRefs: List<String> = emptyList(), foldedSourceIds: List<String> = emptyList(), foldedProvenanceEvidenceKeys: List<String> = emptyList())

Properties

foldedGrounding

val foldedGrounding: List<String>

foldedProvenanceEvidenceKeys

val foldedProvenanceEvidenceKeys: List<String>

One evidence key per entry the fold actually added, minted by ProvenanceEvidenceKey. This is what undo subtracts, and it is what makes an undo of revisioned evidence exact. Empty on traces recorded before this field existed. Kept out of JSON, so a trace serialized and read back undoes at locator granularity — JSON is not a round trip for a trace you intend to undo from.

foldedProvenanceRefs

val foldedProvenanceRefs: List<String>

Locator keys for the sources this proposition brought that the survivor was not already citing. A locator key names a source, not a version of it, so this list can be empty while foldedProvenanceEvidenceKeys is not — a loser carrying r2 of a document the survivor already cites at r1 adds no new source. Trace readers display these, and undo falls back to them when a trace predates evidence keys.

foldedSourceIds

val foldedSourceIds: List<String>

priorStatus

val priorStatus: PropositionStatus

propositionId

val propositionId: String