Skip to content

docs: restructure README (glossary, dropdowns), add ROADMAP, rewrite FAQ - #27

Merged
tishachawla-jg merged 2 commits into
mainfrom
docs/restructure-readme
Jul 24, 2026
Merged

docs: restructure README (glossary, dropdowns), add ROADMAP, rewrite FAQ#27
tishachawla-jg merged 2 commits into
mainfrom
docs/restructure-readme

Conversation

@tishachawla-jg

@tishachawla-jg tishachawla-jg commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

Docs-only. Makes the README skimmable and defines the jargon in one place.

Structure

  • Key terms dropdown up top: boundary, Envelope, trace, fixture, stub, live, cut-point, defined once.
  • Reference material (CLI, on_crossing, env vars, EnvelopeRecorder, project structure) moved under an Advanced section of dropdowns. Each recording helper and each verification layer is its own dropdown.
  • Quick start is three numbered steps + a "which entry point?" table; the "what gets captured (I/O, not side effects)" callout stays.
  • stub / live are made explicit at the cut-point example.

Content

  • Envelope captures I/O, not side effects is stated in How-it-works and Quick start (this is why replay is safe).
  • FAQ rewritten into grouped, substantive answers (boundary count, writing a test, side effects on replay, call matching, path divergence, overhead, providers, streaming, Python versions, production readiness). All verified against the code.
  • Roadmap bullets moved to a dedicated ROADMAP.md and linked, instead of living in the README.

Cut

  • Redaction/secrets was explained three times; Security section trimmed, FAQ + glossary carry the rest.

No em/en dashes. Supersedes #26 (closed).

- State plainly that an Envelope records a boundary's I/O (input and
  return value) and does NOT capture side effects that run inside it
  (file writes, network calls, DB writes, time). This is called out in
  both Architecture and Quick start, since it is the reason replay is
  deterministic and safe.
- Rework Quick start into three numbered steps (wrap client, mark your
  own @boundary, record a fixture) and add a "which entry point" table.
- Consolidate the scattered recording helpers (wrap, wrap_llm,
  instrument_langgraph, EnvelopeRecorder) into one "Recording entry
  points" section, replacing the old buried wrap_llm text (which had a
  broken sentence) and the separate LangGraph section.
- Update nav; put the PyPI install line first.

Supersedes #26.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Signed-off-by: Tisha Chawla <tisha.chawla2020@vitalum.ac.in>
The old FAQ was thin and marketing-shaped. Replace it with grouped,
substantive answers covering the practical gaps: what counts as a
boundary and how many to add; how to write a replay test; whether
replay runs tools / side-effecting code (stubbed no, cut-point live
yes); how calls are matched on replay (name + invocation index, so
loops/retries work); what happens when the code path diverges from the
fixture (clear KeyError); recording overhead; which providers wrap()
supports; streaming; Python versions; and production readiness.

All answers verified against the code (session matching, captured_result
/ call_log, KeyError on missing envelope, wrap() provider detection).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Signed-off-by: Tisha Chawla <tisha.chawla2020@vitalum.ac.in>
@tishachawla-jg
tishachawla-jg merged commit 3dc59ee into main Jul 24, 2026
4 checks passed
@tishachawla-jg tishachawla-jg changed the title docs: restructure README and clarify what an Envelope captures docs: restructure README (glossary, dropdowns), add ROADMAP, rewrite FAQ Jul 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant