Shared component

KindCatalog

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

Shared case

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.

kind-catalog/mixed-inventory

Declared: 3
Substrate: 1
Instance: 2

01

Shared substrate

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

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.

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
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

Shared case

No kinds declared

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

kind-catalog/empty-inventory

This Foundry declares no kinds.

Shared component

NoteHeader

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

Shared case

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.

note-header/full

Design records Design Record

Persistent homology of expression manifolds

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

reviewed method/persistent-laplacian scale/single-cell

Raw

Shared case

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.

note-header/minimal

Mold

Reading a Mold

Shared case

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.

note-header/unstyled-status

Design Record

Superseded approach to filtration

retracted method/persistent-laplacian

Shared component

ContentNote

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

Shared case

Body owns its heading

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

content-note/body-heading

Packages Package

A package profile whose Markdown body owns its title.

method/persistent-laplacian

A short note body makes the shared frame visible without inventing a second content model for the gallery.

Shared case

Frame owns its heading

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

content-note/frame-heading

Design Record

Content-reader architecture

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

A short note body makes the shared frame visible without inventing a second content model for the gallery.

Shared component

TagChips

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

Shared case

Browsable tags

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

tag-chips/linked

method/persistent-laplacian

Shared case

Tags before browse exists

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

tag-chips/unlinked

method/persistent-laplacian

Shared component

ReferenceContract

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

Shared case

A single reference

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

reference-contract/one-reference

contract

Reference Loading

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

Mold Trimming reads

The authored note a skill is cast from.

Runtime Upfront Verbatim Cast Validated

Shared case

With authored detail

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

reference-contract/authored-detail

contract

Reference Loading

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

Mold Trimming reads

The authored note a skill is cast from.

Both On Demand Sidecar Corpus Observed

Purpose: Supplies the parameter table the generated skill fills in.
Trigger: The user asks to trim reads.

Shared case

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

contract

Reference Loading

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

Research Trimming reads

Background synthesis an instance holds but does not publish.

Cast Time Upfront Verbatim Corpus Observed

Shared case

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.

reference-contract/provisional-evidence

contract

Reference Loading

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

Mold Trimming reads

The authored note a skill is cast from.

Runtime Upfront Verbatim Hypothesis

Verify: Cast the skill and check the parameter table survives the round trip.

Shared case

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.

reference-contract/dangling-ref

contract

Reference Loading

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

Mold a-note-that-moved

The authored note a skill is cast from.

Runtime Upfront Verbatim Corpus Observed

Shared case

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.

reference-contract/unregistered-term

contract

Reference Loading

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

Mold Trimming reads

The authored note a skill is cast from.

Runtime Upfront Verbatimvibes

Shared case

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.

reference-contract/several-references

contract

Reference Loading

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

Mold Trimming reads

The authored note a skill is cast from.

Runtime Upfront Verbatim Cast Validated

Research a-note-that-moved

Background synthesis an instance holds but does not publish.

Cast Time Upfront Sidecar Corpus Observed

Mold Trimming reads

The authored note a skill is cast from.

Both On Demand Verbatim Hypothesis

Trigger: A workflow declares a trimming step.
Verify: Confirm the step appears in a cast run.

Research Trimming reads

Background synthesis an instance holds but does not publish.

Runtime Upfront Sidecar Cast Validated

Shared case

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.

reference-contract/no-references

Shared component

LicenseBadge

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

Shared case

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.

license-badge/verbatim-ok

MIT verbatim OK

Shared case

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.

license-badge/copyleft

GPL 3.0 verbatim OK copyleft

Shared case

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.

license-badge/own-words-only

CC BY-NC 4.0 own-words only

Shared case

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.

license-badge/custom-ref

arXiv non-exclusive distribution 1.0 own-words only

Shared case

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.

license-badge/uncurated-ref

yale-non-commercial own-words only

Shared case

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.

license-badge/unresolved

unresolved / missing own-words only

Shared component

LicenseFileBody

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

Shared case

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.

license-file-body/one-license

CC-BY-4.0 verbatim OK

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

Redistributed by (2)

trimming-reads CC-BY-4.0
aligning-reads CC-BY-4.0

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.

Shared case

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.

license-file-body/several-licenses

Apache-2.0 verbatim OK

attribution + notice + preserve NOTICE

MIT verbatim OK

attribution + license notice

Redistributed by (3)

a-note MIT
another-note Apache-2.0
a-third-note MIT

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.

Shared case

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.

license-file-body/no-declared-license

Redistributed by (1)

a-note-with-no-license

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.

Shared case

Text with nothing to leave for

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

Redistributed by (1)

a-manuscript LicenseRef-all-rights-reserved

License text

All rights reserved.

    Reproduced here by permission.

Shared component

SiteFooter

The closing bar: the copyright mark, the repository, and whatever else an instance links.

SGF component

ReferenceContract

Every reference kind this Foundry declares, derived from its contract so vocabulary changes become visible here automatically.

SGF case

Pattern

A statistical-method or invalidity pattern page. Carried verbatim into casts.

sgf-reference-kinds/pattern

contract

Reference Loading

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

Pattern [[gallery-pattern]]

A statistical-method or invalidity pattern page. Carried verbatim into casts.

Runtime Upfront Verbatim Corpus Observed

SGF case

Research

Background synthesis from a source note, loaded by explicit progressive-disclosure metadata.

sgf-reference-kinds/research

contract

Reference Loading

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

Research [[gallery-research]]

Background synthesis from a source note, loaded by explicit progressive-disclosure metadata.

Runtime Upfront Verbatim Corpus Observed

SGF component

SourceMeta

Corpus provenance, redistribution posture, and source recovery kept together at the reading boundary.

SGF case

Own-words paper note

A real corpus record shows how restrictive source terms, citation, DOI, and derivation posture remain legible together.

sgf-source-meta/own-words-paper

SGF component

RefereeLoop

The Foundry thesis made spatial: Family A analyzes, Family B checks independently, and the gate either certifies or returns findings.

SGF case

Gate passes

A successful independent check ends in a clearly labelled certification state.

sgf-referee-loop/gate-passes

Family A Analyze Null-calibration check

Family B Referee Independent empirical check

Gate Certified Checks support the claim

SGF case

Revision required

A failed check makes the return path to analysis explicit instead of hiding it in prose.

sgf-referee-loop/revision-required

Family A Analyze Batch-confounding audit

Family B Referee Independent empirical check

Gate Revise Return with findings

Findings return to Family A

Shared component

KindReference

The complete generated contract for one kind, with instance-resolved navigation around it. Its isolated surface receives a real route rather than a second copy on this document.

Shared case

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.

kind-reference/directory-with-companions

Open kind-reference/directory-with-companions full width

Shared case

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.

kind-reference/flat-without-example

Open kind-reference/flat-without-example full width

Shared case

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.

kind-reference/open-companion-set

Open kind-reference/open-companion-set full width

Shared component

SiteHeader

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.

Shared component

SiteShell

The whole document: head, header, the reading column, footer. Its document surface receives a real route rather than a second copy on this document.

Shared case

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.

site-shell/searchable

Open site-shell/searchable full width

Shared case

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.

site-shell/unsearchable

Open site-shell/unsearchable full width