Repository navigation
docs: stage the RUMI manifest and answer refused inputs in kind - #7
Merged
Merged
Conversation
Fill .rumi/manifest.json in two stages: the vault stage writes the RUMI-owned vault fields (vault id, vault format version, last RUMI version), and the LINA link stage adds the declaration object from the schema in LINA's sibling tag. LINA picks the RUMI row by the declaration's product version. Answer a refused or failed input with the kind that answers it, picked from the input's path: add for an inbox item, brief for a request, with no content and with effect_state and error. Unsupported envelope versions are answered the same way. Take the kit's web fetch tool with its document parsing from LINA's sibling tag, add the sender to the shared inbox front matter, and have RUMI define the Open in RUMI link format with LINA in the RUMI app stage. 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. |
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
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
Closes the RUMI side of the second canon review across LINA, SION and RUMI, in
docs/design/rumi.md:rumiprotocol versions, capabilities) from LINA's schema for sibling declarations, which LINA's sibling tag carries. When RUMI writes the declaration, its product version is the RUMI release in charge of the vault, and LINA selects the RUMI row of its supported-combination table by it. Layout, CLI status and the envelope section follow.addfor aninbox/item,brieffor arequest. The record carries none of its kind's content, only the input it answers,effect_stateanderror. An input at an unsupported envelope version is answered the same way.rumipayload schemas and fixtures, the declaration schema, and document parsing with the web fetch tool, passage anchors and citation checks.LINA's host protocol, materials and surfaces contracts take the matching wording in a separate LINA PR.
Verification
node .github/scripts/check-docs.mjs: passed.node --test .github/scripts/*.test.mjs: 28 passed, 0 failed.git diff --check: clean.#anchor inrumi.mdwith a script: all resolve. No headings changed, and no other document links to an anchor inrumi.mdother than#repository-and-releases, which is unchanged.Compatibility and recovery
Contract text only. No code, data or configuration changes.
🤖 Generated with Claude Code