Repository navigation
Emit Content Telemetry v1.0 with the full presentation funnel - #2
Draft
jalexspringer wants to merge 1 commit into
Draft
jalexspringer wants to merge 1 commit into
jalexspringer wants to merge 1 commit into
Conversation
Move the demo to @openattribution/telemetry 1.0.x (Content Telemetry v1.0 wire) and close the funnel gaps v1 makes explicit: - Each response's citations now also emit content_presented events (source_reference link presentations) with output_id and citation_id; the presentation ids flow to the client, and a link click's content_engaged event references the exact presentation it occurred on (spec 6.7). - content_cited carries id, output_id and turn_id; grounded and retrieved events carry turn_id, and each exchange is bracketed by turn_started/turn_completed at minimal privacy - the SPUR floor: no query text, no intent, content URLs visible. - The engage endpoint sends engagement_type "link_click" (the standard value; "click" was never in the spec, so clickthrough computation saw nothing). - The origin bot hook uses the SDK's new recordStandaloneEvent (spec 7.1 envelope, schema_version included - the hand-rolled POST omitted it) and classifies each bot's access purpose per spec 6.2. - Telemetry and dashboard panes display PRESENTED events. - RUNBOOK notes the server must accept v1.0 documents. Build and svelte-check pass against the v1 SDK (telemetry-js #3) installed locally. package-lock.json still pins 0.4.0: it regenerates once @openattribution/telemetry 1.0.0 is on npm. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019pcWWZA7Z4L34kG4dSw4Rf
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch had an error being deployed
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
1 participant
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.
Moves the demo to the Content Telemetry v1.0 wire via
@openattribution/telemetry1.0.x, and completes the lifecycle the demo shows off:content_presentedevent (source_reference/link) carryingoutput_idandcitation_id. The presentation ids flow back to the client through the SSEdonepayload.presentation_id, so thecontent_engagedevent references the exact surface occurrence (spec 6.7) — and it now sendsengagement_type: "link_click"; the previous"click"was never a standard value, so clickthrough computation saw nothing.turn_started/turn_completedatminimalprivacy (the SPUR floor — no query text, no intent), and content events carryturn_id.schema_version) with the SDK's newrecordStandaloneEvent, and each detected bot's access is classified with the spec 6.2purposevalues.Gated on
package-lock.jsonstill pins 0.4.0 and regenerates after publish (npm installwill fail until then; this PR stays draft).OA_TELEMETRY_URL. The referencetelemetry-serverhas merged v1 conformance; productionoa-telemetry-serverhas not — pointed at a v0.1 server, writes fail silently and the dashboard stays empty (noted in the RUNBOOK).Verification
npm run buildandsvelte-check(0 errors) pass with the v1 SDK built from telemetry-js#3 and installed locally.🤖 Generated with Claude Code
https://claude.ai/code/session_019pcWWZA7Z4L34kG4dSw4Rf