Micro-flagging is one of three architectural annotation patterns surfaced by the change-management skill. It applies when the author raises a concern without proposing a resolution — the expertise required to resolve it sits with someone else (HR, legal, compliance, a subject-matter reviewer).

The pattern is implemented as the flag mode of the changeProposal shortcode (rendered via src/_includes/parts/change-proposal/flag.njk). The card carries a flag marker, orange accent, and presents the rationale field as the substance (typically the most developed section). The tobe (proposed state) field is normally omitted — flags don't dictate fixes.

Use micro-flagging for:

• "This phrase is undefined and may create uneven application — HR needs to review before the next policy revision"
• "This claim cites a number we have not verified — needs a source"
• "This commitment language exceeds what we're authorized to make publicly — legal review required"
• Any case where the problem is clear but the fix requires expertise the author doesn't have

In static documents, flags are relatively rare. In collaborative sessions and verification workflows, they're common: one person flags, another resolves.

Companion patterns: Micro-editing (when the replacement text is known), Micro-RAGing (when the direction of the fix is known but the text isn't).