Ten-site pilot
Begin installations at ten customer sites after selecting a sensor supplier.
How it works
Capture the decisions. Preserve the reasoning. Give the next authorized agent a verified starting point.

01 Capture
Keep your project context in a clear, portable format. Write in Markdown, organize your files, and capture the decisions behind the work.
For a new water-quality product line, that means keeping the pilot scope, supplier questions and next engineering review together.
02 Review
A supplier review changes the rollout plan. Keep the existing decision visible, explain the proposed change, and let the project owner review it.
The next session should know both what changed and why.
Water Quality · Pilot scope · Awaiting review
Begin installations at ten customer sites after selecting a sensor supplier.
Start at three sites. Review installation effort and calibration support before expanding to the remaining seven.
The two shortlisted sensors have different calibration requirements. A smaller first phase lets the team validate its support plan before scaling.
Decision needed: The project owner must approve the revised scope before it replaces the current record.
Review checks the current revision before saving. A changed record requires a fresh proposal.
03 Continue
Once the three-site pilot is approved, carry that decision into the next tool. Bring the agreed scope, open questions and next action into your next session.
“Use the water-quality project record to draft the three-site pilot checklist. Flag decisions that still need approval.”
Use a compatible MCP connection with project access, or bring your Markdown files into a tool that accepts them. Client compatibility, requested permissions, and approval presentation vary.
Explore connection options →Using the desktop companion with Codex or Claude Code? Follow the session memory setup guide to capture new activity and review updates to your project record.
04 Clear boundaries
Keep the right information in the right place, with separate personal, organization and project permissions.
Organization membership does not grant access to every project.
Your work deserves a continuous thread.