The modes a Mold may declare are the two that ship - #39
Merged
Conversation
Retiring condensation left the mode list needing one fewer term. It got two more instead: `inlined` and `bundled` appear in no package and no instance, and `verbatim` — the mode both corpora use for nearly every reference — dropped out of the sentence naming them. The provenance example went further and invented a key, `"placement"`, where the record writes `mode`. The shipped vocabulary is verbatim and sidecar. This page is where a reader is sent to learn that: reference-contract's spec_url points into this site, so prose here is the definition, not a gloss on one. `placement mode` is kept, and is now the better name. Nothing transforms a reference any more — both surviving modes carry it unchanged, one as its own bytes and one as a structured artifact built from them. That is what makes a cast reproducible byte for byte, which is the claim the same page now makes two paragraphs earlier. The standing-up instructions were the costly copy: they told a third Foundry to expect four placement rules, half of them nonexistent, in the paragraph telling it to narrow the group to what its targets implement. 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 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.
Follow-on to the casting-determinism rewrite (#37,
2aff6b7), which was right to retire condensation and got the replacement vocabulary wrong.The mode list needed one fewer term. It gained two:
inlinedandbundledappear in no package and no instance, andverbatim— the mode both corpora use for nearly every reference — dropped out of the sentence naming them. The provenance example inthe-model.mdalso invented a key,"placement", where the record writesmode.The shipped vocabulary is
verbatimandsidecar(@galaxy-foundry/reference-contract). This site is where a reader is sent to learn that —reference-contract.yml'sspec_urlpoints intocontent/pattern/, so prose here is the definition rather than a gloss on one.What is kept
placement mode— and it is now the better name. Nothing transforms a reference any more; both surviving modes carry it unchanged, one as its own bytes and one as a structured artifact built from them. That is exactly what makes a cast reproducible byte for byte, which is the claimthe-model.mdnow makes two paragraphs earlier. The rename was the right instinct; only the enumeration was wrong.Five places
the-model.md"placement": "bundled"/"inline"verbatim/sidecar;"mode": "verbatim"standing-up-a-foundry.instructions.txt04-fair-skills.mdverbatimorsidecar)"guiding-principles.mdglossary.mdprompt(inlined)prompt(copied verbatim)The instructions file was the costly one: it told a third Foundry to expect four placement rules, half of them nonexistent, inside the paragraph telling it to narrow the group to what its targets implement.
22 tests pass, site builds 29 pages.
Related
jmchilton/foundry-lib#49 removes
condensefrom the shared vocabulary, which is what makes "the two that ship" true rather than "the two that ship, plus one nobody implements." The two PRs are independent — this one describes what instances declare today either way.Follow-up, not in this PR
reference-contract.yml'sspec_urlpoints atanatomy-of-an-instance.md, and that page never lists the five vocabularies. The package sends readers to a page that does not define its terms; the definitions are onthe-model.mdandglossary.mdinstead. Either the pointer moves or the page gains the list.🤖 Generated with Claude Code