ch · studies

Pinned reading,
not paraphrase.

Each study scopes one domain question and pins upstream code as nested git submodules. We read from the pinned source — not from training data, not from a paraphrase, not from a blog post that aged out a year ago.

  • 3 studies
  • 0 pinned repos
  • read from source

study · 01

Open Specs & Standards

study · 02

Memory Layers for Agents

study · 03

Data-Analytics Specs & Standards

ch · why pin

Why pin upstream code instead of bookmarking it?

grounded

The agent reads source, not training-data folklore.

When a decision touches a convention someone else already worked out, the answer comes from the pinned repo — not from whatever the model half-remembers.

stable

SHA-pinned. Doesn't rot under us.

A study's submodule points at a specific commit. When we revisit a study six months later, the same source is still there. Upgrades are explicit, not silent.

scoped

One study, one question.

Studies are not a general reading list. Each one scopes a single domain question and pins only what helps answer it. New questions get new studies, not pile-ons.