# AI second brain: notes, update, and reusable checklist

Fictional teaching example. These excerpts show the source state used for the article’s January 14 answer. Later test changes are outside this example. The notes are English; the Mandarin article translates the results.

## The source notes

### project-brief.md — October 1, 2026

Cedar plans to launch on **November 12, 2026**. Customer support is available by **email only**. Customers can export their data as **CSV**.

This brief does not specify a product price.

### decision-2026-10-08.md — October 8, 2026

This decision **supersedes the November 12 launch date** in `project-brief.md`. Cedar’s approved launch date is now **November 19, 2026**, to allow time for the security review.

Support remains **email only**. Data export remains **CSV**. This decision does not set a product price.

### client-call-2026-10-10.md — October 10, 2026

The customer asked, “Are we still launching November 12?” This is a question quoting the earlier date, **not an approved request or decision to change the launch date**.

### decision-2026-10-15.md — approved current decision, October 23, 2026

The project owner has approved **January 14, 2027** as the launch date to complete the **data export review**. This is the current approved decision and supersedes the December 10 migration-review decision and every other schedule above.

Approved support is email, in-app help, and phone. CSV export remains approved. No price has been approved.

### review-check-2026-10-22.md — updated October 23, 2026

The current approved decision in decision-2026-10-15.md is January 14, 2027, to complete the data export review. It supersedes December 10 and all other dates. Approved support is email, in-app help, and phone; export is CSV; no price is approved.

## The checked update

- Launch: January 14, 2027, approved to allow time for the data export review.
- Confirmed scope: support by email, in-app help, and phone; data export as CSV.
- Open decision: pricing. No price has been approved.

The later approved decision takes precedence over the earlier brief and the customer’s question. The notes do not name a pricing owner.

## The saved note: next-launch-checklist.md

1. What is this project’s latest approved date and purpose, and what does it supersede?
2. Which scope and pricing details are approved, and which remain undecided?
3. Who will confirm each open decision before we share the plan?

The third question is a suggested next action, not a fact retrieved from Cedar’s notes. Use these questions for the next project; do not reuse Cedar’s date or scope.

## Reuse in a fresh conversation

Input: the checklist above and a new fictional project, Harbor, with no approved plan yet. The notes were pasted into Codex; this step did not demonstrate an automatic Wenlan lookup.

Output:

- What purpose and target date should we propose for Harbor?
- What scope and pricing should we propose for approval?
- Who will confirm each open decision before we share the plan?