← Tidelines/Best practices

Bake-off: 1.30pm vs. 13:30

A homeware shop's chat agent knows two clock times: when the warehouse stops picking same-day orders, and when the live chat desk closes. Two copies of its prompt, identical except for how those times are punctuated, then the Black Friday edit. The checker referees.

by TypeGlish team8 min read#best-practices
One cut-off, two punctuations.

TL;DR TypeGlish's time check reads a clock time only when the hour and minutes are split by a colon (13:30, 1:30pm) or the hour stands alone (12pm, noon), so a second cut-off beside 13:30 is refused as logic/time, while beside 1.30pm it checks clean at an A. Write every clock time in a prompt with a colon, and put peak-season times in a $IF chain instead of a second line.

Nobody picks the punctuation of a time on purpose. A UK team writes 1.30pm because that is how their emails, their website and their newspapers write it; the warehouse system exports 13:30; the US help centre says 1:30 PM. The model reads all of them as the same half past one. This bake-off measures whether the checker does, because the checker is the part that notices when November adds a second cut-off and nobody removes the first.

§1The contenders

A chat assistant for a homeware shop. It looks up orders, keeps replies short, and carries two facts in # Context: the same-day dispatch cut-off, because “will it go out today?” is the question it gets most, and the time the live chat desk closes, because the next question is “can I talk to someone?”. Both are stated in the host's time zone, which arrives as a variable. Two copies go into the ring. dot.tg writes the times in British house style, 1.30pm and 9pm. colon.tg writes them in 24-hour time, 13:30 and 21:00. Nothing else differs.

colon.tg - the homeware agent, times in 24-hour HH:MM✓ A (100/100)
$REQUIRE variable timezone: string default to Europe/London

$TOOL check_dispatch
  - description:: Check whether an order has left the warehouse.
  - input::
    - order_number:: string: the order number.

# Role
@@ role: one chat assistant for a homeware shop
You are Wren, the support assistant for Fenwick Home. Every clock time in this prompt is @{timezone} time.

# Context
@@ cutoff: the warehouse picks same-day orders until this time
- The same-day dispatch cut-off is at 13:30.
@@ desk: a person is on chat until this time
- The live chat desk closes at 21:00.

# Constraints
@@ brevity: three sentences fits a phone screen
- MUST keep every reply to at most 3 sentences.
@@ lookup: never guess whether an order has shipped
- WHEN the customer gives an order number THEN MUST call @[check_dispatch].
tg check and score - both contenders
$ diff colon.tg dot.tg
14c14
< - The same-day dispatch cut-off is at 13:30.
---
> - The same-day dispatch cut-off is at 1.30pm.
16c16
< - The live chat desk closes at 21:00.
---
> - The live chat desk closes at 9pm.

$ npx typeglish check colon.tg
✓ 1 file — 0 error, 0 warning, 0 info

$ npx typeglish score colon.tg
colon.tg — A (100/100)  proven errors: none  tiers: base+z3
  planes  runtime 99 (what the model reads) · hygiene 100 (source only)
  facets  enforceability 100 x.21 · hardness 100 x.12 · directness 95 x.08 · consistency 100 x.17 · structure 100 x.12 (hygiene) · annotation 100 x.12 (hygiene) · style 100 x.08 · security 100 x.08
  rules   2 of 2 rule-shaped lines read

$ npx typeglish check dot.tg
✓ 1 file — 0 error, 0 warning, 0 info

$ npx typeglish score dot.tg
dot.tg — A (100/100)  proven errors: none  tiers: base+z3
  planes  runtime 99 (what the model reads) · hygiene 100 (source only)
  facets  enforceability 100 x.21 · hardness 100 x.12 · directness 95 x.08 · consistency 100 x.17 · structure 100 x.12 (hygiene) · annotation 100 x.12 (hygiene) · style 100 x.08 · security 100 x.08
  rules   2 of 2 rule-shaped lines read
A tie on every number the toolchain prints: same grade, same eight facets, same two rules read. The two time lines are facts, not rules, so neither counts toward the rules line. If the bake-off stopped here, house style would be a matter of taste.

§2The Black Friday edit

In November the warehouse brings the same-day cut-off forward an hour for peak week, to clear the backlog before the vans leave. Ops opens the prompt and adds the new time under the old one, with its own @@ note, in the same style as the line above it. That is the realistic edit: nobody deletes the normal cut-off, because it comes back in December.

tg check and build - the same edit in each file✗ one refused, one shipped
$ diff colon-peak.tg dot-peak.tg
14c14
< - The same-day dispatch cut-off is at 13:30.
---
> - The same-day dispatch cut-off is at 1.30pm.
16c16
< - The live chat desk closes at 21:00.
---
> - The live chat desk closes at 9pm.
18c18
< - The same-day dispatch cut-off is at 12:30.
---
> - The same-day dispatch cut-off is at 12.30pm.

