NAP-1: Profile topic family - #21
Closed
dskvr wants to merge 3 commits into
Closed
Conversation
Contributor
Author
|
@copilot resolve the merge conflicts in this pull request |
This was referenced Jun 14, 2026
Rebased onto current master; spec only. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
dskvr
force-pushed
the
nub-01-profile-open
branch
from
June 17, 2026 19:14
132355e to
c0e30db
Compare
The numbered topic NAP is a language-neutral wire contract. The shell.supports example is not TypeScript-specific, so it now uses an untyped code fence. Constraint: Keep this branch scoped to its numbered NAP file. Confidence: high Scope-risk: narrow Tested: git diff --check Tested: rg found no ts or typescript code fences in the changed file
Open NAP proposal branches need reader-visible changelogs that track semantic spec changes without recording formatting-only migrations. Constraint: Changelog entries are one bullet per semantic commit-change. Rejected: Include schema-table or formatting-only commits | they do not change the spec contract or boundary. Confidence: high Scope-risk: narrow Directive: Keep future changelog entries semantic; omit changelog-only and formatting-only commits. Tested: git diff --check Not-tested: Rendered Markdown
Contributor
Author
|
Closing this because numbered NAPs are being removed from the registry. Cross-napplet payload shapes should converge as unnumbered conventions, without sequence assignment or Suggested alternative: |
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.
Summary
Broadens NAP-1 from one profile action to the
profile:*NAP-INC topic family. It keepsprofile:openas the first concrete topic and leaves room for future compatibleprofile:*topics.Why
One numbered NAP per tiny topic is too narrow, but the earlier umbrella topic draft was too broad to review or prove compatible. A profile namespace draft is the middle ground: small enough to reason about, broad enough to grow.
Spec / API Surface
shell.supports("inc", "NAP-1").["requires", "inc"].profile:openwith{ pubkey }.profile:*topics.Compatibility
Existing
profile:openproducers and consumers keep the same topic string and payload. The draft does not reserve direct-message, stream, shell, or relay topics.Non-goals
Follow-ups
NAP-2 covers the
stream:*family in a separate namespace draft. Additionalprofile:*topics should be added here only if they stay inside profile identity/display/navigation semantics.Supersedes the
profile:openportion of the closed umbrella topic payload PR #20.Changelog
c0e30db- Introduced NAP-1 as the profile topic family.