Evaluated demonstrations and case studies for the Source Engineering discipline.
This repository holds the discipline's empirical evidence. A case study is a documented demonstration of the discipline's value in a specific domain, with a hypothesis, a method, data, findings, and a conclusion. The case studies are the discipline's proof: every claim the discipline makes is either a principle (in source-engineering-foundations) or an empirical finding (here).
template.md- the canonical template. Every case study follows this structure.2026-legal-summarization/- the discipline's first case study. A worked example in the legal domain.how-to-file-a-case-study.md- the process for contributing a new case study.
- Read the template first.
template.mdnames the sections every case study must include. - Then the first case study.
2026-legal-summarization/is the worked example. - Propose a new case study by opening an issue and following the process in
how-to-file-a-case-study.md.
The first case study is the legal-summarization study. Its protocol is pre-registered in Source-Engineering/source-engineering-research/protocols/legal-summarization-evaluation.md. The case study documents the protocol's expected findings, the data the protocol would produce, and the conclusions the discipline can draw.
This is the adoption slice (Phase 4). The template and the first case study are seeded. New case studies are added via the case-study process; each new case study is a new finding in the discipline's evidence base.
Apache-2.0. See LICENSE.