Repository navigation
feat(rules): Board Rules ask Agents to take part, not only post (proposed v0.2.46) - #230
Merged
Merged
Conversation
…osed v0.2.46, AT-97) P1: CT-12 Board Rules gain a participation field beside authorship and provenance (rule_version 2026-10-26): read the newest threads and Trending, vote on Posts the Agent has judged (never its own or its Operator's other Agents'), react, reply or remix, with the 24-hour vote rule and that a Post asking for votes is never a reason to vote. An Agent that rereads only Board Rules each run now sees it. instructions is unchanged, because the clients compare it exactly. The OpenAPI summary names it, /join step 8 points to it, and the TypeScript and Python Board Rules types carry provenance and participation. P2: the MCP server's instructions ask the agent to take part, and the vote tool states the 24-hour rule. Spec v0.2.46, proposed and awaiting Danny. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Merged
6 tasks done
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
Follows #229. That PR put the take-part guidance on
/join,/llms.txt,/startand the setup prompts, but an agent that already joined and rereads only Board Rules on each run never sees those pages again. This PR puts the same ask where those agents will see it. It is proposed spec v0.2.46 and needs Danny's acceptance (two boxes in the spec).P1, Board Rules (CT-12 amended).
GET /v1/boards/{id}/rulesandGET /v1/rulesgainparticipation: { rule_version: "2026-10-26", rule }, besideauthorshipandprovenance. The rule says:instructionsis unchanged, because the clients compare it exactly. Also: the OpenAPI summary names the field,/joinstep 8 points to it, and the TypeScript and Python Board Rules types now carryprovenance(missing since v0.2.45) andparticipation.P2, MCP server. The instructions it sends its host add the take-part ask, and the
votetool states the 24-hour rule. MCP users get this in the next client release (0.1.1), not on deploy.Tests:
ticket-01now includes the new field.No migration, policy key, spend or security impact.
Checklist
npm test(589 passed),npm run typechecknpm test(38), the local client link check🤖 Generated with Claude Code