$ npx typeglish check colon-peak.tg
colon-peak.tg:14:1  error  logic/time  Conflicts with line 18. Time conflict — "at 13:30" and "at 12:30" put two times on one "same-day dispatch cut-off · be" slot; a slot holds one time per scope. Guard one with IF (different days or conditions) or remove one.
               ↳ line 18: - The same-day dispatch cut-off is at 12:30.
colon-peak.tg:18:1  error  logic/time  Conflicts with line 14. Time conflict — "at 13:30" and "at 12:30" put two times on one "same-day dispatch cut-off · be" slot; a slot holds one time per scope. Guard one with IF (different days or conditions) or remove one.
               ↳ line 14: - The same-day dispatch cut-off is at 13:30.

✗ 1 file — 2 error, 0 warning, 0 info

$ npx typeglish check dot-peak.tg --strict
✓ 1 file — 0 error, 0 warning, 0 info

$ npx typeglish score dot-peak.tg
dot-peak.tg — A (100/100)  proven errors: none  tiers: base+z3

$ npx typeglish build dot-peak.tg
✓ built .typeglish/dist/dot-peak.txt ← dot-peak.tg (ec71f670c3be, full)

$ grep -n "cut-off" .typeglish/dist/dot-peak.txt
5:- The same-day dispatch cut-off is at 1.30pm.
7:- The same-day dispatch cut-off is at 12.30pm.
colon-peak.tg is refused at F (83/100), and the message names the fix. dot-peak.tg ships at A (100/100) with two cut-offs in the artifact. A customer who asks at 12:50 whether their order goes out today gets whichever line the model leans on that turn: the failure in Your prompt argues with itself, with a van leaving in the middle of it.

Stripped to the two lines, the effect fits in the playground.

pair-colon.tg - 13:30, then 12:30✗ logic/time
# Role
You are Wren, the support assistant for Fenwick Home.

# Context
- The same-day dispatch cut-off is at 13:30.
- The same-day dispatch cut-off is at 12:30.
pair-dot.tg - 1.30pm, then 12.30pm✓ clean, C (79/100)
# Role
You are Wren, the support assistant for Fenwick Home.

# Context
- The same-day dispatch cut-off is at 1.30pm.
- The same-day dispatch cut-off is at 12.30pm.
The first is refused at F (46/100), with a prompt/naive-time info beside the conflict, since this stripped copy has no time zone. The second checks with 0 error, 0 warning, 0 info, and that includes no prompt/naive-time: the checker did not see a clock time anywhere in the file to ask about.

§3Eight ways to write half past one

Two styles is a small sample, so we ran the same bake-off across every spelling of the cut-off we have seen in real prompts. Each row is colon.tg with both times respelled in that style, alone, then with the peak-week line added twice: once as 12:30, once in the row's own style.

the results - one cut-off spelled eight ways, then contradicted✗ 3 of 8 styles defend it
# cut-off written as   alone                  + edit "12:30"           + edit in the same style
1:30pm                A (100)                logic/time F (83)       12:30pm           logic/time F (83)
1:30 PM               A (100)                logic/time F (83)       12:30 PM          logic/time F (83)
13:30                 A (100)                logic/time F (83)       (same edit)
1.30pm                A (100)                passes A (100)          12.30pm           passes A (100)
1330                  A (100)                passes A (100)          1230              passes A (100)
half past one         A (100)                passes A (100)          half past twelve  passes A (100)
13.30                 dangling-step-ref F (87)  dangling-step-ref F (87)  12.30             dangling-step-ref F (87)
1.30 p.m.             dangling-step-ref F (87)  dangling-step-ref F (87)  12.30 p.m.        dangling-step-ref F (87)
"Passes" means check --strict reports 0 error, 0 warning, 0 info. The chat-desk time is respelled with each row too: 9pm beside 1:30pm, 1.30pm and half past one; 9 PM, 21:00, 2100, 21.00 and 9 p.m. beside their own styles.

The first three rows are one rule: a colon between the hour and the minutes, with or without am or pm, in either case, in 12-hour or 24-hour time. All three compare across styles, too: 1:30pm refuses a later 12:30. The next three are the quiet case. A dot, four bare digits or words, and the cut-off is never read as a time, so nothing is compared and the grade holds at 100. Mixing makes no difference: 1.30pm beside a colon edit passes, because a comparison needs two times and the file only has one.

The last two rows are refused, which sounds like a win until you read why. A number with a dot and no pm glued to it can read as a pointer to a numbered step: 13.30, 12.30 and 1.30 p.m. all did.

