docs: valuation guardrails harvest v0.1 (terminalDiscipline field semantics) - #2
Merged
Merged
Conversation
… semantics) Forward-only harvest of the whitepaper-era reverse-DCF production guardrail set before deletion of the source artifacts: the five-item discipline set (GDP-ceiling terminal bound, TV-dominance flag, margin fade path, intangible maintenance / no-free-perpetuity, capacity gates + scar scenario) that gives the governed usignal terminalDiscipline fields their intended semantics — currently encoded nowhere except the staged residue copy already ruled for deletion. Non-canonical research register; decides nothing. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
|
Kilo Code Review could not run — your account is out of credits. Add credits or switch to a free model to enable reviews on this change. |
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.
Summary
Second forward-only harvest (same pattern as #1): one new file,
docs/AFI_VALUATION_GUARDRAILS_HARVEST.v0.1.md, preserving the whitepaper-era reverse-DCF production guardrail set in current-register terms, authorizing deletion of the source folder (Nano Trust Bin / Universal_Core_Bundle_AFI).Why this survived the forward-only test (adversarially verified): the governed usignal contract defines
terminalDisciplinefields (gStable, roiicIntangible, salesToCapital, halfLifeDays, capacityConstraints) but no current register gives them weighting/lint semantics — the only implementation ever written isafi-config/afi-uss-pr-v2p1/server/validateAndWeight.ts:54, inside the stale staged residue copy already on the cleanup backlog for deletion. This doc is the design input for the future USS lens-weighting/lint law and for candidate afi-mathreverseDcfextensions (TV-dominance flag, margin fade path).What was deleted with zero harvest (all superseded/represented): the four-generation USS lens lineage (its end state IS the governed usignal canon; the v2p1 tree is byte-identical to the staged workspace copy), the math-and-schema-tests bundle (afi-math is a byte-level superset — logistic/tvMultiple/reverseDCF bodies and every test vector already in the vitest suite), DMV lint functions (retired register), and the rest of the Pablo memo/exhibits (formulas all canonical in afi-math).
Register discipline: NON-CANONICAL research input per math-authority-v0.1 §3; decides nothing; the lenses-optional-but-weighted doctrine is cited from AFI_CONFIG_OVERVIEW.md, not restated.
🤖 Generated with Claude Code