lore sdd
Show which Spec-Driven Development framework governs the current directory, and why.
Usage
lore sdd status [--org <org>] [--json]Description
Prints each layer of the SDD framework chain: the project’s value (from the nearest .lore/config.yaml with an sdd key, up to the repository root), the org’s value, and Lore’s default (lore/openspec). It then names the effective framework and the layer it came from. When the Registry can’t be reached, the org’s value comes from the last cached copy, and the output says so.
The org is found the way the governance hook finds it: --org if you pass it, else the org named by the repository’s .lore.yaml (written by lore hooks pin --org=<org>), else LORE_ORG. The output says which one it used. The org layer also needs a signed-in session (lore login); without an org or a session it’s skipped.
Flags
| Flag | Description |
|---|---|
--org <org> | The org whose SDD framework to read (default: the repository’s .lore.yaml, then LORE_ORG) |
--json | Print the resolution as JSON |
Example
$ lore sdd status
Project: acme/bmad-method (/home/me/acme/payments/.lore/config.yaml)
Org: lore/openspec 1.0.0 — set by the org acme (org from this repository's .lore.yaml)
Default: lore/openspec
Effective: acme/bmad-method (project)To install the effective framework, run lore pull with no package.