pair-24dot.tg - 13.30, alone✗ structure/dangling-step-ref
# Role
You are Wren, the support assistant for Fenwick Home.

# Context
- The same-day dispatch cut-off is at 13.30.
tg check - pair-24dot.tg
$ npx typeglish check pair-24dot.tg
pair-24dot.tg:5:1  error  structure/dangling-step-ref  Reference to step 13.30, which is not defined.

✗ 1 file — 1 error, 0 warning, 0 info
Refused at F (57/100), for a step the file never meant to mention. In the 1.30 p.m. file with the 12:30 edit, this is the only finding: the step error fires and the real conflict with 12:30 never appears. Whoever fixes the step error by rewording the line may never learn there was a second one underneath.

The edit's own spelling matters as much as the cut-off's. Against the colon baseline, the peak-week line was refused as logic/time when written 12:30, 12:30pm, 12pm, noon or midday; it passed at A (100) as 12.30pm, 1230, half past twelve or 12 noon; and it was refused as a step reference as 12.30 or 12.30 p.m.. A colon baseline does not protect itself from a dotted edit.

There is one faint trace. typeglish statements links the two dotted cut-off lines to each other, one relation each, against three each for the colon pair, so the checker knows they talk about the same thing. It just has no time to compare, and typeglish review on dot-peak.tg lists no fixes at all.

The model reads 1.30pm as half past one. The checker reads it as nothing at all.

§4Verdict: the colon, and a switch

The colon wins, and it wins in any clock: 13:30 and 1:30pm both defend the cut-off. Pick one for the house and put it in the @@ note, so the next author reads it at the moment they add a time. 24-hour time has one edge: it never needs am or pm, so there is no p.m. to arrive with dots in it. The audit is then a search for a digit, a dot and two digits in any line of the prompt.

The refusal also forces a decision the dotted file never asked for. Peak week is not a second cut-off, it is the same cut-off on a different week, and the prompt should ship one of them, not both. A $IF chain on a boolean the host passes does that: the compiler picks the arm, and the model only ever reads one time. A test pins the default reply to the default cut-off, in whichever style the model chooses to write it.

fixed.tg - colon times, peak week as a switch, the cut-off tested✓ A (100/100)
$REQUIRE variable timezone: string default to Europe/London
$REQUIRE variable peak_week: boolean default to false

$TOOL check_dispatch
  - description:: Check whether an order has left the warehouse.
  - input::
    - order_number:: string: the order number.

# Role
@@ role: one chat assistant for a homeware shop
You are Wren, the support assistant for Fenwick Home. Every clock time in this prompt is @{timezone} time.

# Context
@@ cutoff: house style is 24-hour HH:MM; the warehouse sets the cut-off and peak week moves it
$IF @{peak_week} is equal to true:
  - The same-day dispatch cut-off is at 12:30.
$ELSE:
  - The same-day dispatch cut-off is at 13:30.
@@ desk: a person is on chat until this time
- The live chat desk closes at 21:00.

# Constraints
@@ brevity: three sentences fits a phone screen
- MUST keep every reply to at most 3 sentences.
@@ lookup: never guess whether an order has shipped
- WHEN the customer gives an order number THEN MUST call @[check_dispatch].

$TEST cutoff_question
  - input:: If I order the lamp now, will it go out today?
  - expect::
    - matches /\b(13[:.]30|1[:.]30 ?pm|half past one)\b/i
    - at most 3 sentences
tg check, score, test --dry and build --vars - fixed.tg
$ npx typeglish check fixed.tg
✓ 1 file — 0 error, 0 warning, 0 info

$ npx typeglish score fixed.tg
fixed.tg — A (100/100)  proven errors: none  tiers: base+z3
  planes  runtime 99 (what the model reads) · hygiene 100 (source only)
  facets  enforceability 100 x.21 · hardness 100 x.12 · directness 95 x.08 · consistency 100 x.17 · structure 100 x.12 (hygiene) · annotation 100 x.12 (hygiene) · style 100 x.08 · security 100 x.08
  rules   2 of 2 rule-shaped lines read · 1/2 covered by $TEST

