Skip to content

Fix false Symphony telemetry claim in llm-cost-attribution README#7

Merged
github-actions[bot] merged 1 commit into
mainfrom
readme/symphony-fix
May 27, 2026
Merged

Fix false Symphony telemetry claim in llm-cost-attribution README#7
github-actions[bot] merged 1 commit into
mainfrom
readme/symphony-fix

Conversation

@riddim-developer-bot
Copy link
Copy Markdown
Contributor

Summary

  • Corrects a factually wrong sentence in the "What it doesn't do" section of llm-cost-attribution

The 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.

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.
@github-actions github-actions Bot enabled auto-merge (squash) May 27, 2026 23:10
@github-actions github-actions Bot merged commit 1bcc9f3 into main May 27, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant