Repository navigation
Say where the source lives: x-source, llms Source: and sameAs - #3
Draft
AgenteLabs wants to merge 1 commit into
Draft
AgenteLabs wants to merge 1 commit into
AgenteLabs wants to merge 1 commit into
Conversation
site.config.json's `links.repo` is the one place this repository already declares itself, so the build threads it into the derived handshake as `x-source` (a convention the flashyos/1 contract ignores; a handshake derived without a source carries no field rather than a guess) and into llms.txt as a `Source:` line. `site/` is regenerated. There is no Organization JSON-LD on this site — the FAQPage node is its only structured data — so there is no `sameAs` to carry. test/source.test.mjs holds the two built surfaces to the config and the config to flashyos's estate register when that checkout is beside this one. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01T2LtjRauY7RENs18aztY6V
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.
Every served property points machine readers at its source, three ways:
x-sourcein theflashyos/1handshake (a convention the v1 contract ignores, likedevelopers), aSource:line inllms.txt, and the GitHub organisation and repository in the page's OrganizationsameAs. The value is the CURRENT GitHub owner (AgenteLabs) as flashyos'sestate.register.jsonnames it — a URL that 404s is worse than none — and the orgsameAsis omitted where the organisation the master plan moves this repository to does not exist on GitHub yet. flashyos'stools/estate-source.mjs(AgenteLabs/flashyos#233) fetches and checks all three against the register.One constant per property; a test holds the three surfaces to it and compares it with the register when a flashyos checkout sits beside this repository (reported unknown, never passed, when it does not).
Only two of the three fields apply here: this site emits no Organization JSON-LD (FAQPage is its only structured data), so there is no
sameAsto carry. The value islinks.repofromsite.config.json, which still names FlashyLabs onmain(a GitHub rename redirect, not a 404) until the rename-sweep PR #1 lands; this PR reads it rather than typing a second copy.Generated by Claude Code