Shared substrate · local expression
The shared cases come from @galaxy-foundry/site-kit; this page supplies no
alternate palette. Every header, note frame, reference card, and licence surface below is
therefore wearing the same warm editorial system as the rest of the TDA Foundry.
Beside them are the pieces that belong here alone: filtration, persistence-barcode punctuation, point-cloud fingerprints, graph-like breadcrumbs, and this corpus's own reference kinds.
Component groups supplied and maintained by site-kit.
Groups derived from TDA vocabulary and local visual components.
The invariant page frame around an instance-specific typed note.
Most corpus notes already begin with H1; the frame supplies navigation, summary, tags, and the article boundary without duplicating it.
content-note/body-heading A package profile whose Markdown body owns its title.
A short note body makes the frame visible without inventing a second content model for the gallery.
A design record whose body starts directly in prose asks the shared frame to render its title and summary.
content-note/frame-heading Why content mechanics are shared and the content model is local.
A short note body makes the frame visible without inventing a second content model for the gallery.
Controlled vocabulary shown as links only when an instance has a browse route.
An established content site links each chip through the one route prefix the instance supplies.
tag-chips/linked A partial content site shows controlled metadata without claiming a destination it has not built.
tag-chips/unlinked A note's typed reference manifest, rendered against the contract it was authored under.
The baseline: a kind with a destination, four inherited chips, no authored prose.
reference-contract/one-reference Typed references describe what casting consumes, and when the generated skill should load each artifact.
The authored note a skill is cast from.
Purpose, trigger and verification are the author's prose, not vocabulary. They open the detail list under the chips.
reference-contract/authored-detail Typed references describe what casting consumes, and when the generated skill should load each artifact.
The authored note a skill is cast from.
The kind pill is a link only when its term carries an href. Without one it is a span — because an anchor with no href is not focusable, not clickable, and announced as plain text, while wearing the same pill styling as the real links beside it.
reference-contract/kind-without-destination Typed references describe what casting consumes, and when the generated skill should load each artifact.
Background synthesis an instance holds but does not publish.
The chip is coloured by the standing its term DECLARES, not by a list of term names in a selector. `hypothesis` also requires a verification, and the detail row wears the same standing's colour.
reference-contract/provisional-evidence Typed references describe what casting consumes, and when the generated skill should load each artifact.
The authored note a skill is cast from.
A resolver returning a target with no href means the note is named and not there. It renders as marked text rather than as a link to nowhere.
reference-contract/dangling-ref Typed references describe what casting consumes, and when the generated skill should load each artifact.
The authored note a skill is cast from.
Should never reach a page — the schema refuses it at build. If one does, it renders as itself with the reason attached, rather than throwing on a reader or rendering as a blank chip that looks like a term with a short label.
reference-contract/unregistered-term Typed references describe what casting consumes, and when the generated skill should load each artifact.
The authored note a skill is cast from.
The grid is auto-fit at a 17rem minimum, so how many columns appear is decided by the width the gallery gives it and not by the count. Narrow the window here.
reference-contract/several-references Typed references describe what casting consumes, and when the generated skill should load each artifact.
The authored note a skill is cast from.
Background synthesis an instance holds but does not publish.
The authored note a skill is cast from.
Background synthesis an instance holds but does not publish.
The component renders NOTHING — not an empty card, not a heading with an empty grid. A note with no typed references gets no section, so this specimen is deliberately blank and the gallery should say so rather than look broken.
reference-contract/no-references What a licence permits, as chips, from the id a note declares.
The baseline. `MIT` is also 1 of the 23 rows whose name equals its id, which is why rendering the id instead of the name looked right for sixteen notes.
license-badge/verbatim-ok The third chip appears only when the row calls for it. Copyleft is a property of the licence and not of the policy — a reader has to be able to see both at once.
license-badge/copyleft The chip that has to be distinguishable from `verbatim OK` at a glance, because it means the opposite thing. Its colour is a token: as a raw hex in two repositories nothing could change it and nothing could break it either.
license-badge/own-words-only Why the badge renders `name` rather than the id: `LicenseRef-arXiv-nonexclusive-distrib-1.0` is a pill that teaches a reader nothing. The id stays reachable as the chip's title.
license-badge/custom-ref The same deny-by-default policy as the specimen below, and deliberately not the same name. This licence IS resolved — an author identified it and used the escape hatch — so labelling it `unresolved / missing` reports a real licence as an absent one, and reproaches the note that did the right thing. Its terms are still unknown, which is why the policy chip does not soften.
license-badge/uncurated-ref Deny-by-default, rendered. An unknown id resolves to the default row — own-words-only, flagged a defect — rather than to a gap, because a conservative chip beats a blank where a licence should be.
license-badge/unresolved What one vendored licence copy governs, who redistributes under it, and its text.
The baseline, and the URLs in the text are the case worth looking at: a licence is the one document a reader most plausibly wants to leave, and the canonical terms are what they are leaving for.
license-file-body/one-license CC-BY-4.0 verbatim OK
attribution (title/author/source/license/changes)
Permission is granted to redistribute this text verbatim. The canonical terms are at https://creativecommons.org/licenses/by/4.0/ and questions go to https://example.org/contact — this copy is a courtesy.
A copy is keyed by SOURCE, so what it governs has more than one answer: the users' own ids, deduped and resolved. Both instances derived this the same way, which is why the derivation ships rather than the list.
license-file-body/several-licenses Apache-2.0 verbatim OK
attribution + notice + preserve NOTICE
MIT verbatim OK
attribution + license notice
Permission is granted to redistribute this text verbatim. The canonical terms are at https://creativecommons.org/licenses/by/4.0/ and questions go to https://example.org/contact — this copy is a courtesy.
The policy section disappears entirely rather than rendering empty. Nothing was resolved because nothing was declared, and a row of chips derived from no ids would be an answer the notes never gave.
license-file-body/no-declared-license Permission is granted to redistribute this text verbatim. The canonical terms are at https://creativecommons.org/licenses/by/4.0/ and questions go to https://example.org/contact — this copy is a courtesy.
The other half of the URL cut. Everything outside a match is emitted verbatim, whitespace included — reflowing a redistributed licence is exactly what the obligation forbids.
license-file-body/no-links-in-the-text LicenseRef-all-rights-reserved own-words only
citation only
All rights reserved.
Reproduced here by permission. Every reference kind this Foundry declares, derived from its contract so a new kind cannot arrive unseen.
A runnable biopixi fixture and its declared bundled companions.
tda-reference-kinds/environment Typed references describe what casting consumes, and when the generated skill should load each artifact.
A runnable biopixi fixture and its declared bundled companions.
A deterministic barcode used as punctuation between conceptual sections.
One interval receives the persistent accent, turning a divider into domain-specific hierarchy without adding prose.
tda-persistence-divider/section-punctuation Seeded geometric marginalia that gives each surface a stable visual fingerprint.
The same semantic seed always yields the same points, neighborhood edges, and highlighted loop.
tda-point-cloud-fingerprint/stable-fingerprint The dark bar: wordmark, derived navigation, search box, theme toggle. Its isolated surface receives a real route rather
than a second copy on this document.
No "More" button, and the overflow script is not shipped at all — an instance whose destinations all fit is the intended state, not a stub.
site-header/everything-fits One list and a cut point, not two lists: which destinations exist and which of them fit are different questions, and only the second is about the header's width.
site-header/overflows The "More" button itself lights up when the reader is inside a destination it holds — otherwise the section they are in has no marker anywhere on the bar.
site-header/active-under-more A destination is active on its own page and on everything beneath it, so a note page keeps its section marked.
site-header/active-below-a-section Compared on whole path segments: on `/tags/`, a `/tag/` destination stays dark. String-prefix matching lights up both, and the bug is invisible until an instance happens to own both routes.
site-header/sibling-prefix Why `navVisible` is not a number to copy from a sibling instance: the same count that fits beside "Foundry" wraps beside a longer name. Measure it against a built page.
site-header/long-wordmark The whole document: head, header, the reading column, footer. Its document surface receives a real route rather
than a second copy on this document.
The default, and defaulted TRUE on purpose: `<main>` carries the Pagefind attribute. Marking one page is what removes every unmarked page from the index, so a route one forgotten prop away from unfindable is the failure this default exists to refuse.
site-shell/searchable Opting out is per page and is the only thing that makes an absence a decision. A gallery route is itself a fair candidate — its text is component names and prop values, which nobody is searching the corpus for.
site-shell/unsearchable The interactive frontispiece: a point cloud becomes a complex and leaves one persistent loop. Its isolated surface receives a real route rather
than a second copy on this document.
The range control makes filtration tangible while the copy connects multiscale structure to the Foundry workflow.
tda-filtration-hero/stable-loop