docs: add AEP <-> OpenTelemetry GenAI field mapping (closes #159) - #160
Merged
Conversation
Position AEP explicitly as an evidence-integrity layer on top of OTel GenAI, not a competing protocol. Adds docs/AEP-OTEL-MAPPING.md: - fields AEP shares with OTel GenAI (trace_id, gen_ai.system, gen_ai.request.model, gen_ai.tool.name, token usage, agent id ...) - the delta AEP adds with no OTel equivalent: signature/tamper-evidence, capability_decisions, side-effect provenance + taint, verifier_results, argument_drift, governance budgets All fields are drawn from the actual schemas/aep/*.schema.json. README gains a "Standards alignment" subsection linking the mapping. Docs-only; schema conformance + drift tests unchanged (18/18 pass).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #159.
Positions AEP explicitly as an evidence-integrity layer on top of OpenTelemetry GenAI, not a competing telemetry protocol. Teams already emitting OTel GenAI spans can see, field by field, exactly what AEP adds.
Adds
docs/AEP-OTEL-MAPPING.md:trace_id,gen_ai.system,gen_ai.request.model,gen_ai.tool.name, token usage, agent id, etc. (populate from existing spans).signature/ tamper-evidence + Sigstore bundle,capability_decisions, side-effect provenance (side_effect_class, pre/post state digests, taint labels),verifier_results,argument_drift, and governance budgets beyond token usage.Every field is drawn from the actual
schemas/aep/*.schema.json(no invented fields). README gains a Standards alignment subsection linking the mapping.Docs-only. Schema conformance + drift tests unchanged (18/18 pass locally).