Agent Application DevelopmentAccount
Knowledge catalogChoose core direction and segmented content
Practice 06AdvancedSystem designAbout 18 minutes

Corresponding knowledge: Separate plan revisions from external facts

Halfway through the execution, it is discovered that the plan is wrong. Should the Agent re-plan or continue?

Examine dynamic plans, completed side effects, dependencies, and acceptance invariants.

planningstatus versionApproval

Knowledge content check2026-10-03 · Check the source of the original question2026-10-02

Knowledge unit directory

LEARN · PRACTICE · REFLECT

Knowledge exercises·Independent answers

My notes and review ↗

Principles and Solutions have been collapsed. Explain the core mechanism, boundaries and verification methods in your own words, and then compare them.

Answers and personal notes

Each modified commit will be kept as an independent history. Your level of mastery is up to you to evaluate yourself against the standards.

Explain in your own words first

The core principles, analysis, Q&A and migration cases have been closed. When you are ready, unfold it and compare it with the content to find any omissions.

Hands-on verificationComplete on demand · Suggestions15 minutes

A three-step plan is given: fetch data, generate reports, and publish; modify the measurement definition after generation to mark which states are invalid.

Expand acceptance requirements and checkpoints
  • Dependency changes propagated to reports
  • Release Approval Revalidation
  • Historical execution records can still be traced

Key inspections

  • Distinguish between target contract and plan version
  • Reconcile committed side effects
  • Give replanning trigger and upper limit