EAL-Bench epistemic report

Type: agentic-system-analyses/types/agentic-system-epistemic-report.md

Source-and-claim boundary

The question is whether EAL-Bench produces, checks and licenses authorization claims, and how those claims or evaluation results affect later behavior. Scope and exclusions are see boundary; evidence identity and layers are see Source register. All new inspection uses SRC-1 at that revision. No target execution, supplied execution trace or causal experiment establishes operation here. Implementation deductions below are not observed results.

The benchmark's authorization domain is a fictional case history and its encoded ledger, not an organization's actual permissions. Its public evaluation claim is EPI-CLM-benchmark-test; its narrower attribution contract is RT-CLM-memory-attribution. The intended evaluation role does not require a general knowledge-production loop. Conversely, a writer's accepted status cannot be promoted into evidence-consuming semantic acceptance merely because evaluation software exists elsewhere.

Coverage distinguishes direct reads in this job from supplied runtime findings. Uninspected relevant operations prevent a system-complete negative about semantic checks, maintenance or feedback.

Entry point or operation Source path in SRC-1 Coverage and records, or limit
Main study dispatch, writer formation, checkpoints and executor calls experiments/run.py; experiments/authorization_memory/study_engine.py Supplied RT-RTE-study-execution; direct dispatch search and direct read of prepare_execution confirm reviewer/builder and finalizer hooks. Arbitrary registered callbacks are not all audited.
Existing-profile proposal, structural repair, admission and rejection experiments/authorization_memory/langmem_writer.py Supplied RT-RTE-writer-admission; no new semantic oracle inferred.
Full-history, memory and empty-evidence executor modes, domain-native tools and scorer experiments/authorization_memory/pipeline.py; domains/procurement/adapter.py Supplied RT-RTE-executor-score and RT-BAP-memory-evidence. Cybersecurity/Finance semantic internals not directly audited here; no claim of independent oracle correctness.
Saved checkpoints and replay experiments/authorization_memory/resume.py Supplied RT-RTE-checkpoint-resume; hashes license reuse of bytes, not endorsement.
Best-of-k reviewer and gold-fidelity selection domains/procurement/studies/writer_ttc.py Supplied RT-RTE-candidate-selection; model ranking and gold ranking remain distinct.
Source-authority mitigation experiments/mitigations/source_authority/gate.py Direct core read plus supplied RT-RTE-authority-gate; diagnostic predicate does not test entailment.
Event extraction and lifecycle reduction experiments/mitigations/event_sourcing/core.py Supplied RT-RTE-event-admission; full runner/recovery not audited.
Extension aliases and feedback experiments/extension_cli.py; experiments/closed_loop.py Direct complete alias dispatch read; closed_loop and writer_variants are forwarded to separate drivers. Feedback covered by supplied RT-RTE-closed-feedback; writer-variant internals not independently audited.
Public preservation and formation assessment src/eal_bench/eval/preservation.py Direct annotation resolution, score_memory, apparent_authority and status helper reads; EPI-RTE-memory-assessment.
Saved free-text annotation experiments/annotate_authorization_memories.py; domains/procurement/studies/annotations.py Direct request, parse, result construction and child-run persistence/sample reads; EPI-RTE-annotation-extraction, EPI-RTE-annotation-admission. Other domains' annotation paths uninspected.
Matched propagation and end-to-end attribution src/eal_bench/eval/propagation.py; src/eal_bench/eval/end_to_end.py Direct variant-widening, plan and per-request attribution reads; EPI-RTE-variant-construction, EPI-RTE-failure-attribution. Aggregate uncertainty implementation not independently audited.
Public CLI and registered Inspect adapter src/eal_bench/eval/__main__.py; pyproject.toml; src/eal_bench/eval/inspect_adapter.py Direct complete CLI and packaging reads confirm resource/export CLI and Inspect registration; adapter/scorer behavior supplied by RT-RTE-alternate-consumers. Export serialization internals uninspected.
Generic handler loop and auxiliary judge src/eal_bench/llm/client.py; judge.py Supplied handler-loop finding RT-RTE-alternate-consumers; direct complete judge read. Judge extracts option labels; no inspected connection makes it an authorization oracle.
Historical analyses, diagnostics and shipped domain maintenance analysis/; results/; domains/ Not independently audited here. Primary archives unavailable per boundary; diagnostic artifact provenance and maintenance routes remain unassessed. Prevents reproducing published findings or a whole-system absence of further acceptance/criticism routes.

