docs(specs): spec-0026 amendment — vista_radius definition + blend_width range - #261
Merged
Merged
Conversation
…ult + blend_width range vista_radius was self-contradictory: floor "view-distance×16" (=192 at the shipped summit view-distance 12) exceeded its own default 176. Resolved: measured outward from the scene bounding-box edge, floor 192, default 208 (one chunk of slack over the fog line; perf non-gating). blend_width gains the range 1..=16 (0 is a hard edge, forbidden by the flatland interpenetration ruling). Reported by W-A during #155 implementation as a spec ambiguity, correctly not invented downstream. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
stellarfeline
added a commit
that referenced
this pull request
Aug 4, 2026
…ult 208, blend_width 1..=16 (PR #261) Planner design ruling, resolving the foundation's flagged contradiction (default 176 < the spec's own view-distance floor): - summit.vista_radius is now DEFINED as measured outward from the scene bounding-box edge; floor 192 (shipped summit view-distance 12 × 16, so peaks never pop out at the fog line); default raised to 208 (one chunk of margin). DW0366 below the floor. - flatland.blend_width range 1..=16 (0 is a hard material wall — the exact no-pedestal outcome the interpenetration ruling forbids; past 16 the dither outgrows the seam). Default 6 unchanged. DW0366 outside it. - HorizonSpec/horizon_defaults doc comments updated; DW0366 catalog row updated in the same PR; code-asserting cases added to the v09_horizon range test (DW-coverage gate). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
stellarfeline
added a commit
that referenced
this pull request
Aug 6, 2026
…am, not by this slice The DW0366 row claimed `summit.vista_radius`'s floor was unenforceable because the spec contradicted itself (floor 192 vs default 176). That was true when the foundation slice reported it and stopped being true on 2026-08-04: the spec-0026 amendment (PR #261, on `main` for 66 commits now) resolved both open params — `vista_radius` measured from the scene bounding box, floor 192, default 208; and `blend_width` 1..=16. Enforcement is deliberately NOT added here. Both params configure surrounds this slice does not emit, and the valley slice (task #155 W-B, PR #259, based on this branch) already carries the checks and the corrected default verbatim. Implementing them twice would put a duplicate in the dependent branch's path for no behaviour gained. The row now says what is true: the ambiguity is resolved, the enforcement is owed, and which slice owes it. No behaviour change: `dsl::validate::horizon_rules` and `horizon_defaults` are byte-identical to this branch's pre-merge state. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AjQ5p1Kv5MrkGPumi7yXWL
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.
Owner-review class (spec change). Two param rulings, resolving ambiguities W-A reported during #155 implementation rather than inventing values downstream:
DSL-side DW0366 range checks + the VISTA_RADIUS default constant ride the W-B PR (#259), which already touches horizon_rules.
Held for owner chat confirmation before merge (decisions presented in conversation).
🤖 Generated with Claude Code