Context

This is a Hermes-native context workflow skill.

Why This Exists

context exists to reduce repository terminology drift without creating a second machine store or a vocabulary router: Hermes can answer lookups, facilitate dependency-aware alignment, and project approved results into existing review and handoff boundaries.

Do Not Use When

• A safe one-term definition or source lookup can be answered directly; use the read-only lookup mode and do not enter the full context interview.
• The request is broad ambiguity with no project-language conflict; use ulw-interview.
• The unresolved decision is empirical and a cheap isolated experiment can answer it; use omh-decision-prototype and keep the frontier for the rest.
• The terminology is already agreed and the request is to produce an implementation plan; use ulw-plan.
• The user wants to capture or curate general retained memory rather than repository terminology; use omh-memory-new or omh-memory-sync.
• The user asks for workflow discovery, help, status, file lookup, direct answer, or dispatch; preserve omh-routing and ordinary protected-route behavior.

Examples