---
desc: Reserved design areas that may be refined later.
lifecycle: Active
name: Future Work
structural:
  category:
  - concept
  belongs:
  - sirno
---

Several design areas are reserved for later refinement.

The `locked` field may later define how *entries* or generated regions resist accidental edits.

Long-term version retention policy is reserved for later design.
The core model already treats versions as `eter` snapshots.
Future work decides which snapshots Sirno keeps by default,
which snapshots can be named,
and how review interfaces expose them.

The *transform* names are now `actualize` and `internalize`.
Future work may add command support for those names where the CLI still exposes older surfaces.

Planning skills are future work.
They may use *entries* to leave durable work artifacts without changing Sirno's core fields.

Future work should remain explicit without becoming speculative architecture.
The current design is useful because its core is small:
*entries*, metadata, structural fields, generated footers, forms, *transforms*, checks, and *witnesses*.
New features should preserve that clarity.

The `locked` field is one example.
It may eventually protect *entries*,
metadata fields,
or generated regions that a project treats as controlled.
That design needs a clear ownership model before it becomes part of the schema.
Until then, leaving the field reserved is safer than accepting vague lock behavior.

Version retention is another example.
`eter` provides history, snapshots, retirement, and garbage collection.
Sirno still needs policy for which snapshots stay live.
That policy should preserve reviewable *lake* states without making *entry* metadata harder to read.

The *transform* names may also evolve.
The current names are compact and memorable,
but they should remain subordinate to the model they describe.
If the project learns a clearer vocabulary,
*entries* and manuals can internalize that vocabulary deliberately.
