Add the required public messaging - #65
Merged
Merged
Conversation
Issue #47 lists messaging the repository was required to carry, and none of it appeared anywhere: not "Your AI has credentials. BlockSiFr gives it boundaries", not "Same identity. Same permission. Different consequence. Different decision", not BlockSiFr Control, Execution Control Infrastructure, Consequence Intelligence, the January 6 2027 launch date, the early-access line, or the CTA. The issue also records why it was never applied: repository rules blocked the automated commit. Those rules were scoped to main and unblocked earlier today, so it lands now. It sits below the quickstart rather than above it. A visitor arriving at an open-source repository is there to find out whether the thing runs, and the commercial framing reads better once they have seen that it does. The naming also goes into COMMERCIAL_BOUNDARY.md, where someone looking for the open/commercial line will actually look. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
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.
Closes #47.
#47 lists messaging the repository was required to carry. None of it appeared anywhere — not "Your AI has credentials. BlockSiFr gives it boundaries", not "Same identity. Same permission. Different consequence. Different decision", not BlockSiFr Control, Execution Control Infrastructure, Consequence Intelligence, the January 6 2027 launch date, the early-access line, or the CTA.
The issue records why: "Repository rules prevented the automated messaging commit because this protected repo requires verified signatures / Code Scanning compliance." Those rules were scoped to
mainand unblocked earlier today, so it lands now.Placement: below the quickstart, not above it. Someone arriving at an open-source repo is there to find out whether the thing runs; the commercial framing reads better once they've seen that it does. The naming also goes into
docs/COMMERCIAL_BOUNDARY.md, where anyone looking for the open/commercial line will actually look.Paired with #63, which resolved the three competing product names, the repo now says one thing about what this is called.
🤖 Generated with Claude Code