Golden Briefing Schema

Use a versioned, JSON-parseable schema like the Golden Briefing, where each field carries provenance metadata (level, source, validation status). This lets downstream agents consume the brief programmatically without re-reading source documents.

A Golden Briefing is a versioned contract produced by the Strategist agent and consumed by downstream agents as ground truth. One brief is produced per stream (growth-value or dispositivos), and only the Strategist writes it after human gate approval.

Run the schema's validation checklist: required identity fields, 5-7 executive reading points, 3-4 monthly architecture movements, at least 2 demand currents, rubric entries for all 14 criteria, and traceable evidence for every claim.

Yes. Fields can be empty or marked pending with a reason, figures flagged a_validar must appear in flags_dato_a_validar, and blocking open decisions prevent approval status without an explicit human note.

Through the rendimiento_periodo_anterior block, which the Strategist fills from weekly reports. It separates per-creativity response metrics (CTR, leads, CPL, VTR, clicks, interaction) from per-campaign delivery data and business context.

It is a documentation-only schema with no executable validation scripts, so enforcement depends on the agent following the checklist. It is also tailored to a specific two-stream monthly planning workflow and requires migration when the schema version changes.