Full Index

Every note in the Foundry.

A directory-grouped map of content notes, reference material, and generated navigation surfaces.

Notes
242
Dirs
9

cli/ (32)

meta/ (16)

molds/ (47)

patterns/ (54)

pipelines/ (7)

prompts/ (2)

research/ (63)

schemas/ (14)

source-patterns/ (7)

docs/ (16)

Foundry design records

  • Guiding Principles design record The design pressure behind source authority, progressive disclosure, validation, portability, and corpus grounding.
  • Architecture Map design record A short map of the Foundry's major parts, boundaries, and focused architecture records.
  • Molds design record The axes a Mold buckets on, the boundary against reference content, and where the Mold set is still uneven.
  • Mold Spec design record The Mold authoring contract: source layout, which files may sit beside index.md, and who enforces it.
  • Compilation Pipeline design record How typed Mold references become target-specific cast artifacts with provenance.
  • Cast Walkthrough design record One real committed cast (discover-shed-tool) annotated end to end: every bundle file traced back through per-kind dispatch and _provenance.json.
  • Eval Philosophy design record Why eval.md is an abstract oracle and scenarios.md holds the concrete cases, and the eval/scenario/refinement split.
  • Corpus Integration design record How IWC grounding works without turning the Foundry into an upstream workflow mirror.
  • Harness Pipelines design record The source-to-target journeys that compose Molds, loops, and branch phases.

Project infrastructure research

  • Comparisons project infrastructure Where the Foundry sits versus wikis, skill bundles, and the KB-to-skill landscape (MCP, Agent Skills, llms.txt, Corpus2Skill, RAG) — a dated snapshot.
  • Pattern Authorship Policy project infrastructure Developer-facing authorship rules for operation-named, corpus-grounded pattern pages.
  • Schema Packages project infrastructure Where a Mold IO schema lives, how cast resolves one through a schema note, and why there is no separate schema package.
  • Code Architecture project infrastructure Implementation components, dependency direction, entry points, and contracts across the Foundry codebase.
  • Content Model project infrastructure How Foundry notes, kinds, metadata, tags, links, references, and companions represent knowledge.
  • Build and Validation project infrastructure How authored Foundry source is checked, generated, cast, assembled, rendered, and kept current.
  • Repository Layout project infrastructure Where authored source, implementation code, generated artifacts, fixtures, and site files belong.