- Build the latest VSIX and portable distribution; do not use the earlier full-page Training Console build.
- Open a small normal TypeScript repository with a test task and Git initialized.
- Use the checked Monad Testnet fixtures below; do not paste private wallet data.
- Confirm the RPC status is live. If it is unavailable, show the error honestly rather than substituting cached numbers.
- Do not attempt attestation publish or verification until
RepRegistryhas a verified Testnet address and the wallet flow is configured.
Checked on 2026-07-19 from finalized block 46339905:
- third-party inspection fixture, not PureFlow's
RepRegistry:0xa2b0067002df61df015c11b2cf0be4f34fc41cf8(2,227 bytes of code atsafe); - successful transaction:
0x20c7f773bfaf3b60edd05443955d6168959d76cd8e4f5aa56a1a8fea041b41b0; - receipt evidence: status
0x1, gas used224930, four logs; - explorer: https://testnet.monadscan.com/tx/0x20c7f773bfaf3b60edd05443955d6168959d76cd8e4f5aa56a1a8fea041b41b0.
Launch PureFlow.cmd and open the repository.
Say: “PureFlow is a separate VSCodium distribution for daily development, not a browser IDE and not a coding exercise tab. The normal editor, Explorer, terminal, tests, debugger, and Git stay in charge.”
Edit one line, open the integrated terminal from PureFlow, and run the native test task. Briefly show the PureFlow Mineral theme and compact sidebar; keep the code editor visible.
Open the Workspace route. Point out the current project, relative file, language, selection, and Git branch. Open Source Control through the sidebar to show that PureFlow delegates to the native surface.
Mention that Create Project can scaffold an empty folder, strict Node + TypeScript project, or Monad + Hardhat starter, then opens it as a normal workspace.
Select a small function in the editor. Right-click → PureFlow → Why Is This Code Written This Way? Show the sidebar moving to Mentor while the editor remains open.
Say: “This action sends only the explicit selection, relative file identity, language, and line range. PureFlow never uploads the repository in the background. With no coach configured, the result is clearly labeled local guide.”
Show Quiz me or Quiz current function, then search for one API symbol in Documentation. Do not imply the local guide is a model response.
Open Monad. Refresh Testnet health and show chain ID 10143, latest/safe/finalized blocks, RPC latency, and gas price.
Inspect the prepared real address or transaction hash. Point out balance/nonce/bytecode for an address, or receipt status/finality/gas/logs for a transaction, then open the official explorer link.
Run Monad Project Doctor against a Monad project or starter. Show detected Hardhat/Foundry/Solidity/viem/wagmi signals and whether Testnet configuration was found.
Say: “These are live, read-only RPC and local project results. No wallet is needed to use the workbench.”
Open demo/cache-lab or return to the prepared failing test. Switch to Focus and start a short Rep only now.
Record the hypothesis that the cache-expiry comparison is inverted, run the native test task, mark its outcome yourself, fix the comparison manually, and mark the next outcome. Point out that configured AI calls are blocked while the Rep is active and that PureFlow records user-declared workflow events rather than keystrokes, clipboard contents, terminal history, or parsed test-runner output.
If time is tight, stop after showing the hypothesis and test evidence. The product has already been demonstrated without requiring a Rep.
Show the proof section labeled Prepared, not published.
If RepRegistry is already deployed: show the real address once, and only claim verification after a successful attestorOf read.
If not deployed yet: say so out loud — do not invent a success toast.
End on the companion https://yava-code.github.io/PureFlow/ and https://github.com/yava-code/PureFlow.
- Companion homepage + live Monad band
- IDE: edit + mentor on selection
- Monad inspect fixture
- Focus idle loop copy
- Prepared proof honesty + links