Repository navigation
docs(agents): the triage-filing block names the NAMESPACE, not just the type (step 1 of 3) - #5766
Merged
meshweaver-cloud[bot] merged 1 commit intoSep 26, 2026
Conversation
…he type — step 1 of 3 The fleet-wide `file-it-and-move-on` block told agents to file "a `Feedback/Feedback` node on the control instance" and never said where. Agents read the namespace off the type: they created at `Feedback/<id>`, `Feedback/_Submissions/<id>` and `Feedback/Inbox/<id>`, got the by-design `Access denied: Create permission required`, and dropped the finding. Measured in agent transcripts 2026-09-20..25 (twelve sessions), the last one AFTER #5172 put the namespace on Doc/Architecture/IncidentalFindings — that page is not in an agent's context; this block is. The block now says: create with `namespace: "{user}/Feedback"` on the `systemorph` MCP server, the three refused namespaces are refused by design and are no reason to drop a finding, omit `status`, no `@` in the message, and read the node back — the read is the wake the hand-over waits on. A text change to a slot-less block cannot land green in one step (the gate runs only in core and reads the spokes' default branches), so this lands like an addition: required-in narrowed to the hub here, the six spokes copy the text, then required-in widens back. SharedRuleBlocks.md now documents that order; it previously stated one that could not go green. Verified: check-shared-rules.py self-test 18/18; live sweep green with this register; red control with main's register names all six spokes DRIFTED; MeshWeaver.Documentation.Test 649/649, 0 warnings under -c Release -warnaserror. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Copilot review overview
🟢 Approval recommended
Final findings are minor documentation nits with no blocking issues.
Review effort: Lite
Findings: None
What changed in this PR
Updates triage-filing guidance with the correct user namespace and documents the staged shared-rule rollout.
Changes:
- Clarifies feedback filing and verification steps in
AGENTS.md. - Temporarily narrows shared-rule validation to core.
- Documents the three-step rollout.
- Expands refused namespace documentation.
| File | Summary |
|---|---|
src/MeshWeaver.Documentation/Data/Architecture/SharedRuleBlocks.md |
Documents staged shared-rule changes. |
src/MeshWeaver.Documentation/Data/Architecture/IncidentalFindings.md |
Clarifies refused feedback namespaces. |
AGENTS.md |
Adds precise triage filing instructions. |
.github/shared-rules.json |
Narrows validation during rollout. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Contributor
Contributor
Contributor
Contributor
Contributor
Contributor
Contributor
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.
Why agents got
Create permission requiredwhen filing into triageThe fleet-wide
file-it-and-move-onblock in everyAGENTS.mdtold agents to file "aFeedback/Feedbacknode on the control instance" and never said where. Agents took the namespace from the type. They created atFeedback/<id>,Feedback/_Submissions/<id>orFeedback/Inbox/<id>. All three answerAccess denied: Create permission requiredby design, and the agents dropped the finding.Measured by grepping this machine's agent transcripts for the refusal. Twelve sessions between 2026-09-20 and 2026-09-25 hit it, and every refused path was one of those three namespaces. None was
{user}/Feedback/…. The newest case (2026-09-25) came after #5172 had put the namespace onDoc/Architecture/IncidentalFindings. That session triedFeedback, thenFeedback/Inbox, and gave up, so the finding was never filed. The doc page is not in an agent's context. This block is.The route works. On memex.systemorph.com today (core
45e7f94e),rbuergi/Feedback/notification-config-per-application-20260926was created byrbuergi. It was handed over at 18:15:17Z, landed asHosting/PlatformBuilds/_Inbox/bc328f15…(event: feedback) and becameHosting/Triage/feedback/memex-systemorph-com-rbuergi-feedback-notification-config-per-application-20260926at 18:17Z.What changed
AGENTS.md, blockfile-it-and-move-onnow tells agents:namespace: "{user}/Feedback"on thesystemorphMCP server (notmemex);status, since sending"New"round-trips as absent;@in the message;.github/shared-rules.json: step 1 of 3. A text change to a block with no slots cannot land green in one step. The gate runs only in core and reads the spokes' default branches, so the hub's PR is red until the spokes change, and a spoke that changes first reddens every core PR. This change therefore narrowsrequired-into the hub and adds awhyline saying the change is in flight. Next come the six spoke PRs, then a core PR that widensrequired-inagain.SharedRuleBlocks.md: "Changing the text of one" used to prescribe an order that cannot go green. It now documents the three steps.IncidentalFindings.md: addsFeedback/Inbox/{id}to the list of refused namespaces, and notes why the page alone did not fix this.Verification
check-shared-rules.py --self-test: 18/18 correct.--local Systemorph/MeshWeaver=AGENTS.md): all 6 blocks identical everywhere they are carried.file-it-and-move-onis now compared in 1 repo.DRIFTEDand exits 1. That is why the narrowing is needed.MeshWeaver.Documentation.Test: builds with 0 warnings and 0 errors under-c Release -warnaserror; 649/649 passed.Docs, rules and the register only. No source changes. No catalog keys.
Pairs-with: none — no public surface touched
Mirror-sync: none — no catalog key added or changed
Refs #5670 (the feedback-path cluster), #5172.
🤖 Generated with Claude Code