Changing a Radar Brief Format? Check Fields & Meaning | Yihu

Fix the client version, compare required fields, nulls and approval meaning before adopting a format. Try Yihu’s sample brief, then review privacy and App Store setup.

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.

Fix the target version, then compare fields and meaning

Record the actual client version and retain harmless before-and-after examples. Compare required keys, types, nulls, source time and confirmation scope. Review editorial labels separately from Radar snapshot fields; renaming a proposal cannot create approval. Pause adoption on a mismatch and consult the existing producer workflow rather than inventing defaults to hide errors.

A separate task from types and batch values

Single-file checks inspect shape; batch comparison inspects source-record differences. Here the question is whether changing a producer/template would change consumer compatibility or confirmation meaning. Do not make universal promises for old/future clients; compare the actual intended source/build and existing workflow.

Format-change review table

Change Existing contract to inspect Risk example Go/stop evidence
Editorial key name An editorial label, not an app field proposals renamed decisions implies approval Preserve meaning; renaming grants no authority
Required root keys Existing date_str, decisions, active/stale/cold types Replacing arrays with projects loses required fields Stop on missing keys; no invented defaults
Optional tasks Missing/null fallback versus explicitly empty [] Adding [] changes interpreted scope Record scope/meaning rather than claiming all tasks vanished
Field type Actual String/Double/Bool/array declarations Number becomes text; Bool becomes string No assumed coercion; validate the actual consumer
Added fields Fields recognized/validated by the intended version New key assumed to provide UI/capability Key presence is not support; inspect implementation
Time meaning Source read, task update and editorial time date_str becomes export time Keep source meaning explicit, not artificially fresh
Identity/scope project/path/id and permissions Renaming/changing sources treated as the same tasks Do not match automatically; retain unknown provenance
Reply meaning Read access, reply_supported and write authority differ New true flag triggers real replies Original eligibility, phone confirmation and receipt gates remain

One synthetic editorial revision

Old editorial label: unconfirmed_proposals = Suggest reviewing a sample checklist.
Proposed label: confirmed_decisions = Suggest reviewing a sample checklist.
Risk: Renaming falsely turns an unapproved proposal into a decision.
Review decision: Reject this meaning change; retain an unconfirmed proposal. Create no task.

These labels are not importable JSON or an executed migration test. A team with an authorized exporter must maintain its actual contract through that process. This page neither converts templates into Radar records nor supplies scripts to modify a live source.

Fix the consumer version first

Record the intended source/build, then compare its snapshot fields instead of declaring the new format compatible. Keep non-sensitive synthetic before/after fixtures identifying required keys, types, absence and meaning. Parsing is not post-decode size/date/identity/timestamp acceptance, much less device, permission or production acceptance.

On a mismatch, do not fill now, copied tasks or completed status merely to hide an error. Stop adoption and report through the existing producer-maintenance workflow. Do not alter source permissions or bypass validation. No schema negotiation, automatic downgrade or migration database is added.

FAQ

Does changing the minutes template update Yihu fields?

No. Editorial labels and app models are different contracts. A template revision creates no interface, import field or service capability.

Does a v2 label establish version negotiation?

No. Inspect actual source support; a file declaration does not certify the consumer supports a new contract. This guide implements no negotiation.

Can proposals simply be renamed decisions without changing content?

Names can change interpretation. Without separate approval, unconfirmed suggestions cannot become decisions or execution authority by renaming.

Does an added producer key work with every client?

No blanket claim follows. Recognition, ignoring and validation depend on the actual version. A new key also supplies no UI/native enhancement without implementation evidence.

Is adding empty tasks only formatting?

No. Missing/null trigger legacy fallback, while [] explicitly supplies an empty ledger. Scope meaning can change and needs source confirmation.

Does this replace Swift decoding and device acceptance?

No. It is manual revision review, not execution of app decoding or checks of real permissions/data. Tests must bind to an actual consumer version and scope.

Reading and evidence

Single-file types/nulls · Same-source batch values · Editorial minutes fields · Degraded-handoff decision · Start · Privacy

Evidence: Radar fields/decode, README source/write boundaries.