---
desc: The movement from the monograph into the Sirno Lake.
lifecycle: Active
name: Lower
structural:
  category:
  - concept
  belongs:
  - transform
---

`lower` moves from `mono` to `sirno`.

Lowering gives broad narrative design compact nominal form.
It splits a long narrative into *entries* without losing the design route that made the narrative readable.

Lowering preserves intent.
It creates named objects that future work can cite without retelling the whole design.

It does not need to decompose an entire project uniformly.
The area being changed needs enough *entries* to make the work accountable.

Good lowering starts by reading the *monograph* as a whole.
The goal is not to chop each heading into a file mechanically.
The goal is to identify the named objects that will help future work:
concepts, structural fields, interfaces, invariants, implementation commitments,
and narrative routes.

Each lowered *entry* should stand on its own enough to be useful from a query result.
It should also preserve its place in the larger design through metadata.
`category` describes the kind of object.
`belongs` gives local neighborhoods.
`refines` connects local *entries* back to broader design.
Repository *witnesses* are added only when *repository* evidence exists.

Lowering is especially valuable before implementation work becomes local.
Without *entries*, the source of intent may live in chat context or memory.
With *entries*, the next edit can point to the design object that explains it.
That makes review and future reflection less dependent on remembering the original conversation.
