Watch the new 80-second story: create a synonym, share it, then search
These earlier host recordings remain available as versioned evidence. The new story above follows the current alternative-to-search flow.
Keep alternatives attached to words, sentences and paragraphs. Ghost a passage without losing it, stash notes in Overflow, and use the Lab to inspect possible cuts. The editor runs as WebAssembly in your browser with a bundled local knowledge graph.
Grammarly for knowledge work
Follow a public project brief from editing to search using the same knowledge graph. The 77-second captioned overview shows the browser editor, explicitly hands off to the clean file exported from Safari, then compares real terraphim-grep executions with and without --answer.
Recorded host walkthroughs
- Chrome: editing, saved annotations and reopen — 44s
- Safari: editing, saved annotations and reopen — 45s
- Firefox: editing, saved annotations and reopen — 49s
- Existing Zed extension: KG completion, saved history, Ghost and Revive — 60s
- Real grep execution: evidence without synthesis, then with
--answer— 21s
The browser recordings produced identical saved annotated files. A separately checked Safari clean-export file supplies the grep corpus; the Safari walkthrough does not show that export gesture. Newly authored Assessment registers as a document-scoped synonym; it does not update the shared KG used by the CLI. Zed demonstrates existing extension capabilities; the Zed fork is separate. The brief's Trim preview produced zero cuts, so this recording does not demonstrate text reduction. The generated synthesis overstates a review policy as observed practice; compare that statement with the returned evidence rather than treating it as verified fact.
All six videos now have explanatory on-screen captions. Idle intervals are cut, actions are accelerated by 1.5–3× where disclosed, and the long terminal end hold is removed. Captions sit outside the application image. Safari setup is cut and the Zed avatar remains masked. Chronological source ranges and speed changes are recorded in the manifest; original captures are retained. These are finite walkthroughs, not complete acceptance of all 41 requirements. Build identities, media hashes and edit disclosures identify the recorded candidate. The current editor preview includes the Unicode normalization repair: canonically equivalent accents, Terraphim Unicode lowercase and Greek sigma equivalence protect exact original spellings during Trim. The videos retain their earlier recorded build identity; they do not demonstrate this later repair.
This is a preview. The complete source-video requirements are still being qualified; Safari dragging and some visual/native cases remain unresolved. Keyboard pull from Overflow is available. The browser demo does not imply full custom visual parity in the stock Zed extension.
Start with a public brief
Paste this supplied example into the editor. It is sample input, not generated output:
# Public research workspace
Decision: launch a local-first research workspace for the delivery team.
The decision owner will review the brief before the pilot begins.
Risk: inconsistent terminology makes prior decisions hard to locate.
Use the project brief to align the team and keep the decision record clear.
Turn on Write_On using the word counter. Explore alternatives for “decision”, add your own wording, and compare it in context. Ghost/revive a passage, stash a note in Overflow and inspect the Lab. Save the result and reopen the actual file to check the choices and annotations.
Save your work and use it in search
Save keeps the Markdown, alternatives, ghosts and Overflow together. Clean Markdown export includes active text and omits ghosts, Overflow and the annotation block. Chrome can offer a file handle; Firefox and Safari use a download. Check the actual browser dialog and downloaded file.
Download the same bundled KG and inspect the editor build identity. Newly authored alternatives register as document-scoped synonyms; they do not silently change this shared KG.
Move the chosen saved or clean-exported file into a dedicated local corpus folder. Keep evidence logs and other copies outside that folder. With terraphim-grep installed, set paths for that public corpus and downloaded KG:
terraphim-grep "decision" --thesaurus ./default.json --paths ./public-corpus --json
terraphim-grep "decision" --thesaurus ./default.json --paths ./public-corpus --json --answer
The first command returns search evidence without enabling synthesis. The second asks for an answer when sufficient evidence and a configured provider are available. Keep the query, corpus and KG unchanged to compare them. Add the same --role-config path to both commands if configuring a provider through a role. Check the generated answer against the returned source lines; a missing answer or provider error is not a successful synthesis.
Writing and local search do not require sending your document to an LLM. Synthesis may send retrieved content to the configured provider. Use public sample content for the demo and inspect the provider configuration before enabling --answer.