NAP-NN: Topic payload semantics over IFC - #20
Closed
dskvr wants to merge 1 commit into
Closed
Conversation
Defines profile, chat, and stream context topic payloads carried over NUB-IFC without changing the generic IFC transport surface. Tested: git diff --check
Contributor
Author
|
Closing this umbrella topic-payload PR because the topic semantics should be split into separate numbered NUB-NN drafts per topic instead of one combined NUB. I will replace this with one PR per topic. |
This was referenced May 25, 2026
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.
Summary
NAP-NN-TOPIC-PAYLOADS.md, a provisional NAP-NN draft for IFC-carried topic payload semantics.Why
NAP-IFC defines the generic inter-frame transport:
ifc.emit,ifc.subscribe,ifc.unsubscribe, andifc.event. It does not define what a topic such asprofile:openmeans.This PR makes those topic payloads public napplet-agreed semantics instead of
leaving them as implementation-local conventions.
Spec / API surface
The draft defines payload and producer/consumer behavior for:
profile:openchat:open-dmlivestream:channel-switchstream:current-context-getstream:current-contextThe draft references NAP-IFC as the carrier and does not redefine IFC envelopes
or add a new shell API.
Compatibility
unsupported topics.
NAP-NN-TOPIC-PAYLOADSidentifier should be replaced withthe assigned NAP-NN number after merge.
Validation
git diff --check-> PASSgit diff --check HEAD~1..HEAD-> PASSrg -n "hyprgate|napplet/napplet|@napplet" NAP-NN-TOPIC-PAYLOADS.md README.md-> no matchesgit status --short --branch->## nap-topic-payload-semantics...origin/master [ahead 1]Non-goals
wm:*shell telemetry topics.shell:*host command topics.auth:identity-changed.stream:channel-switchalias promotion.Follow-ups
payload fields.