Uh oh!
There was an error while loading. Please reload this page.
Correct the roadmap status and stop duplicating it - #1
Merged
Conversation
The roadmap here said Core was "in development" and probabilistic matching was still ahead, while both had shipped in the core repo. It drifted because it restated a list that lives somewhere else — two copies of the same facts, only one of which anyone updates while working. So this stops restating it. The profile now names the current phase in a sentence and links to the roadmap in the core repo, which is the copy that gets maintained because it sits next to the code it describes. Also adds a short paragraph on how matching decides. For an identity graph that is the first thing a visitor wants to know, and the most reassuring fact about it — that automatic fuzzy merging ships off — was previously visible only to someone reading the specs. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
"Original data is sacred" was the only untestable bullet among four testable ones, restated "immutable" less precisely, and carries a religious connotation that travels badly for an international audience. The replacement states the consequence an integrator needs — corrections arrive as new records, never as edits — instead of an attitude toward the data. Matches the same change in the core repo. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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 freeto 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.
The roadmap here says Core is "🚧 in development" and lists probabilistic matching as still ahead. Both shipped some time ago, and the guest timeline is in review now — so this page has been telling visitors the project is roughly two phases behind where it is.
It drifted because it restated a roadmap that also lives in the core repo. Two copies of the same facts, and only one of them gets touched while working. So rather than re-syncing it, this removes the duplication: the profile names the current phase in a sentence and links to the roadmap in the core repo, which stays current because it sits next to the code.
Also adds a short paragraph on how matching decides. For an identity graph that is the first question a visitor has, and the most reassuring fact about GuestGraph — that automatic fuzzy merging ships off, with the threshold at 1.0 and fuzzy scores capped below it — was previously visible only to someone willing to read the specs.
Two things in this change only become true when that PR lands:
docs/matching.mdlink 404s until then — the file is on the slice-3 branch.Both are accurate the moment #17 merges. Holding this until then is the simplest way to avoid a broken link on the org landing page.
🤖 Generated with Claude Code