SDD frameworks
A Spec-Driven Development (SDD) framework is the workflow a project follows to go from an idea to shipped code: where specs live, how a change is proposed, designed, implemented and archived. OpenSpec and BMAD are two examples. Lore lets your org choose one, lets each project override it, and tells the AI which one applies.
A framework is a Scaffold
An SDD framework is distributed as a kind: Scaffold package that marks itself with spec.sddFramework: true:
apiVersion: lore.io/v1
kind: Scaffold
metadata:
namespace: acme
name: bmad-method
version: 2.1.0
spec:
title: BMAD Method
description: The BMAD workflow and its directory layout
sddFramework: true
content:
defaultLanguage: en-US
translations:
- en-USThe marker is valid only on kind: Scaffold; lore validate rejects it on any other kind. It changes nothing about how the Scaffold installs: lore pull still writes an instruction file plus a lore extract command. It only lets an org or a project pick the package as its framework, which a generic project starter or a Rule can’t be.
Lore publishes its own default, lore/openspec: OpenSpec’s directory layout and instructions to install and use the OpenSpec CLI.
Which framework applies
The effective framework is the first one set among:
| Layer | Where it’s set | |
|---|---|---|
| 1 | Flag | lore pull --sdd <namespace/name[:version]> |
| 2 | Project | sdd: in the nearest .lore/config.yaml |
| 3 | Org | The painel’s SDD Framework page |
| 4 | Default | lore/openspec |
The org’s choice
The org owner chooses the framework on the painel’s Settings → SDD Framework page, from the SDD-framework packages visible to the org, optionally with a version constraint. Every member can see it. Lore checks that the package exists, has a matching version, is visible to the org (public, or in one of the org’s namespaces) and is marked as an SDD framework. Reset returns the org to “not configured”, so projects without their own choice follow Lore’s default.
A project’s choice
A project overrides the org with one line in .lore/config.yaml:
sdd: acme/bmad-method:2 # or just acme/bmad-method for the latest versionThe CLI uses the nearest .lore/config.yaml that sets sdd, walking up from the current directory to the repository root, and never above it. In a monorepo, services/payments/ can follow one framework while the rest of the repository follows another. An invalid value is a warning, and the project layer is then skipped. The CLI never writes this file.
Applying it
lore pull # install the effective framework
lore pull --dry-run # show the resolution, install nothing
lore sdd status # show every layer and which one winslore pull with no package prints SDD framework: <package> (<layer>) and installs that Scaffold on every detected target, exactly as lore pull <package> would. It refuses a package that isn’t an SDD framework. When the Registry can’t be reached, the org’s choice comes from the last cached copy, and the CLI says so.
At session start
When the project or the org chose a framework, the governance hook adds one line after the org’s Rules:
[Org SDD] This project follows acme/bmad-method (set by the org acme). Use that workflow; if it isn't set up here, run `lore pull`.Lore’s default alone adds nothing, so an org that never chose a framework isn’t pushed into one. The line counts against the hook’s context budget like a Rule and is never cut. MCP-only surfaces (claude.ai, ChatGPT) don’t receive it: choosing a framework is about the files in a repository.
SDD framework vs. mandatory packages
These are two different org policies, on two different painel pages.
| Mandatory packages | SDD framework | |
|---|---|---|
| Shape | A list: every entry is delivered | One value: a new choice replaces the old one |
| Packages | Rules and Skills | One kind: Scaffold with spec.sddFramework: true |
| Projects | Project globs narrow an entry | A project’s .lore/config.yaml replaces the org’s choice |
| Delivered | Every session (hook and MCP) | lore pull, and one line at session start (hook only) |
Lore checks which framework a project should follow, not whether the repository actually follows it.