paper(schema-bound-tokens): reconcile §4.1 tau_burn with tokenomics schedule - #170
Merged
Conversation
…nomics schedule (~25x steady-state)
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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
Resolves the one item the consistency re-audit (#169) flagged for author decision: schema-bound-tokens §4.1 cited "recommended τ_burn ∈ [0.3, 0.5]," contradicting the canonical AVOW Tokenomics §7 schedule {0.60, 0.40, 0.25} and themisra-licensing's 0.25 burn share.
The fix
The §4.1 bound is explicitly qualitative (the paper defers the precise parameterized version to v0.3 pending devnet data, line 167) and used a transparent 100×τ_burn mapping (0.3→30, 0.5→50). So this re-anchors to the correct τ_burn values rather than redoing a derivation:
τ_burn ∈ [0.3, 0.5]→ "AVOW Tokenomics §7 schedule (steady-state 0.25, rising to 0.60 during bootstrap)"; the bound now states the binding steady-state case at ~25× (τ_burn = 0.25), noting bootstrap phases only loosen it.This is strictly more correct, not just consistent: the old "30-50×" overstated the steady-state margin (steady-state τ_burn is 0.25, below the old band's floor). The v0.3 precise-bound deferral is unchanged.
Also
CONSISTENCY_REVIEW.md §5flipped from "flagged for author decision" → "resolved"; summary block + §7 open-items updated to match.Test plan
check_citations.pypasses (102 citations)[0.3, 0.5]or "30 to 50" strings remain in SBT (verified)