Missing primary trial/memory/context archives prevent rescoring original results and reconstructing bootstrap inputs. Missing model weights and provider internals prevent assessment of parameter-state epistemic content or provider-internal learning. Available but unread registered studies, domain maintenance, aggregate analysis and diagnostic artifacts prevent exhaustive negative conclusions; they are not access gaps. See RT-CMP-writer-model, RT-CMP-executor-model and RT-CMP-reviewer-model for distinct distributed-parametric limits.

Epistemic-object inventory

Object ID Candidate truth-apt content or none Claimed role Evidence source ID and local anchor Gap/limit
EPI-OBJ-case-ledger Whether a case request is authorized at a checkpoint see record see record Benchmark reference truth, not external organizational truth
EPI-OBJ-typed-memory Current grants, scope, lifecycle and provenance see record see record Symbolic validation/assessment and model-interpreted executor consumption have different force
EPI-OBJ-text-memory Prose assertions of current authorization, where individuable see record see record Particular generated propositions not determinable without candidate instances; unannotated prose is not deterministically scored
EPI-OBJ-annotation-state Extracted interpretation of what a prose memory says see record see record Schema acceptance and inter-annotation agreement do not prove extraction fidelity
EPI-OBJ-evaluation-results Field errors, false-authority formation and matched attribution predicates see record see record Local predicates, not evidence of general mechanism or transfer
RT-OBJ-executor-plan Identity/hash facts; no new authorization grant see record see record Recovery relevance only; no semantic endorsement
RT-CMP-writer-model, RT-CMP-executor-model, RT-CMP-reviewer-model, EPI-CMP-annotation-model Internal truth-apt content not determinable see records see records Accessible inference interfaces do not individuate propositions in weights

Authority-route ledger

Fields owned by a shared record are cited rather than copied. Rows split functions of the same implementation; separate local rows need not declare duplicate route identities. All statuses below describe inspected implementation, including implementation supplied through runtime records, not observed operation.

