docs: HC-114 — runtime resolver boundary decided#28
Merged
Conversation
Build/generation-time resolution is the only supported mode of the reference implementation; the embedded runtime resolver is out of scope by decision, not deferral. DOCS/RuntimeBoundary.md records the question, the rationale (the product is the reviewable artifact; provenance is review material, not telemetry; validation depends on enumerable contexts; the runtime niche composes via OpenFeature targeting resolved anchors), the binding design consequences (resolution stays a pure function; interpolation placeholders pass through as opaque strings) and the three revisit conditions. HC-115 parked accordingly. Also brings RFC §10 up to date — debugging (HC-110), binding time (HC-114) and complexity management (HC-116) recorded as answered; §9.8 no longer claims HC2104 is in progress (shipped in 0.5.0). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This was referenced Jun 12, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
This PR documents and codifies HC-114’s decision on the resolver’s binding-time boundary: Hypercode supports build/generation-time resolution only, and an embedded runtime resolver is explicitly out of scope (with defined revisit conditions). It updates the RFC and overview docs to reflect this decided boundary and parks HC-115 accordingly.
Changes:
- Adds a new decision record:
DOCS/RuntimeBoundary.md(HC-114). - Updates
RFC/Hypercode.mdto mark runtime resolution out of scope and refreshes §10 “Open Questions” to reflect HC-110/HC-114/HC-116 being answered. - Updates
OVERVIEW.mdandworkplan.mdto point to the decision and reflect HC-115 being parked.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| workplan.md | Marks HC-114 as decided and parks HC-115 based on the boundary decision. |
| RFC/Hypercode.md | Updates §9.8 runtime boundary language and refreshes §10 open questions / changelog entries. |
| OVERVIEW.md | Aligns overview “binding time” description with the HC-114 decision and links the decision record. |
| DOCS/RuntimeBoundary.md | Introduces the HC-114 decision record describing the build-time-only contract and revisit conditions. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Same staleness as §9.8 (already fixed in this PR), missed in the §9.4 parenthetical; the changelog bullet now covers both sections. (The historical 0.2 changelog entry keeps its wording — it records what was true at 0.2.) Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
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.
Decision record for HC-114 (stacked on #27).
Decision: build/generation-time resolution is the only supported mode; the embedded runtime resolver is out of scope — excluded from the core's contract with explicit revisit conditions, not deferred-pending-demand. HC-115 (OpenFeature bridge) parked accordingly.
Why (
DOCS/RuntimeBoundary.md):diffas invalidation feed, HC2104 gating — assumes a finished, reviewable resolved artifact. Per-request answers have nothing to hash, diff or review.validate --ctxin CI works because build-time contexts enumerate finitely; per-request context spaces would silently void the "every shipped context was checked" guarantee.Resolverstays an embeddable pure function as a fact, not a contract: no caching, no hot-reload, no per-request provenance sink.Also in this PR: RFC §10 Open Questions brought up to date (debugging → HC-110, binding time → HC-114, complexity → HC-116; integrity chain and type-system depth remain open); §9.8 stale "HC2104 in progress" fixed (shipped in 0.5.0); OVERVIEW §6 points at the decision.
Train: #27 (HC-116) → this → HC-120 → HC-121.
🤖 Generated with Claude Code