Event Governance And Lineage
Governs event ownership, classification, metadata, lineage, quality and lifecycle. Use when governing shared event catalogues, schemas, or stream ownership.
Install
$ agentstack add skill-mmccalla-coding-agent-skill-library-event-governance-and-lineage ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-mmccalla-coding-agent-skill-library-event-governance-and-lineage) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Event Governance and Lineage
When to use
Use when events are shared, reused, regulated or business-critical.
Objective
Produce a practical, concise, traceable architecture artefact that a coding agent can use to guide implementation or review.
Procedure
- Assign event owner.
- Define catalogue metadata.
- Classify sensitivity.
- Link to capability/value stream/data product.
- Capture producer/consumer lineage.
- Define quality/contract checks.
- Define retention/lifecycle.
- Define access controls.
Required outputs
- Owner
- Catalogue metadata
- Classification
- Lineage
- Quality checks
- Lifecycle/access policy
Best-practice alignment
Apply event-driven best practice: business event semantics, producer/consumer ownership, schema contracts, compatibility, ordering, partitioning, idempotency, replay, retention, lineage, observability and operational SLOs.
Quality checks
- No orphan streams.
- Sensitive data is classified.
- Producer/consumer lineage exists.
Avoid
Do not rely on tribal knowledge for event meaning.
Governance template
For each shared event, capture owner, business definition, source capability, producer, consumers, schema version, classification, retention, quality checks, lineage links and support contact. A catalogue entry is not complete until consumers can understand meaning, sensitivity, replay constraints and who approves breaking changes.
References
- DAMA-DMBOK (DAMA International)
- EDM Council CDMC (Cloud Data Management Capabilities)
- CloudEvents specification
Verification
- [ ] Required artefacts produced and linked to scope.
- [ ] Decisions, assumptions and risks stated explicitly.
- [ ] Quality checks or validation performed.
- [ ] Files changed reported with traceability preserved.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: mmccalla
- Source: mmccalla/coding-agent-skill-library
- License: Apache-2.0
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.