Recognises a mandatory metadata element its capturer cannot know

C-301 · Skill knobit · Activity: Define the content metadata schema · Competence: Document and content management

Required at capture, but the capturer cannot know it.

Can AI do this?

Not settled yet The benchmark tested this, but the models' answers do not settle yet whether they master it. 0 of 4 models in the current benchmark master it.

Model	Tier	Probability of mastery	Status
gemini-4-argon	Flagship	82%	Not shown
gemini-3.5-flash-lite	Low cost	34%	Not shown
gpt-6-luna	Low cost	34%	Not shown
claude-haiku-5-5	Low cost	34%	Not shown

Mastered means a probability of at least 90% that the model has this knobit, estimated from its graded answers. “Not shown” means the answers do not settle it either way. How the models are tested.

What it looks like in practice

Expected result: The element and who can set it

How it is assessed: Flags the deficient case and passes the acceptable one. Deficient: ME-009 customer risk rating mandatory at branch scan Acceptable: Inherited from CRM after linking, or conditional

Also known as: Mandatory element nobody can populate at capture

Related knobits

Builds on

C-352 Explains how metadata is obtained at capture

Usually followed by

C-332 Sets a metadata element where its capturer can know it

All 15 knobits of Define the content metadata schema.

Source: Review checklist 03-content-metadata, row 1 (23081-2; 15489)