aoa-memo-writeback

Session evidence routing evaluates live `.aoa` artifacts against closeout context to emit a bounded memo writeback decision, ensuring raw transcripts are never mistaken as reviewed memory. It inspects evidence first to determine if a local memo candidate, reviewed-intake export, or explicit stop line is appropriate.

Separating raw `.aoa` artifacts from reviewed `aoa-memo` memory requires validating the owning repository's `memo/` port before emitting any writeback decision. This governance boundary ensures only reviewed evidence anchors durable memory packets while preventing direct unreviewed landings.

A no-writeback stop line is needed when session evidence lacks the posture required for reviewed-intake export or local memo promotion. Recording this explicit stop line preserves governance by documenting why a durable memory decision was deferred without direct landing.

Agent memory writeback requires validating the owning repository's `memo/` port before creating local memo candidates. This local-first governance guardrail ensures promotion remains legible and prevents direct durable landings outside the reviewed repository workflow.

Handling closeout scenarios with `.aoa` evidence involves inspecting session history for decisions, failures, and route changes before validating the repo's `memo/` port. The process outputs evidence-anchored packets or explicit stop lines to capture durable memory reasons absent from the final diff.

Session evidence routing does not perform direct durable landings; it only prepares reviewed-intake export packets or records no-writeback debt. It is limited by the requirement of an existing `memo/` port in the owning repository to enable any local memo candidate promotion.