Retire @async reserved syntax; add spec-census facts file - #6
Open
Disentinel wants to merge 1 commit into
Open
Disentinel wants to merge 1 commit into
Disentinel wants to merge 1 commit into
Conversation
`@async` had its own branch in `temporal()` answering `'@async' is reserved syntax, not in v0`. That message says one thing beyond the refusal: the word is being held. The effects executor is not going to be built, so it was held for nothing. The branch is gone: `@async` is refused by the single arm that refuses every unknown marker, and the temporal set is exactly the three the section 1.1 grammar always listed -- the reservation was never in the production, only in the prose. START.md is not edited, per the tree's own idiom: section 8 was retired item by item by LIMITS.md through `amends[map]`, not by deletion. `l_no_async` now amends both sentences that were about the WAITING rather than the absence -- `s_async_reserved_rejected` (3.3) and `s7_no_pretend_async` (7) -- and says the stronger thing: not reserved, not a marker, refused like any other unknown one. The world survived the feature and was re-pointed rather than deleted. A superseded duty keeps its guard link while dropping out of `live_duty`, so `c_w_async_reserved` would have gone on resolving while standing behind a sentence nobody owed; it guards `l_no_async` now, which took the LIMITS.md bullet from uncovered to covered. Renamed to async-refused.rofl because `reserved` had stopped being true of it. superseded 8 -> 10, live 124 -> 122, uncovered 102 -> 101, `guarded_by` unchanged at 17, prohibitions with no mechanical check still 0. 94/94 worlds, ts only -- the release binary is not built in this container. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WcB3U4mr6HkxfJgbwMNgUY
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
2 participants
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
This change removes
@asyncfrom reserved syntax and updates the specification coverage model to track duty acceptance and coverage inheritance. The parser no longer reserves@asyncas a keyword, allowing it to be treated as an unknown temporal marker and refused like any other. A newspec-census.roflfacts file is introduced to track specification coverage checks.Key Changes
Parser: Removed the reserved syntax check for
@asyncinsrc/parser.ts. The marker is now rejected as an unknown temporal marker rather than as reserved syntax.Specification Coverage Model (
rules/spec-coverage.rofl):inherits_coverandcoveredrelations to track coverage inheritance through duty restatementaccepted_shortcutandidle_shortcutrelations to handle accepted gaps and idle coverageChecks Registry (
facts/checks.rofl):async_reservedtoasync_refusedto reflect the new semanticsexamples/checks/async-reserved.rofltoexamples/checks/async-refused.roflrules_specandasync_refusedworldsExamples:
examples/checks/async-reserved.roflexamples/checks/async-refused.roflwith updated documentation explaining that@asyncis no longer reservedDocumentation:
LIMITS.mdto clarify that@asyncis not reserved for future useREADME.mdtemporal marker documentationFacts Files:
facts/spec-census.rofl(285 clauses) to track specification coverage censusfacts/spec.roflwith expanded coverage tracking (212 clauses vs. 178)facts/findings.roflwith new findings related to coverage model changesfacts/goldens.roflwith new golden state hashes reflecting all changesImplementation Details
The coverage model now tracks:
The
async_refusedworld validates that the parser correctly rejects@asyncas an unknown temporal marker, maintaining the prohibition against using it while removing the special reserved syntax status.https://claude.ai/code/session_01WcB3U4mr6HkxfJgbwMNgUY