Route ID Route function Architectural status Object/candidate ID Content/update relation Transition or check target Evaluator/condition and domain Activation and timing Possible or observed result Implemented force Epistemic authority and scope Operational authority: behavior permitted, blocked, or changed Behavioral-authority path: consumer, channel, force, horizon Evidence source ID and local anchor Claim IDs or none Mismatch marker or none Gap/limit
RT-RTE-writer-admission, proposal content transformation implemented EPI-OBJ-typed-memory, EPI-OBJ-text-memory truth-apt transformation: indeterminate see route see route see route see route Candidate generation No semantic license established by inference alone Proposes replacement profile see RT-BAP-profile-update see route EPI-CLM-benchmark-test none Compression may preserve, omit or alter permissions; a specific non-entailing output requires an instance
RT-RTE-writer-admission, validation check/evidence production implemented EPI-OBJ-typed-memory, EPI-OBJ-text-memory no content change see route see route see route see route Structural check Payload shape, visible identifiers and configured capacity only Supplies admission decision, not semantic certification see route see route none accepted is protocol acceptance Visible citation can still support a wrong grant
RT-RTE-writer-admission, disposition disposition/acceptance implemented EPI-OBJ-typed-memory, EPI-OBJ-text-memory no content change see route see route see route see route Enforcing candidate admission/rejection No evidence-consuming semantic acceptance established Accept changed profile, distinguish unchanged, or retain prior accepted profile after rejection see route see route none Protocol admission is not knowledge acceptance First failed update may have no prior accepted profile; see EPI-RTE-memory-assessment
RT-RTE-writer-admission, persistence retention implemented EPI-OBJ-typed-memory, EPI-OBJ-text-memory no content change see route see route see route see route Persisted state made reusable Retention adds no warrant Seeds later updates and supplies frozen evidence see RT-BAP-profile-update, RT-BAP-memory-evidence see route none none Retention is not lifecycle integration after semantic acceptance
RT-RTE-executor-score, evidence consumption operational admission/selection/consumption implemented EPI-OBJ-typed-memory, EPI-OBJ-text-memory no content change see route see route see route see route Model-interpreted evidence No programmatic authorization license from the memory Can influence generated terminal action see RT-BAP-memory-evidence see route EPI-CLM-benchmark-test none Delivery is not compliance or activated influence
RT-RTE-executor-score, scoring check/evidence production implemented EPI-OBJ-case-ledger, EPI-OBJ-evaluation-results truth-apt transformation: entailed derivation see route see route see route see route Deterministic local measurement Validity and action/authorization classification under encoded semantics Returns scored trial; does not veto a real transaction see route see route EPI-CLM-benchmark-test Action means benchmark decision here Source truth and deployed enforcement outside license
EPI-RTE-annotation-extraction content transformation implemented EPI-OBJ-text-memory, EPI-OBJ-annotation-state truth-apt transformation: indeterminate see route see route see route see route Interpretation proposal No established semantic equivalence Supplies candidate annotation see route see route none none Exact extraction versus changed meaning requires output/source comparison
EPI-RTE-annotation-admission, check check/evidence production implemented EPI-OBJ-annotation-state no content change see route see route see route see route Structural/hash/agreement check Identity and consistency only Controls estimability see route see route none none Agreement can preserve a shared wrong interpretation
EPI-RTE-annotation-admission, disposition disposition/acceptance implemented EPI-OBJ-annotation-state no content change see route see route see route see route Enforcing score admission No semantic acceptance established Allows annotation-backed scoring, or returns unscored reason see route see route none Annotation accepted is not gold truth Optional human sample creation is not a completed human review
EPI-RTE-memory-assessment check/evidence production implemented EPI-OBJ-typed-memory, EPI-OBJ-annotation-state, EPI-OBJ-case-ledger truth-apt transformation: entailed derivation see route see route see route see route Diagnostic; ranking in separate oracle-selection path Relative to case oracle and fidelity encoding Reports errors/formation, not automatic writer correction see route see route EPI-CLM-benchmark-test none Encoding and annotation adequacy remain assumptions
RT-RTE-candidate-selection operational admission/selection/consumption implemented EPI-OBJ-typed-memory, EPI-OBJ-text-memory no content change see route see route see route see route Ranking then enforced whole-candidate choice Live model selection adds no verified warrant; gold mode licenses relative minimum field error Selected memory reaches executor see route see route none Minimum error is not necessarily zero error No edit/merge; selection quality unobserved
RT-RTE-authority-gate, predicate check/evidence production implemented EPI-OBJ-typed-memory no content change see route see route see route see route Fixed every-citation predicate Visible authority-capable source metadata only Supplies per-record pass/fail see route SRC-1 experiments/mitigations/source_authority/gate.py; see route none none Entailment, scope and lifecycle not checked
RT-RTE-authority-gate, filter disposition/acceptance implemented EPI-OBJ-typed-memory truth-apt transformation: non-ampliative reshaping see route see route see route see route Enforcing removal Passing source-capability criterion, not semantic authorization Removes failed records before mitigation replay; original arm remains see route SRC-1 experiments/mitigations/source_authority/gate.py; see route none none No automatic global withdrawal of other saved copies
RT-RTE-event-admission, extraction content transformation implemented EPI-OBJ-typed-memory truth-apt transformation: indeterminate see route see route see route see route Proposed lifecycle delta Structural acceptance cannot warrant extracted meaning Supplies event candidate see route see route none none Concrete extraction correctness unobserved
RT-RTE-event-admission, reduction content transformation implemented EPI-OBJ-typed-memory truth-apt transformation: entailed derivation see route see route see route see route Fixed reducer rules Consequences of supplied events under reducer semantics Changes compact current state see route see route none none Derivation from an unwarranted event does not warrant source authorization
RT-RTE-event-admission, validation check/evidence production implemented EPI-OBJ-typed-memory no content change see route see route see route see route Structural constraint checking Parsed delta, references, targets and capacity only Checks clone before candidate return see route see route none none Not semantic entailment
RT-RTE-event-admission, disposition disposition/acceptance implemented EPI-OBJ-typed-memory no content change see route see route see route see route Atomic candidate acceptance/rejection No semantic acceptance established Failure does not commit candidate reducer see route see route none none Full runner recovery beyond supplied inspection
EPI-RTE-variant-construction content transformation implemented EPI-OBJ-typed-memory truth-apt transformation: ampliative conjecture see route see route see route see route Controlled experimental alteration No license to trust altered permission; intentionally constructs a contrast Selects erroneous memory for diagnostic replay see route see route EPI-CLM-benchmark-test Deliberate mutation is not endogenous writer failure This classification concerns widening, not all variant recipes
EPI-RTE-failure-attribution check/evidence production implemented EPI-OBJ-evaluation-results truth-apt transformation: entailed derivation see route see route see route see route Enforced label criterion Three-part matched predicate under supplied rows Includes or withholds attribution and records reasons see route see route RT-CLM-memory-attribution none Predicate satisfaction is not independent causal identification
RT-RTE-closed-feedback, outcome rendering content transformation implemented EPI-OBJ-evaluation-results truth-apt transformation: acquisition/import see route see route see route see route Local outcome text for writer Preserves benchmark-decision origin; real-world outcome warrant absent Supplies action/outcome or neutral update see route see route none none Input explicitly synthesized from benchmark trials
RT-RTE-closed-feedback, feedback update behavior/policy adaptation implemented EPI-OBJ-typed-memory, EPI-OBJ-text-memory truth-apt transformation: indeterminate see route see route see route see route Model-mediated state revision plus structural admission No new gold authorization license Revised memory can condition later requests see route see route none Feedback is not proven improvement Neutral arm and rejection/seed retention are countercases to inevitable reinforcement
RT-RTE-checkpoint-resume lineage/freshness/recovery implemented RT-OBJ-executor-plan no content change see route see route see route see route Enforced local compatibility Byte/identity compatibility, not truth Allows missing executor calls, rejects incompatible checkpoint see route see route none none Reviewer-backed resume rejected; no universal exactly-once guarantee
RT-RTE-alternate-consumers, public/Inspect check/evidence production implemented EPI-OBJ-evaluation-results truth-apt transformation: entailed derivation see route see route see route see route Scoring Local oracle classification only Returns measurement rather than invoking domain tools see route see route EPI-CLM-benchmark-test none Inspect model configuration remains external
RT-RTE-alternate-consumers, generic handlers operational admission/selection/consumption implemented No benchmark authorization object required no content change see route see route see route see route Python handler dispatch No benchmark semantic license Can invoke host-granted effects and return results into next model turn see route see route none Bypasses benchmark scorer Host authority and handler correctness uninspected

