Empty Task Fields? Check Values Before Drafting | Yihu

Missing status, priority or next steps? Check source values before drafting. Try Yihu’s no-login sample brief, keep unknowns separate, and review privacy before downloading.

Preview privacy before you try

The linked preview uses preset material, needs no login or microphone, and keeps edits only in the open page. Reloading resets edits. Optional read-aloud uses the browser’s voice service; usage analytics require consent.

Keep private originals in approved tools. In the app, on-device recognition and the destination’s storage, sync and access rules are separate steps. Review the installed version before using a source-described workflow. Read the data-flow guide

US listing verified; availability depends on your storefront. No Mac or self-signing for store installation. Bring your workspace address and account; the optional speech model is about 950 MB.

Check source values; draft only what is confirmed

Check status, priority and next steps in the authorized source first. Keep missing values unknown rather than guessing an owner, date or business state. Compare the card with the source and put only checked information into the draft. Display placeholders and sorting fallbacks need separate review.

Different from JSON type validation

JSON guidance checks missing/null/types. Here rendering, fallback ordering and capability conditions can be mistaken for source contents. This is not another full schema guide, field editor or blanket equivalence between empty strings and all whitespace.

Empty values, placeholders and fallbacks

Location Existing consumer behavior/boundary Review Do not fill/infer
Required identity/title Decode checks nonempty project/title and other conditions Presence, type and nonempty rules Untitled automatically replaces valid source data
status rendering Blank task-card state can display not provided Label versus raw status Missing means planned, done or approved
priority rendering nil/empty can display pending priority Actual value versus label Replace with P2/default business priority
next rendering Task card can show pending after trimming empty text Original, specific control and known gap Invent action or owner
session/evidence Some missing values display pending/not provided Whether the source supplied those words literally Label establishes an owner session or evidence
Sort fallback Unknown priorities have ordering rules Order is not a field assignment Low position means source assigned low urgency
reply_supported Explicit true required for this capability condition Unknown differs from explicit false Disabled UI means rewrite all missing values as false
Empty note transcript handOff rejects an empty transcript Original versus UI message Pass a placeholder as transcription or silently remove gaps

Trimming depends on each implementation/control; it is not uniform. Do not generalize one card’s condition into universal cleansing. Similar displays do not establish identical raw values.

Synthetic placeholder versus literal text

A: evidence is null; the card displays a pending label.
B: evidence is literally the pending-label string supplied by the source.
Review: Neither establishes actual business evidence, but source values differ.
Decision: Preserve the distinction; a placeholder screenshot is not the original field. Rewrite no live data.

This is not a complete snapshot or actual decoder run. Inspect originals only with existing authorization; no raw-data viewer or public private-source access is added.

Defaults must not expand conclusions

An editor can label unknowns but must not claim source updates. Identity/required-field/capability failures cannot be bypassed by filling now, empty arrays or familiar priorities.

No text does not prove no meeting occurred. No matching tasks does not prove all tasks completed. A pending label does not promise automatic completion. Retain actual facts/unknowns without deriving business status, authority or resend eligibility from placeholders/order.

FAQ

Does priority pending mean the source saved that string?

Not necessarily. Inspect the original field rather than treating screenshot labels as raw values.

Can an untitled default make a missing title valid?

Do not fabricate values. The consumer has nonempty identity/title conditions; use the real source-maintenance process.

Are empty, whitespace and missing identical everywhere?

No. Parser/control conditions differ. No universal normalization or cleansing guarantee is supplied.

Does disabled UI prove reply_supported is explicitly false?

No. Unknown capability and other permission/source conditions affect availability. Preserve raw value versus UI outcome without writing false.

Can fallback ordering justify filling low priority?

No. Ordering does not modify source priority or establish business urgency.

Can no-text placeholder text be handed off as transcription?

Do not do so. Messages are not originals; entry/one-handoff guards remain. Preserve the actual content gap.

Reading and source

JSON types/nulls · Summary provenance · Cross-device display · One note handoff · Start · Privacy

Evidence: task-card placeholders, decode/sorting, empty-transcript guard.