Gallery

Every case @galaxy-foundry/site-kit says its components handle, rendered here in this instance's theme. The props come from the package; the colours, the type and the spacing are ours. A sibling Foundry running the same specimens gets a different page from the same data.

ReferenceContract

A note's typed reference manifest, rendered against the contract it was authored under.

A single reference

The baseline: a kind with a destination, four inherited chips, no authored prose.

contract

Reference Loading

Typed references describe what casting consumes, and when the generated skill should load each artifact.

With authored detail

Purpose, trigger and verification are the author's prose, not vocabulary. They open the detail list under the chips.

contract

Reference Loading

Typed references describe what casting consumes, and when the generated skill should load each artifact.

A kind with nowhere to go

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.

contract

Reference Loading

Typed references describe what casting consumes, and when the generated skill should load each artifact.

Provisional evidence

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.

contract

Reference Loading

Typed references describe what casting consumes, and when the generated skill should load each artifact.

A ref that resolves to nothing

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.

contract

Reference Loading

Typed references describe what casting consumes, and when the generated skill should load each artifact.

A term outside the vocabulary

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.

contract

Reference Loading

Typed references describe what casting consumes, and when the generated skill should load each artifact.

Several references

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.

contract

Reference Loading

Typed references describe what casting consumes, and when the generated skill should load each artifact.

No references

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.

ReferenceContract

Every kind this instance declares, one card each. The accent bar is ours — `global.css` names three of them, and the rest take the brand fallback. Which is which is visible here and nowhere else.

Pattern

Workflow-construction idiom. Copied verbatim.

contract

Reference Loading

Typed references describe what casting consumes, and when the generated skill should load each artifact.

CLI Tool

Tool-level install metadata. Aggregated into the cast bundle's Required Tools section.

contract

Reference Loading

Typed references describe what casting consumes, and when the generated skill should load each artifact.

CLI Command

Command reference. Usually cast to a sidecar and loaded only when invoked.

contract

Reference Loading

Typed references describe what casting consumes, and when the generated skill should load each artifact.

Schema

Structured contract copied for validation or lookup.

contract

Reference Loading

Typed references describe what casting consumes, and when the generated skill should load each artifact.

Prompt

Prompt fragment copied verbatim or inlined by the target adapter.

contract

Reference Loading

Typed references describe what casting consumes, and when the generated skill should load each artifact.

Example

Fixture or exemplar copied verbatim.

contract

Reference Loading

Typed references describe what casting consumes, and when the generated skill should load each artifact.

Research

Background synthesis loaded by explicit progressive-disclosure metadata.

contract

Reference Loading

Typed references describe what casting consumes, and when the generated skill should load each artifact.

LicenseBadge

What a licence permits, as chips, from the id a note declares.

Redistributable

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.

MIT verbatim OK

Redistributable, and copyleft

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.

GPL 3.0 verbatim OK copyleft

Not redistributable

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.

CC BY-NC 4.0 own-words only

A LicenseRef, not an SPDX id

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.

arXiv non-exclusive distribution 1.0 own-words only

A LicenseRef nobody has curated

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.

yale-non-commercial own-words only

An id the table does not have

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.

unresolved / missing own-words only

LicenseFileBody

What one vendored licence copy governs, who redistributes under it, and its text.

One copy, one licence

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.

CC-BY-4.0 verbatim OK

attribution (title/author/source/license/changes)

Redistributed by (2)

License text

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.

One copy, several licences

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.

Apache-2.0 verbatim OK

attribution + notice + preserve NOTICE

MIT verbatim OK

attribution + license notice

Redistributed by (3)

License text

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.

Users that declare no id

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.

Redistributed by (1)

License text

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.

TagChips

Controlled vocabulary shown as links only when an instance has a browse route.

Browsable tags

An established content site links each chip through the one route prefix the instance supplies.

Tags before browse exists

A partial content site shows controlled metadata without claiming a destination it has not built.

NoteHeader

What sits above a note: where you are, what kind of thing this is, and what it says.

Everything a note can carry

The flagship shape — kind, status, tags, and a published source — so the vertical rhythm between five stacked rows is visible in one place.

Design records Design Record

Persistent homology of expression manifolds

Why the filtration is built on correlation distance rather than Euclidean distance.

Raw

A kind that carries neither status nor tags

Two of six kinds in the adopting instance declare a status, and a kind off the tag surface renders no chips — so the sparse header is the common case, not the degenerate one.

Mold

Reading a Mold

A status the instance has no rule for

Status is `data-status`, so the vocabulary is the instance’s. A value it has not styled has to stay legible rather than disappear — which is what makes adding one cost no release here.

Design Record

Superseded approach to filtration

ContentNote

The invariant page frame around an instance-specific typed note.

Body owns its heading

Most corpus notes already begin with H1; the frame supplies navigation, summary, tags, and the article boundary without duplicating it.

Packages Package

A package profile whose Markdown body owns its title.

Frame owns its heading

A design record whose body starts directly in prose asks the shared frame to render its title and summary.

Design Record

Content-reader architecture

Why content mechanics are shared and the content model is local.

KindCatalog

One Foundry’s generated kind inventory, resolved into its own route space and corpus.

Substrate and instance kinds

The index groups by the layer each kind declares, keeps source order within a layer, and exposes shape, field, companion, location, and corpus facts without turning them into a card wall.

Declared
3
Substrate
1
Instance
2
01

Shared substrate

Kinds this Foundry declares as part of the transferable Foundry structure.

  1. Mold mold

    One repeatable action, authored here and cast into a target-specific artifact.

    Lives in content/molds

    Shape
    directory
    Fields
    3 req · 1 opt
    Companions
    2
    Corpus
    47 Molds
02

Instance vocabulary

Kinds introduced for this Foundry’s own domain and operating model.

  1. Package package

    A profile of external software and the evidence supporting its use here.

    Lives in content/packages

    Shape
    file
    Fields
    3 req · 1 opt
    Companions
    0
    Corpus
    Packages
  2. Research note research

    Background synthesis whose source files are intentionally an open companion set.

    Lives in content/research

    Shape
    directory
    Fields
    2 req · 0 opt
    Companions
    0 + open set

No kinds declared

An empty manifest says so directly rather than leaving a blank region that looks like a failed data load.

This Foundry declares no kinds.

SiteShell

The whole document: head, header, the reading column, footer. Each is a page of its own — document means it cannot share this one — so the frames below are the real routes, at whatever width this column gives them.

A page in the index

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.

A page kept out of the index

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.

KindReference

The complete generated contract for one kind, with instance-resolved navigation around it. Each is a page of its own — isolated means it cannot share this one — so the frames below are the real routes, at whatever width this column gives them.

Directory kind with a worked example

The full case: required and optional fields, companion dispositions, live corpus count, escaped example source, and generated-source provenance.

Flat kind before examples are published

The manifest format permits an absent example, so the reference says what is missing without hiding the rest of the contract.

An open companion set

Zero declared companions plus `allow` is not rendered as no companions; the open-set fact remains explicit in the ledger and layout.