No lifecycle-integration row is inferred from persistence. The inspected baseline writer, annotation parser and event validator do not establish evidence-consuming semantic acceptance followed by integration. This is a local route assessment, not a system-wide evidenced absence over unread maintenance and study paths.

For a concrete implementation deduction, give the cited-source gate an empty citation tuple: decisions is empty and the result is missing_provenance; the caller does not append the record to retained. A single visible authority-capable citation passes regardless of the remembered scope because this predicate never reads scope content. Thus removal is operative, but survival does not entail authorization correctness (SRC-1 experiments/mitigations/source_authority/gate.py; RT-RTE-authority-gate). No execution is needed for this bounded deduction.

System-claim versus route comparison

Claim ID Claimed operation or warrant Claim source ID/anchor and evidence layer Doctrine/design support Implemented route IDs Observed-run support Causal support and design limits Supported conclusion Mismatch/unknown
EPI-CLM-benchmark-test see record see record see record RT-RTE-writer-admission, RT-RTE-executor-score, EPI-RTE-memory-assessment, EPI-RTE-variant-construction Not established in this job Written versus exact memory is a bounded contrast; altered variants cannot establish writer production; independent component effects require independent variation Implementation affords testing preservation and downstream decision sensitivity Not proof of published rates, live transactions or deployed safety
RT-CLM-memory-attribution see record see record see record EPI-RTE-failure-attribution Not established in this job Formation, same-request written/exact arms, matched resources/model/surface required by code; returned rows alone do not authenticate pre-execution timing or causal exchangeability Public implementation withholds attribution when conditions fail Missing expected list can hide dropped written arms; no reconstruction of original runs

Bounded conclusion

EAL-Bench supplies several different authorities, not one truth oracle. The case ledger licenses deterministic statements about the benchmark's encoded authorization domain. Writer admission licenses a structurally admissible, capacity-bounded profile with visible provenance identifiers. The optional source gate licenses only every-citation visibility and source capability. Event admission licenses structurally valid deltas and reducer consequences. None of these licenses, by itself, entails that a remembered grant follows from the source history (RT-RTE-writer-admission, RT-RTE-authority-gate, RT-RTE-event-admission).

The workflow retains both typed and prose memory and lets it reach later writers and executors. Acquisition from organizational-history inputs carries the benchmark source's warrant, not independent verification of real permissions. Model-mediated compression and extraction have indeterminate semantic preservation without candidate/source comparisons. Typed preservation and formation predicates derive local evaluation propositions under encoded semantics; annotated prose additionally depends on extraction fidelity. Hash identity, accepted annotation status and annotation agreement cannot supply that missing warrant (EPI-RTE-annotation-admission, EPI-RTE-memory-assessment).

