docs: the front door leads with the recorded session and states what works where - #48
Merged
Merged
Conversation
…works where Co-Authored-By: Subash Natarajan <suboss87@gmail.com>
Contributor
Author
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The README asked a reader to take three paragraphs of positioning on trust before showing them anything the tool does, and the one artifact that cannot be faked — the recorded session — was a click away in
docs/USAGE.md. This reorders the front door around evidence and adds the one section it was missing.## A real sessionis now the second thing on the page, embeddingmedia/session.gifwith themedia/record-session.shlink next to it, plusnpx fdeops demoas the zero-install path. The recording gate accepts README or USAGE as the host; it now reportsrecorded session in README.md + docs/USAGE.md.### What works wherereplaces the per-row "Claude Code does X, others do Y" caveat that was repeated in four places. Two columns, four rows, and the one honest admission the README never made in a table: pulling from Granola/Slack/Notion requires you to add that source MCP — FDEOps only ingests.npx fdeops resumeprints phase, trust, next action — and prints the same thing tomorrow from a cold session.One drive-by:
adapters/README.mdlinked../README.md#switch-coding-agents-anytime, an anchor that has not existed for some time; it now points at#what-works-where, which covers the same question.No code, no skills, no templates.
npm run checkgreen, 110/110.Link to Devin session: https://app.devin.ai/sessions/f135381c4682413bae73dff38eb6d1a3
Requested by: @suboss87