Skip to content

paper(schema-bound-tokens): reconcile §4.1 tau_burn with tokenomics schedule - #170

Merged
proofmancer merged 1 commit into
mainfrom
paper/sbt-tau-burn-reconcile
May 28, 2026
Merged

paper(schema-bound-tokens): reconcile §4.1 tau_burn with tokenomics schedule#170
proofmancer merged 1 commit into
mainfrom
paper/sbt-tau-burn-reconcile

Conversation

@proofmancer

Copy link
Copy Markdown
Contributor

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:

  • §4.1 (line 163): τ_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.
  • §4.1 (line 165): "~30-50×" → "~25× at steady state (margin widens during bootstrap)".

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 §5 flipped from "flagged for author decision" → "resolved"; summary block + §7 open-items updated to match.

Test plan

  • check_citations.py passes (102 citations)
  • SBT PDF rebuilds clean
  • No [0.3, 0.5] or "30 to 50" strings remain in SBT (verified)
  • No em dashes

@proofmancer
proofmancer merged commit c4194fe into main May 28, 2026
2 checks passed
@proofmancer
proofmancer deleted the paper/sbt-tau-burn-reconcile branch May 28, 2026 21:50
@github-actions github-actions Bot locked and limited conversation to collaborators May 28, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant