docs: the platform makes EVERYTHING addressable, not just code - #2078
Open
rbuergi wants to merge 1 commit into
Open
docs: the platform makes EVERYTHING addressable, not just code#2078rbuergi wants to merge 1 commit into
rbuergi wants to merge 1 commit into
Conversation
The page said the platform "makes code addressable", which undersells the mechanism and misdescribes it. Code is one of the things with an address; so are a domain record, a spreadsheet, an inbound e-mail, a schema, a business rule, a layout area, an agent, a skill, and every historical version of each. An address resolves to whatever answers it — not to code specifically. Says so, and states what falls out of it: an agent can be handed precisely the right context instead of a document dump, access control and audit are properties of the system rather than per-screen features, and "where does this value come from" has an answer. Heading, description, prose, figure seam text and aria-label all updated together so the page does not say two different things. Documentation link/embed integrity: 41 passed. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the “Platform and content” architecture page to correctly describe MeshWeaver’s core mechanism: the platform makes everything addressable (not just code), and resolves an address to whatever answers it—aligning the header, front-matter description, and the diagram’s accessibility text.
Changes:
- Reworded the front-matter
Descriptionand section heading to emphasize “everything addressable” and “resolves to whatever answers it”. - Expanded the opening prose to enumerate non-code addressable artifacts (data, documents, e-mail, schemas, rules, views, agents/skills, and historical versions).
- Updated the diagram’s
aria-labeland internal seam text to match the revised framing.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
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.
Follow-up to #2072.
That page said the platform "makes code addressable". That undersells the mechanism and, more importantly, misdescribes it — code is merely one of the things that has an address. So does a domain record, a spreadsheet, an inbound e-mail, a schema, a business rule, a layout area, an agent, a skill, and every historical version of each. An address resolves to whatever answers it.
Stating it correctly also lets the page say what falls out of it, which the narrower version could not:
Heading, front-matter description, opening prose, the figure's seam text and the
aria-labelare all updated together, so the page does not say two different things in two places.MeshWeaver.Documentation.Test— 41 passed, 0 failed.🤖 Generated with Claude Code