Draft cohort analysis#344
Open
RichardJECooke wants to merge 88 commits into
Open
Conversation
* Add agent-identity-walled-gardens blog post, publishing 2026-04-24 * Google Cloud 2026 dev keynote post * Update agent-identity-walled-gardens.mdx * Update agent-identity-walled-gardens.mdx * Update agent-identity-walled-gardens.mdx
4317956 to
e4a316b
Compare
e4a316b to
f521c5e
Compare
Dan reported the extract took ~13 minutes for ~20k users and was unsure if it had stalled. Add a short note after the extract command so readers expect the wait and know progress is being printed. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
The note was added when the example repo defaulted to 20,000 mock users (a ~13 minute extraction). The default has been reverted to 1,000, which completes in well under a minute, so the warning is no longer warranted. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
The previous "Charts created" line was incomplete — charts.go also prints "charts-output.html written" and the actual ready signal "Server listening at http://0.0.0.0:7777". The first line appears before the server is up; a reader watching only for it would think the program had hung after rendering. Also surface charts-output.html, the standalone HTML the program writes on startup. It's mentioned in the output but had no explanation; without one, readers would wonder what the file is. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Two prose fixes in the cohort analysis article.
1. Abandonment chart description. The previous wording ("haven't
logged in for more than one, two, six, or 12 months") naturally
reads as cumulative thresholds, but the code (and the rendered
image) use mutually exclusive buckets, with the last one
open-ended. Cumulative would be mathematically impossible given
the image: it shows ~560 users in the "12" column and only ~60
in "1", but if 560 users were inactive for 12+ months they would
all also count as inactive for 1+ month, so "1" would have to be
at least 560. Rewrite to describe the actual exclusive bucketing
and explain why "12+" dominates.
2. Appendix instruction "Adjust the URL, authorization key, and
application Id in the code above" was nonsensical — those values
live in .env, and no code appears above. Drop "in the code
above".
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
The accompanying repo no longer ships a tracked .env (it now ships .env.example with placeholder values). Update both spots that referenced .env to point at the new copy-and-edit flow. The appendix spot also gets a "if you skipped the extraction step" qualifier — a reader running the appendix after the main extraction section already has a working .env and doesn't need to do this again. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
The accompanying repo no longer writes a static HTML copy on startup; the server at localhost:7777 is the only output. Update the expected terminal output to match and remove the now-stale sentence about a standalone copy. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.
FusionAuth#2990