the evaluation ecosystem's log is authored events with one port per occurrence, read through the prefix

agent-decided, reversible. The concrete evaluation ecosystem of projects/deference/rounds/2026-09-09-evaluation-ecosystem-realization/ fixes the log shape: an append-only list of events carrying an authentic author, a kind, a payload, an optional warrant and references; occurrence identity is the ordinal of the mandate event; ports are occurrences, never renumbered; the protocol's history at prefix k is the index range and every protocol predicate reads the log prefix of that length; an answer receipt is a commit naming the occurrence under a key the log's warrant registry holds at the strict prefix, adequate there; a closure receipt is the engine's close on a settled sentence; the canonical account is the first valid resolving event's receipt. The one authentication assumption is the author field, stated once. Under this shape Integrity propagation is a function of the log (EvaluationEcosystem.propagate_segment_eq) and activation is a reading of it (activated_iff). Rejected alternatives: ports renumbered as occurrences resolve (dependent-type cost, no content); histories as arbitrary index lists read by membership (nothing the builder produces needs it); authentication modelled as signatures inside the log (re-imports the same assumption with more structure).