Struct RecordFence 

pub struct RecordFence {
    store: Arc<LeaseStore>,
    lease: Lease,
    agent: String,
    lost: Arc<LostReason>,
    last_ok_ms: Arc<AtomicI64>,
}

The writer-side fence on the agent’s shared record (spec §4.3, Phase 3).

Cheap in the common case: while the lease was confirmed ours within the TTL, nobody can have reclaimed it, so appends go ahead on in-memory state alone. After a longer gap — the holder was suspended, and its CLI and output reader resume together with the renewal task — the first append checks the lease file before writing, so output a reclaimed holder flushes on waking never reaches the record the new holder is writing.

Fields

store: Arc<LeaseStore>

lease: Lease

agent: String

lost: Arc<LostReason>

last_ok_ms: Arc<AtomicI64>

Implementations

impl RecordFence

pub fn may_write(&self) -> bool

May this process append to the agent’s shared record now?

Trait Implementations

impl Clone for RecordFence

fn clone(&self) -> RecordFence

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.