Conversation
- The logoscore passage no longer describes a daemon without its bundled capability_module forwarding as the runtime (modules saw Host): such a daemon does not start now. - host_services lists token_delivery alone. token_registry is still accepted but grants nothing. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This branch has not been deployed
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.
Part of deleting legacy mode (the runtime without its token authority). Stacked on #96 (
docs/runtime-control).Two passages in the developer guide described what legacy mode allowed:
capability_moduleused to forward calls as the runtime, so modules sawHost. With feat!: the daemon is a shell over core_service; its suites run the authority logos-logoscore-cli#146 such a daemon does not start ("no token authority").host_services(metadata table): the closed set is nowtoken_deliveryalone.token_registryis retired in the protocol (feat(tokens): retire the token registry logos-protocol#98): still accepted so older metadata builds and older hosts' grants don't fail, but it grants nothing.Tutorial Sync Rule: the guides were searched for every other name the stack removes (
logos_core_set_token_listener,logos_core_get_token, the lifecycle C functions,LOGOS_LOAD_*,registerRestriction,tokenListener,saveCoreTokenToQtStore), and none appears. No spec changed, so no output needed regenerating.🤖 Generated with Claude Code