# HSE domain context brief

By Chris Durgin · Version 1.0
Replace bracketed prompts with your own evidence. This is a context brief,
not a domain rulebook or an installable agent.

## Domain and scope
[Field, product, organization boundary, intended use, and explicit exclusions.]

## People and work
[Users, affected people, roles, goals, tasks, decisions, handoffs, and authority.]
[Environment, devices, accessibility needs, connectivity, time pressure, operating rhythm.]

## Evidence
[Research sources, dates, limitations, and links to authoritative records.]
[Separate observation, interpretation, assumption, and proposed recommendation.]

## Vocabulary and data
[Approved terms, metric definitions, units, population, sources, freshness, and owners.]
[Unknown or disputed meanings and the expert who can resolve them.]

## Constraints and consequences
[Applicable requirements and guidance with sources, permissions, privacy, error
consequences, recovery, escalation, and specialist review. Do not invent policies.]

## Implementation profile
[Your approved design system, components, tokens, interaction conventions,
accessibility requirements, stack, testing and delivery expectations.]

## Human review
[Who validates domain assumptions, data definitions, generated artifacts,
prototype behavior, and release readiness? What decisions remain human-owned?]

## Adaptation check
- Remove assumptions inherited from the example's mining or company context.
- Inspect all skills and examples, not only the domain-context file.
- Keep general HSE reasoning and source traceability intact.
- Test a small representative task and record errors before expanding use.
- Record version, reviewer, changes, and unresolved questions.

## Reuse

Original material by Chris Durgin, licensed under CC BY 4.0.
https://creativecommons.org/licenses/by/4.0/
Credit the author, link the license, and indicate changes.