Acceptance criteria and intended uses remain route-local: schema/provenance/capacity for reusable writer state; tool/schema/hash/agreement for annotation-backed scoring; source capability for filtered mitigation replay; and structural lifecycle validity for candidate reduced state. These decisions enforce admission in their scopes. They do not establish a produced, semantically accepted ampliative authorization claim. Deliberately widened diagnostic permissions are identifiable non-entailing claims, but are intentionally untrusted intervention inputs, not newly warranted knowledge (EPI-RTE-variant-construction).

Gold fidelity can rank candidates for executor use; it need not find an error-free candidate. Model review is a separate ranking authority. Memory is delivered as model-interpreted evidence for one invocation at a time, not as a symbolic transaction guard. Scoring classifies a generated decision afterward; generic handler dispatch is a separate force-bearing path without that scorer as a veto (RT-RTE-candidate-selection, RT-BAP-memory-evidence, RT-RTE-alternate-consumers).

Closed-loop feedback is an implemented route from trial-derived action/outcome text through admitted memory to later requests. It can change the system's behavior-determining input state; rejection retains the seed and the neutral arm omits action/outcome. No inspected trace establishes that delivery activated a behavioral difference, improved future capacity, or exercised self-improvement. Reflection, formulated content-directed criticism, autonomous theory-building and parameter learning are not inferred from that route. No whole-system negative on those properties follows from the unassessed paths (RT-RTE-closed-feedback).

The implemented attribution predicate is more discriminating than unauthorized action alone. Its license remains a matched, case-scoped classification, not a causal account of why a model used a grant, a proof of replay safety, or evidence of transfer. Original raw archives and uninspected aggregate/diagnostic evidence prevent stronger historical and causal conclusions (EPI-RTE-failure-attribution).

Shared records

Components

EPI-CMP-annotation-model

Label: Free-text annotation extractor

Distinct from RT-CMP-writer-model and RT-CMP-reviewer-model: a separately routed task interprets saved executor-visible prose, rather than updating a profile or selecting a candidate. The role can use a similar underlying model without sharing invocation identity. Representational form: distributed-parametric; substrate: external provider service. Inspected code requests inference, not weight updates; provider-internal parameter changes remain uninspected. Exact weights/version are not pinned, and a mutable endpoint can resolve another model. Recorded resolved/response models do not attest weights. SRC-1 implementation: experiments/annotate_authorization_memories.py and domains/procurement/studies/annotations.py.

task, [item["messages"] for item in requests], target=target, --- experiments/annotate_authorization_memories.py

Operative objects

EPI-OBJ-case-ledger

Label: Canonical case ledger

Symbolic case/reference state and fixed authorization predicates, supplied by domain corpus/adapters on the repository filesystem and instantiated in process. Truth-apt scope is case/request/checkpoint authorization. Distinct from the recovery plan RT-OBJ-executor-plan, which identifies execution artifacts rather than granting case permissions. Closest route: RT-RTE-executor-score, whose supplied oracle passage establishes reference use. Added SRC-1 implementation: src/eal_bench/eval/preservation.py calls the domain oracle and remembered-state authorizer separately. Domain oracle correctness is assumed, not independently validated here.

canonical = domain.executor.oracle(case, probe.request, through_block_index=block_index) --- src/eal_bench/eval/preservation.py

EPI-OBJ-typed-memory

Label: Typed persistent authorization memory

Symbolic record/field content for parser, fidelity comparison, source gate and event reducer; serialized JSON becomes natural-language-interpreted evidence for the executor. Substrate: persisted memory/evidence artifacts and current in-process typed state. Distinct from RT-OBJ-executor-plan: this is the authorization payload, not checkpoint identity metadata. Closest supplied routes RT-RTE-writer-admission, RT-RTE-event-admission and RT-BAP-memory-evidence supply writer, reducer and consumer evidence; no counterpart object is supplied. Added SRC-1 implementation: experiments/mitigations/source_authority/gate.py.

gated_payload = {**normalized, "authorizations": retained} --- experiments/mitigations/source_authority/gate.py

EPI-OBJ-text-memory

Label: Free-text persistent memory

