Documentation
¶
Overview ¶
Command refund-plan demonstrates the orchestration ledger on a weft/thread session: a refund-support chat whose policy state lives in the session file as custom entries, so a process that dies mid-flow is replaced by one that resumes exactly where the file says — the last refund_plan entry. Never re-ask the customer facts the transcript already holds; never infer the step from the model's phrasing; never re-decide policy with newer rules than the customer was promised.
The conversation is the scripted model's job; the policy is this program's. Every transition appends the COMPLETE current plan state — pi's rule: the complete, total current state, never a delta — so any single surviving entry is enough to resume, and the plan and the transcript share one atomic-append file, so they can never disagree.
Run 1 — drive the chat and die after the manager hand-off:
go run ./thread/examples/refund-plan -crash
Run 2 — a brand-new process resumes from the ledger and finishes:
go run ./thread/examples/refund-plan
Run 3 — a plan version above what this build knows is refused loudly:
go run ./thread/examples/refund-plan -future
Source Files