Skip to content
Astera Technology

Separate an internal proposed plan from an agreed customer instruction

Keep proposal, accepted plan and completed action distinct when preparing a reply.

An internal note can describe unfinished decisions

Synthetic internal note N-271 proposes reissuing October output after the data owner checks rows. The data owner has not yet accepted the plan. Another note N-272 records that customer guide G-2 has been checked and can be sent. A reply must not say “October output has been replaced” merely because N-271 exists. The fixture separates approved instructions from proposed operations, without defining contractual authority.

Filled synthetic support record
NoteDecision stateAction evidencePublic reply treatment
N-271Reissue proposedNo reissue completedDescribe proposal if relevant
N-272G-2 instructions acceptedGuide availableCan send current guide
Claim: output replacedNo supporting decision/actionAbsentReject completed-action wording
Download editable CSV ↓

Check decision state before turning notes into instructions

  1. Read internal note context
  2. Identify proposal or accepted instruction
  3. Check whether action occurred
  4. Write the appropriate customer message

Do not copy internal shorthand that implies certainty or completion unsupported by the case record.

Which note supports sending a ready instruction now?

Show the worked answer

N-272 for G-2. N-271 remains a proposed reissue and does not prove a completed replacement.

Keep plan acceptance and actual completion as separate facts. A proposed operation can be communicated as a proposal while its decision remains open.

Related resources