Analysis Port Publish: Transaction Ownership and Ordering

Publish contract

Publish only finalized transactions, maintain observed order, and enforce object ownership policy (clone/freeze/immutable).

[MON] publish checklist
- decode complete object
- assign timing/status metadata
- publish once in observed order
- do not mutate after ap.write

function void publish_txn(my_txn tr);
  my_txn out = tr.clone();
  ap.write(out);
  publish_hits++;
endfunction

• Explicit ownership policy prevents cross-subscriber mutation bugs.

• Filtered modes should be reported with counters.

• Smoke tests must validate publish and ingest liveness.

Applied Patterns

This appendix consolidates reusable monitor patterns for enterprise-scale UVM environments where multiple teams share protocol VIP.

Use this as a quick implementation checklist before releasing monitor updates into regression branches.

[MON][UVM][AGT] reusable pattern grid

sampling:
  accepted-handshake gating only

reconstruction:
  key-based accumulator with completion predicate

publishing:
  clone policy + counter instrumentation

debug:
  boundary-first triage with deterministic smoke

function void monitor_health_report();
  `uvm_info("MON_HEALTH",
    $sformatf("sampled=%0d published=%0d dropped=%0d pending=%0d",
      sampled_cnt, published_cnt, dropped_cnt, pending_cnt),
    UVM_LOW)
endfunction

[MON] review checklist

- passive contract verified
- reset/flush policy documented
- publish ownership policy documented
- consumer fan-out validated
- counters visible in report_phase

• Design monitor updates as API changes to downstream consumers, not local edits.

• Keep monitor diagnostics always-on and low overhead for regression reliability.

• Revalidate sample-to-publish boundary after every protocol extension.