Save a Decision and Reuse It

Complete setup and use the same Wenlan library and Space throughout this example. A Space keeps the project’s knowledge together.

The launch decision below is fictional. Replace it with a decision from your work; do not save it as a real project fact.

Imagine you have decided to launch a project on the web before building a mobile app. Save both the choice and the constraint behind it.

In Claude Code, send this command. Check the saved memory and the Space returned by the capture tool: it should contain the decision, reason, and condition for revisiting it in the intended Space.

Start a fresh conversation with the same Wenlan connection and run the /recall command below. Compare the Space shown with the Space reported when you saved the decision. If they differ, select the matching Space using the Spaces guide and try again.

The result should say “web first” and explain the maintenance constraint. Open the returned memory to check it. A plausible answer without a matching saved record does not verify recall.

Use /handoff when you want to preserve more than one fact: what changed, what remains open, and where to resume. Check its summary before relying on it.

In the next session, /brief reads the current Space’s Brief. Use it to get oriented; use /recall for a specific past decision. You do not need to run every command for every chat.

Saved memories are searchable immediately; turning them into Wiki pages is optional. When several findings belong together, ask your connected AI to organize them with /wenlan steep.

Automatic background upkeep is a separate mode that needs a configured model. Human-edited or review-locked pages can require approval before an update is applied.