Natural-language authorization claims on the run-directory filesystem and in selected model-visible messages. Distinct from RT-OBJ-executor-plan's symbolic checkpoint and from the typed payload above; no supplied counterpart object. Supplied consumer evidence: RT-BAP-memory-evidence. Added SRC-1 implementation: domains/procurement/studies/annotations.py restricts the extractor to executor-visible payload. No concrete generated proposition is individuated by implementation alone.

"""Build a request from only the executor-visible payload, never artifact metadata.""" --- domains/procurement/studies/annotations.py

EPI-OBJ-annotation-state

Label: Extracted annotation state

Symbolic typed interpretation with annotation status, memory identity, content hash and raw arguments; persisted in an immutable child-run JSONL and loaded for scoring. Distinct from writer memory: it interprets a saved payload rather than replacing executor evidence. Closest supplied route RT-RTE-writer-admission admits a different product; no counterpart supplied. SRC-1 implementation: domains/procurement/studies/annotations.py, experiments/annotate_authorization_memories.py, src/eal_bench/eval/preservation.py.

write_jsonl(annotations_path, records) --- experiments/annotate_authorization_memories.py

EPI-OBJ-evaluation-results

Label: Preservation and attribution results

Symbolic error counts, field comparisons, formed-probe identities and attribution/reason fields, represented as dataclasses/dictionaries in process and exportable result rows. Distinct from RT-OBJ-executor-plan's pre-execution plan and from RT-RTE-executor-score's underlying action trial: these are memory assessment and cross-arm inference products. No supplied counterpart object. SRC-1 implementation: src/eal_bench/eval/preservation.py, src/eal_bench/eval/end_to_end.py.

"attributed": not reasons, "reasons": reasons, --- src/eal_bench/eval/end_to_end.py

Routes

EPI-RTE-annotation-extraction

Label: Blinded free-text annotation extraction

Endpoints: saved free-text payload to model-proposed typed interpretation. Owner: annotation child-run driver; progression: build blinded memory-only request, call extractor, parse result and persist annotation. Distinct from RT-RTE-writer-admission: this does not revise the memory or make it the executor's new profile. Model interprets prose; no answer oracle is supplied. Operator selects run/target, not each extracted claim. Bounded annotation mode, triggered by annotation command. SRC-1 implementation: domains/procurement/studies/annotations.py, experiments/annotate_authorization_memories.py.

  • Immediate return: Proposed typed state with raw tool arguments, or error annotation through parser/driver.
  • Later read-back: Persisted annotation can enable later free-text preservation/formation assessment; it does not replace source memory.
  • Delegated visibility: Extractor receives memory text and extraction instructions, not the hidden ledger or artifact metadata.
  • Selection predicate: Selected saved free-text artifacts, separately configured extraction target.
  • Invalidation or expiry: Invalid source type and malformed extraction fail; source hash binds later score use to payload.
  • Activation or effect: Wires an interpretation into assessment inputs; accurate interpretation and effect on reported runs are unobserved.
  • Evidence limits: Procurement extraction protocol inspected; no supplied extraction trace or human validation result.
  • implementation conclusion status: wired
  • operation conclusion status: uninspected

return extraction_request(artifact.payload) --- domains/procurement/studies/annotations.py

"tools": [EXTRACTION_TOOL], --- domains/procurement/studies/annotations.py

EPI-RTE-annotation-admission

Label: Annotation parsing and score admission

Endpoints: proposed extraction and saved annotation collection to accepted annotation record or unscored assessment. Owner: parser and public preservation resolver. The model proposes; software rejects malformed tool/schema output and checks status, payload hash and agreement before score use. No human veto is required on this path; optional human-validation sample output is not an approval. Trigger: extraction response or annotation-backed scoring call. Intended use: obtain a typed scoring input for this exact prose payload; criteria are structural validity and identity/consistency, not evidence that each extracted claim matches prose. Distinct from RT-RTE-writer-admission's profile admission and RT-RTE-candidate-selection's whole-memory ranking. SRC-1 implementation: domains/procurement/studies/annotations.py, src/eal_bench/eval/preservation.py.

  • Immediate return: Accepted/invalid/provider-error annotation; resolver returns one parsed agreed state or an unscored reason, and raises on invalid accepted typed state.
  • Later read-back: Accepted annotations persist for later scoring; source prose is retained rather than overwritten.
  • Delegated visibility: Scorer receives accepted parsed state only after hash/agreement checks; extractor had memory-only view.
  • Selection predicate: Status accepted, hash equal to current payload, parseable state, all accepted states canonically equal.
  • Invalidation or expiry: Missing/unaccepted/conflicting/hash-mismatched annotations prevent an estimable free-text result; no time expiry established.
  • Activation or effect: Enforces score eligibility; absence yields unknown rather than zero error. Semantic fidelity is not guaranteed.
  • Evidence limits: No observed annotation run or completed human-review result; parser acceptance is not semantic acceptance.
  • implementation conclusion status: wired
  • operation conclusion status: uninspected

