data(projects): correct tier-1 note + alchemy docs pointer (DOCS_LINKS) - #448
Merged
theboycoder merged 1 commit intoJul 10, 2026
Merged
Conversation
…(DOCS_LINKS) The previous commit's comment claimed the official tier-1-orgs page does not list Alchemy — boxy-corrected: it does (a text-strip curl of a data-rendered page produced a false negative; a negative grep over fetched HTML is not evidence of absence). New DOCS_LINKS fill-if-empty section records the policy answer to raven#18's ingest question: provider reference docs stay at SOURCE (they are already agent-readable — Alchemy ships llms.txt) and our records carry a first-class links.docs pointer instead of a staleness-prone corpus copy. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
@theboycoder is attempting to deploy a commit to the StellarLight Team on Vercel. A member of the Team first needs to authorize it. |
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.
Two things, both raven#18 follow-ups:
links.docs): the policy answer to "should we ingest partner docs?" is NO — provider reference docs are already agent-readable at source (Alchemy shipsllms.txt), a corpus copy would go stale (class 19) and duplicate what the provider serves. Our differentiated role: the structured record + a first-class pointer to the living source. First row:alchemy → alchemy.com/docs/reference/stellar-api-quickstart.Rollout: curate Action dry-run → execute → verify links.docs served.
🤖 Generated with Claude Code