Roadmap item 4: Add inactive dormant publisher payload - #227
Merged
Conversation
added 7 commits
September 2, 2026 14:42
# Conflicts: # README.md # RESTORE.md # ci/required-files.txt
# Conflicts: # README.md # RESTORE.md # ci/required-files.txt
…fault-dormant-publisher-adapter-v1 # Conflicts: # README.md # RESTORE.md # ci/required-files.txt # scripts/test/portable-core-schema.test.sh
Owner
Author
Codex reviewer (cross-vendor, read-only)Reviewed-head: d30f007 Posted verbatim by The dormant publisher normalizer consistently validates claim shape, trusted bindings, content identity, and inert authority ceilings. The focused tests and restore manifest updates align with the new payload, with no actionable correctness issues found. |
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
Scope
Tracks Roadmap item 4 without closing an intake issue. This is one payload-only unit. It adds no adapter manifest or profile binding; the default-profile assembly follows after every payload has a durable main identity.
Safety
The payload is inactive, offline, and dormant. It has no credential, network, capability, permission, tool, merge, publish, activation, or external-write effect. It is separate from the temporary construction publisher gate.
Targeted proof
The preserved one-concern branch was adopted by merging current main normally. It was not rebased or force-pushed.