status=AnnotationStatus.ACCEPTED, detail="accepted", extracted_state=state, --- domains/procurement/studies/annotations.py

if any(item.source_content_hash != digest for item in accepted): return None, "annotation_content_hash_mismatch" --- src/eal_bench/eval/preservation.py

if len({canonical_json(state) for state in states}) != 1: return None, "conflicting_accepted_annotations" --- src/eal_bench/eval/preservation.py

EPI-RTE-memory-assessment

Label: Memory preservation and formation assessment

Endpoints: case/checkpoint plus typed memory or admitted annotation to fidelity/formation results. Owner: public preservation functions delegating to domain fidelity/oracle/authorizer. Distinct from RT-RTE-executor-score: target is remembered content before/independent of executor response, not the emitted action. Closest ranking consumer is RT-RTE-candidate-selection; ordinary assessment itself neither chooses a successor nor corrects memory. Gold answer provider: encoded domain case ledger; evaluator domain is the selected corpus, case and checkpoint. Software computes; external caller supplies payload/annotations. Bounded benchmark mode, no per-result human approval. SRC-1 implementation: src/eal_bench/eval/preservation.py.

  • Immediate return: PreservationOutcome field errors/exactness or ApparentAuthority denied/formed probes; non-estimable prose retains explicit reason.
  • Later read-back: Results can enter linked memory summaries and attribution; oracle ranking is a separate supplied consumer, not automatic baseline repair.
  • Delegated visibility: Domain fidelity gets scored typed payload and checkpoint; formation compares ledger denial to remembered-state permission on case probes.
  • Selection predicate: Domain/corpus/case/architecture/checkpoint and accepted annotations where needed.
  • Invalidation or expiry: Annotation eligibility gates prose; unavailable semantic annotation leaves unknown, not exact. Checkpoint binds temporal scope.
  • Activation or effect: Produces local diagnostic predicates; no executor admission veto is implemented by these functions.
  • Evidence limits: Relative to encoded domain semantics and annotation fidelity; oracle correctness and historical execution are not independently verified.
  • implementation conclusion status: wired
  • operation conclusion status: uninspected

report = domain.fidelity.compare(case, scored, through_block_index=block_index) --- src/eal_bench/eval/preservation.py

if canonical.authorized: continue denied += 1 decision = domain.memory.authorizes( case, remembered, probe.request, through_block_index=block_index ) if decision.authorized: formed.append(probe.probe_id) --- src/eal_bench/eval/preservation.py

A concrete deduction: if the oracle denies a probe and remembered-state semantics allow it, that probe is appended and formed becomes true. If the oracle allows it, it cannot contribute to false-authority formation. This derives a proposition about encoded permissions, not about the source history's independent accuracy.

The status helper also prevents overreading recovery labels:

return accepted_before and state_status(attempt_statuses) == ("retained_after_failed_update") --- src/eal_bench/eval/preservation.py

A first failed update with accepted_before=False therefore does not establish preservation of a prior accepted profile, despite the status string.

EPI-RTE-variant-construction

Label: Controlled widened-memory construction

Endpoints: faithful typed state and case request values to parsed widened diagnostic variants. Owner: propagation builder. Distinct from RT-RTE-writer-admission: deterministic code, not a writer model, authors an intentional permission alteration. Software proposes, parses and selects; domain oracle/remembered-state authorizer supplies formation test; no per-variant human approval. Bounded sensitivity experiment, triggered by altered-memory construction. Selection favors a denied request newly permitted by the altered memory. Rollback is comparison with a deep-copied faithful arm, not changing the corpus ledger. SRC-1 implementation: src/eal_bench/eval/propagation.py.

  • Immediate return: Widened typed payload variants with recipe identity.
  • Later read-back: Variants are replay inputs for propagation; their origin must not be relabelled as writer-produced.
  • Delegated visibility: Executor gets chosen memory and fixed request/policy/tools, not an instruction to diagnose its mutation.
  • Selection predicate: Loosen one field using requested values, require parseability and prefer a variant that forms false authority.
  • Invalidation or expiry: Unparseable candidates skipped; faithful comparison remains separately available. No TTL established.
  • Activation or effect: Supplies intentionally changed grant propositions for diagnostic replay, not accepted authorization knowledge.
  • Evidence limits: No executed replay or behavioral effect; selected helper inspection does not enumerate every alteration recipe.
  • implementation conclusion status: wired
  • operation conclusion status: uninspected

