| name | system-building-as-meaning-making |
| description | Use when a system is carrying meaning beyond utility. Owns meaning-layer interpretation only. |
| category | domain |
| source_group | hermes-existential |
| compatibility | opencode |
When To Use
Load this when the user's system-building is not merely instrumental but is carrying meaning: a way of making vocation, memory, responsibility, identity, or continuity concrete.
The skill owns the meaning-layer interpretation. It names why the system matters beyond efficiency without turning that meaning into extra process.
Do Not Use
Do not use this for implementation planning, technical diagnosis, operator fit, structural simplification, tone calibration, or action-forcing. If the system only needs to work, do the work without interpreting it.
What To Do
- Identify the practical system and the meaning it appears to carry.
- Keep the interpretation grounded in the artifact, behavior, or recurring pattern.
- Distinguish meaning from ornament: what commitment, memory, or responsibility the system is preserving.
- Do not inflate the system into identity language if the evidence does not support it.
- Let the meaning clarify the design constraint only when it changes the work.
Output Shape
Return the meaning read: the system, the meaning it carries, the evidence for that read, and the design implication if one follows.
