# Domain Skill Composition

Read this when specialized engineering guidance must support the current owner.

Freeflow owns authority interpretation, current ownership, route changes, evidence honesty, checkpoints, continuity, and Supported Exit. Domain guidance supplies specialized engineering method. It does not become another Workflow, current owner, or authority source.

## Compose One Current Owner

For the current bounded activity:

1. keep one Freeflow current owner;
2. add only the domain guidance required by the concrete technology, behavior, environment, or risk;
3. use one primary implementation, diagnostic, verification, or review method at a time;
4. retain [Design for Depth](../../design-for-depth/SKILL.md) only when direction is already design-bearing or evidence establishes structural pressure;
5. select independent specialist review only when it materially protects a named boundary.

Prefer repository policy, current primary sources, and technology-specific evidence over generic examples.

Do not load a handbook because one keyword appears. Do not combine several overlapping methodologies merely because each contains useful advice.

## Preserve Workflow Boundaries

Domain guidance may provide techniques for frontend systems, accessibility, browsers, security, performance, databases, APIs, CI/CD, observability, cloud platforms, migrations, releases, deployments, or other specialized work.

It does not override:

- user-owned product, scope, or risk decisions;
- repository instructions or accepted behavior;
- the authority envelope;
- source truth, failure contracts, or evidence requirements;
- the current owner’s result and return conditions;
- selected checkpoints or separately controlled effects;
- mode, capability, host, or tool controls.

When domain guidance conflicts with accepted intent or live source truth, return the conflict to Workflow. Use [Decision Gate](../../decision-gate/SKILL.md) when resolving it requires one user-owned choice.

## Return To The Current Owner

Return domain results, evidence, assumptions, and limits to the same current owner.

A domain method, tool choice, or new observation does not automatically change the current owner, accepted scope, durable task state, or Workflow route.

When the domain method exposes material architecture, authority, safety, evidence, or scope pressure, return that changed boundary to Workflow rather than silently expanding the method.