legacy: archive the cost-optimization PoC suite (superseded by cost/) - #26
Open
geisbruch wants to merge 1 commit into
Open
legacy: archive the cost-optimization PoC suite (superseded by cost/)#26geisbruch wants to merge 1 commit into
geisbruch wants to merge 1 commit into
Conversation
First-pass cost governance pipeline (scanner → planner → apply) from the engine repo's corpus, kept for reference. README marks it as superseded and explains why cost/ replaced it.
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.
Copies the July 2026 first-pass cost-governance suite (8 YAMLs: scanner + per-level variants, per-scope analysis, remediation planner, apply-and-deploy, action-item event reactor) from the engine repo's corpus into
legacy/cost-optimization/.It is not meant for new deployments —
cost/replaced it after live bring-up (scope-config billing + loading factor, remote metrics agent, streaming-pagination/idempotent-item patterns). The README marks it as superseded and records why, so the design history stays discoverable next to its successor.No inline credentials (secrets are indirect
np.api.tokenbindings).🤖 Generated with Claude Code