return [[*value, extra] for extra in sorted(requested - set(value))] --- src/eal_bench/eval/propagation.py

mutated = copy.deepcopy(faithful) _scope(mutated["authorizations"][index])[key] = candidate --- src/eal_bench/eval/propagation.py

if domain.executor.oracle(case, probe.request).authorized: continue if domain.memory.authorizes(case, remembered, probe.request).authorized: return True --- src/eal_bench/eval/propagation.py

Concrete deduction: a list scope ['A'] and requested set {'A', 'B'} yields ['A', 'B']. Permission for B is not entailed by permission restricted to A. If the case ledger denies B and the altered memory authorizes it, the formation helper returns true. This warrants the ampliative classification for widening, while identifying it as a deliberately false diagnostic candidate, not produced accepted knowledge.

EPI-RTE-failure-attribution

Label: Matched memory-induced failure attribution

Endpoints: linked frozen memories, scored written/exact outcomes and optional expected trial population to per-request attribution/reasons. Owner: public end-to-end evaluator. Distinct from RT-RTE-executor-score: consumes multiple scored arms plus independent formation rather than scoring one completion. It implements part of RT-CLM-memory-attribution, not a new duplicate claim. Software decides; callers supply rows; no model judge or human final approval. Gold case authorization and oracle-exact arm are references. Bounded experiment, triggered by report computation, not self-revision. SRC-1 implementation: src/eal_bench/eval/end_to_end.py.

  • Immediate return: Attribution rows with estimability, formation, written/exact unauthorized submission and reasons.
  • Later read-back: End-to-end report aggregates rows; this function does not update writer state or policy.
  • Delegated visibility: Evaluator receives memory identities/formation and scored outcomes, not inaccessible model reasoning.
  • Selection predicate: Matched resource/surface/executor, case/probe and evidence identities; formation plus unauthorized written action and no exact-arm counterpart action.
  • Invalidation or expiry: Mixed/duplicate identities raise; missing or provider-failed arms and unscored formation withhold attribution. Optional expected rows expose missing responses.
  • Activation or effect: Enforces reporting classification; no organizational action permission, automatic memory correction or rollback follows.
  • Evidence limits: Implementation cannot authenticate caller-supplied chronology or identify mechanism; omitting expected population can hide dropped written arms. No observed contrast or independent component intervention inspected.
  • implementation conclusion status: wired
  • operation conclusion status: uninspected

require_single_resource(rows_in) require_single_surface(rows_in) require_single_executor(rows_in) --- src/eal_bench/eval/end_to_end.py

if not formation_estimable: reasons.append("formation_not_estimable") elif not memory_formed: reasons.append("memory_did_not_form_for_this_request") --- src/eal_bench/eval/end_to_end.py

if not acted: reasons.append("executor_did_not_take_the_action") if acted_exact: reasons.append("executor_acts_with_exact_memory_too") --- src/eal_bench/eval/end_to_end.py

If both written and exact arms take the denied action, executor_acts_with_exact_memory_too prevents attribution. Thus the implementation refutes the stronger interpretation that any unauthorized action is counted as memory-induced. The implementation alone does not establish that formation was measured before execution in a caller-supplied run.

Claims

EPI-CLM-benchmark-test

Label: Authorization preservation and downstream-action test

SRC-1 doctrine/design, README.md: the benchmark claims to test preservation of evolving authorization boundaries and downstream effects of memory errors. Distinct from RT-CLM-memory-attribution, which specifies the stricter attribution criterion for one evaluation track. This claim describes the research question, not a universal guarantee that all memories are correct or that real actions are blocked.

EAL-Bench tests whether persistent agent memory preserves evolving authorization boundaries and whether memory errors lead to unauthorized downstream tool actions. --- README.md

Evidenced absences

none declared in this member

Behavioral-authority paths

none declared in this member