Fix false Symphony telemetry claim in llm-cost-attribution README#7
Merged
Conversation
Symphony explicitly out-of-scopes PR-merge state, CI status, and reviewer verdicts (§2.2 Non-Goals, §11.5). They are not recorded by a conformant orchestrator — that was wrong. Updated to accurately state they come from GitHub and are outside the CLI transcript boundary.
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.
Summary
llm-cost-attributionThe old text claimed: "A Symphony-conformant orchestrator records these in its own telemetry" (referring to PR-merge state, CI status, and reviewer verdicts).
The Symphony spec explicitly out-of-scopes all of this. §2.2 (Non-Goals): "Built-in business logic for how to edit tickets, PRs, or comments." §11.5: "Symphony does not require first-class tracker write APIs in the orchestrator. Ticket mutations... are typically handled by the coding agent."
The corrected text accurately states these come from GitHub and are outside the CLI transcript boundary, with spec section references.