Verification telemetry timeline: visualizing proof, replay, provenance, and mutation rejection events

[JROChub]

I built a generic Open MCT example plugin that visualizes verification and provenance event streams as telemetry.

It displays:

• core verification status
• artifact lineage and replay fingerprints
• semantic packet binding
• witness observations
• mutation challenge results
• rejection traces and scope notes

The sample fixture is generated from a Power House/slbit-style memory-capsule workflow, but the plugin is intentionally generic and does not add Power House, slbit, Rust, WASM, or any verifier runtime as an Open MCT dependency. It only displays already-generated verification reports as telemetry.

I opened a draft PR here for review of the shape and fit:
#8362

I would appreciate maintainer guidance on whether this is best as:

1. an upstream example,
2. a docs/tutorial contribution,
3. an external community plugin,
4. or a smaller schema-only contribution.

The main boundary in the example is explicit: semantic packet data can explain verified core state, but it does not alter proof identity. The plugin displays reports; it does not claim Open MCT is cryptographically verifying the artifacts.