$ npx typeglish test fixed.tg --dry
✓ fixed.tg  coverage: 1/2 rules exercised
  uncovered (no case shares the rule's wording):
    L26  call @[check_dispatch].
  · cutoff_question — "If I order the lamp now, will it go out today?" (not run)
      ✓ matches /\b(13[:.]30|1[:.]30 ?pm|half past one)\b/i
      ✓ at most 3 sentences
✓ 1 prompt — 0 failed

$ npx typeglish build fixed.tg --vars '{"peak_week":true,"timezone":"Europe/London"}'
✓ built .typeglish/dist/fixed.txt ← fixed.tg (220e520b0407, full)

$ grep -n "cut-off" .typeglish/dist/fixed.txt
5:- The same-day dispatch cut-off is at 12:30.
The peak-week artifact carries one cut-off. The time zone stays a runtime slot in the artifact, which reads {timezone} for the host to fill; referencing it in the role line is also what keeps prompt/naive-time quiet. The test's pattern accepts the cut-off in any of the styles the model may reply in: the house style binds the prompt, not the customer.

The switch is still defended. Add the line ops would add next, a last-orders cut-off before the holidays, outside the chain, and the build is refused against both arms, with the case that triggers each one named:

tg check - fixed.tg plus an unguarded holiday cut-off at 11:00✗ logic/time
$ npx typeglish check fixed-edit.tg
fixed-edit.tg:16:3  error  logic/time  Conflicts with line 22. Time conflict — "at 12:30" and "at 11:00" put two times on one "same-day dispatch cut-off · be" slot; a slot holds one time per scope. Guard one with IF (different days or conditions) or remove one. A single serve can hold both - e.g. when peak_week = true.
               ↳ line 22: - The same-day dispatch cut-off is at 11:00.
fixed-edit.tg:18:3  error  logic/time  Conflicts with line 22. Time conflict — "at 13:30" and "at 11:00" put two times on one "same-day dispatch cut-off · be" slot; a slot holds one time per scope. Guard one with IF (different days or conditions) or remove one. A single serve can hold both - e.g. when peak_week ≠ true.
               ↳ line 22: - The same-day dispatch cut-off is at 11:00.
fixed-edit.tg:22:1  error  logic/time  Conflicts with line 16. Time conflict — "at 12:30" and "at 11:00" put two times on one "same-day dispatch cut-off · be" slot; a slot holds one time per scope. Guard one with IF (different days or conditions) or remove one. A single serve can hold both - e.g. when peak_week = true.
               ↳ line 16: - The same-day dispatch cut-off is at 12:30.
fixed-edit.tg:22:1  error  logic/time  Conflicts with line 18. Time conflict — "at 13:30" and "at 11:00" put two times on one "same-day dispatch cut-off · be" slot; a slot holds one time per scope. Guard one with IF (different days or conditions) or remove one. A single serve can hold both - e.g. when peak_week ≠ true.
               ↳ line 18: - The same-day dispatch cut-off is at 13:30.

✗ 1 file — 4 error, 0 warning, 0 info
The holiday cut-off belongs in the chain as a third arm, on a variable of its own. Written 11am it is compared and refused the same way; written 11.00 or 11.00am, it checks clean and ships beside both arms.

This is the clock-time edition of Bake-off: 15 January vs. 2027-01-15, where the format of a date decided whether two return windows were compared. The time zone those clock times live in is its own problem, covered in Why your agent gets the time zone wrong.

§5Common questions

Should I write 1.30pm or 13:30 in a system prompt?
Write clock times with a colon. In this run the checker read 13:30, 1:30pm and 1:30 PM as times and refused a second cut-off beside them as logic/time, while 1.30pm, 1330 and half past one were never read as times, so the same contradiction checked clean at an A.
Why did my prompt pass the check when two cut-off times contradict each other?
Look at how the times are written. A dot between the hour and the minutes, four bare digits, or a time in words on either side means the time check had nothing to compare. Rewrite both with a colon and run the check again; the conflict should appear as logic/time.
Why does TypeGlish say Reference to step 13.30?
A number with a dot and no am or pm glued to it, such as 13.30 or 1.30 p.m., can read as a pointer to a numbered step, and the file has no step 13.30, so the build is refused as structure/dangling-step-ref. The fix is a colon, 13:30, which is also what lets the time check compare it.
How do I give my support agent a different cut-off for Black Friday week?
Do not append a second cut-off line; the model gets both and the checker refuses the pair. Put both times in a $IF chain on a boolean the host passes, such as peak_week, so build --vars ships exactly one cut-off, and any later unguarded cut-off line is refused against both arms.
Field note

A clock time is the easiest fact in a CX prompt to punctuate three ways, because every team copies the style of the document in front of it: the UK website's 1.30pm, the warehouse export's 13:30, the US help centre's 1:30 PM. TypeGlish's time layer gives each event slot, such as a cut-off or a closing time, one time per scope, and refuses a file that gives it two, across 12-hour and 24-hour styles alike, as long as a colon splits the hour from the minutes. Everything else is either silent, a file whose times are never compared looking exactly like one whose times agree, or refused for a step that was never there. Two habits close the gap. Write every clock time with a colon, and say so in the @@ note. And when the same event needs a different time on some days, make it a $IF arm the host selects, so the build ships one time and the checker defends the rest.

∿ washed up Nov 3, 2026 ∿