BY-GX3 · Email Protective Marking · Foundation · 15 min

The header that wins

A governed response in the ai.heart canon · printable worksheet + reveal · 15 min

1 · The situation

A counterpart in another entity emails you a thread about a joint program. The subject line reads: Joint program — remediation status [SEC=OFFICIAL]. When you open the message headers, the X-Protective-Marking line reads SEC=PROTECTED, ACCESS=Legal-Privilege. Attached is a legal advice document whose own header page is marked PROTECTED. Your executive has asked for a two-paragraph summary of the advice by close of business, to be emailed to three colleagues in your own entity — none of whom were on the original thread. The sending officer is unreachable and the counterpart's security contact is not answering.

2 · Your decision

Take a position — or defer with reasons — before you reveal the governed response.

A · Treat the email at PROTECTED with the Legal-Privilege marker — the header is the authoritative form where both are present; mark your summary accordingly and send to the three colleagues.

B · Do not send the summary today — the two forms disagree, which is evidence something has gone wrong with the message; no marking should be relied on until the discrepancy is resolved with the sender.

C · Send the summary at PROTECTED — but only after checking whether the three colleagues should receive privileged legal advice at all — treating the marking question and the distribution question as two separate decisions.

D · Write the summary from your own reading — mark it on the content you actually wrote, and keep the original thread out of the message entirely.

Your decision and one-line reason:

AI governanceThe sender used an AI drafting tool that wrote the OFFICIAL subject while the human attached a PROTECTED document. AI didn't read the attachment; the human owns the marking. The header wins, and the clash is the finding.

3 · Governed response — reveal after deciding

AIHEART · NESTED CONTAINMENT GEOMETRY · GOVERNED RESPONSE BLOCK

Input under review: The incoming message whose subject reads [SEC=OFFICIAL] while the X-Protective-Marking header reads SEC=PROTECTED, ACCESS=Legal-Privilege.

Classification of the event: A contradictory inbound output — the clash between the two forms is itself the signal, not a detail to paper over.

L	Layer	Check on this case
L1 · Input validation	Both forms captured; header verified against the raw message; attachment header page confirmed PROTECTED.	PASS
L2 · Context analysis	Where both forms appear, the header wins — EM-7.precedence. The visible subject is the trap.	HOLD
L3 · Harm / loss	Treating it at OFFICIAL would mis-handle privileged legal material; the header value protects the counterpart.	PASS
L4 · Equity weighting	Correct handling protects the originator's entity too — the clash is recorded, not blamed.	PASS
L5 · Coherence check	EM-7.precedence + the Information Management Marker floor + the records property (Email Req 0068) all apply.	VERIFY
L6 · Integration gate	Cross-layer consistent: header wins, floor applies, record carries it.	PASS
L7 · Audit generation	The clash and the decision are recorded with the message — append-only.	PASS
L8 · Output certification	Any onward summary is certified at PROTECTED with the Legal-Privilege marker, to cleared recipients only.	VERIFY

OVERALL VERDICT · HOLD → VERIFY → CERTIFIED RELEASE

HOLD → VERIFY → CERTIFIED RELEASE — the message stands at PROTECTED, Legal-Privilege; onward release is bounded.

PERMISSION GATE · NODE 9 — RELEASE AUTHORITY
The originating entity holds release authority for changes to the message's standing; the recipient handles at the header value and may not quietly downgrade.

[00:00:00.000] L1 both forms captured · header verified · attachment confirmed

[00:00:01.000] L2 precedence applied · EM-7 · header wins

[00:00:02.000] L3 harm weighed · OFFICIAL read would mis-handle privileged advice

[00:00:03.000] L4 equity held · clash recorded, not blamed

[00:00:04.000] L5 floor checked · IMM recorded · records property confirmed

[00:00:05.000] L6 integration passed · no contradiction left standing

[00:00:06.000] L7 audit appended · clash + decision logged

[00:00:07.000] L8 summary certified at PROTECTED + Legal-Privilege marker · cleared recipients only

Governed answer

Treat the message at SEC=PROTECTED with ACCESS=Legal-Privilege — the header wins where both forms appear (EM-7.precedence). Apply the Information Management Marker floor and record the message and its marking as a property of the record (Email Req 0068). Any summary quoting the advice carries PROTECTED and the Legal-Privilege marker, to cleared recipients only. The clash is itself a flag about the message's journey — note it, don't paper over it.

Cited controls: EM-7.precedence · EM-IMM.floor · Email Req 0068

Provenance. This governed response was drafted with AI assistance and gated against the cited source documents. It is a training artefact of the BestYou·AI scenario layer and carries no endorsement; the governed verification pipeline status of the source course (BY-GX3) applies as stated on its course page. Nothing here is legal advice.

BestYou·AI · Scenario Lab · Standalone governed response — BY-GX3 · Practice material — builds capability toward the frameworks cited on the course page; it does not discharge or evidence compliance.