docs(vol-1): ch02 prose review — advance to voice-check#174
Merged
Conversation
Prose review pass (Stage 5). Trimmed from 7,703 to 4,684 words (target 4,680-5,720). Advanced ICM marker from icm/prose-review to icm/voice-check. Applied style rules: active voice, no hedging, no synonym cycling, no academic scaffolding, lead-with-punchline, cut restatement, cut filler, paragraph max 6 sentences. Kept: Sunita Kulkarni narrative thread, Sabina Rahman, Tariq Hassan, Maria Santos, seven failure-mode section headers, named examples (Sunrise Calendar, AWS us-east-1, Linear, Actual Budget, Anytype, M-PESA). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Prose review pass (Stage 5). Cut from 5,509 to 4,401 words (target 4,000 +/-10%).
Removed academic scaffolding ("this dissertation", "my contribution"), passive
constructions, hedging phrases, and restatement sentences. Renamed "What This
Dissertation Adds" to "What This Book Adds". Advanced ICM marker to voice-check.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
📝 WalkthroughWalkthroughThis PR rewrites three foundational chapters of the dissertation to tighten narrative clarity and deepen technical framing. Chapter 1 condenses the SaaS failure catalog while sharpening emphasis on structural patterns; Chapter 2 updates the local-first taxonomy and positioning; Chapter 3 substantially clarifies the five-layer architecture and its operational consequences. All 183 lines of net change are prose rewrites with no API, contract, or code alterations. ChangesDissertation Narrative Rewrite and Clarity
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🧹 Nitpick comments (1)
vol-1/part-1-thesis-and-pain/ch02-local-first-serious-stack.md (1)
66-67: ⚡ Quick winPrefer citation-only reference style over inline raw URL in body text.
Use the numbered citation (already [9]) and move URL details to References to keep IEEE-style prose consistent.
As per coding guidelines, "Use IEEE numeric citation style (in-text: [1], [2], [3] in order of first appearance)."
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@vol-1/part-1-thesis-and-pain/ch02-local-first-serious-stack.md` around lines 66 - 67, Remove the inline raw URL after "Replicache" and leave only the numeric citation [9] in the sentence (i.e., change "Replicache (https://replicache.dev/)..." to "Replicache [9]..."); then add a corresponding entry in the References section listing the full URL and any bibliographic details for replicache.dev so that all in-text citations follow IEEE numeric style.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@vol-1/part-1-thesis-and-pain/ch01-when-saas-fights-reality.md`:
- Around line 117-120: The two paragraphs beginning "In 2022, Western SaaS
providers — Adobe, Autodesk, Microsoft, Figma..." and "The authority can act on
the customer instead." make specific legal/regulatory claims without inline
numeric citations; add IEEE-style numeric inline citations ([1], [2], [3], ...)
to each concrete claim in the order of first appearance (e.g., sanctions/service
suspensions; US Defense Secretary/Anthropic designation; Russia Federal Law
242-FZ residency requirement; Schrems II ruling; India's DPDP Act), and ensure
each citation maps to the corresponding source in the bibliography using the
required source-section tags (v13 §X, v5 §Y, R1/R2) per the coding guidelines so
numbering/order remains consistent across the chapter.
In `@vol-1/part-1-thesis-and-pain/ch02-local-first-serious-stack.md`:
- Around line 5-6: The chapter exceeds the 4,000 ±10% target by one word; remove
at least one word from ch02-local-first-serious-stack.md so the chapter word
count falls at or below 4,400 (e.g., shorten a sentence in the intro or a long
paragraph), then re-run the word-count check; look for the HTML comment marker
"<!-- Target: ~4,000 words -->" to locate the chapter target metadata and make a
minimal wording change that preserves meaning.
---
Nitpick comments:
In `@vol-1/part-1-thesis-and-pain/ch02-local-first-serious-stack.md`:
- Around line 66-67: Remove the inline raw URL after "Replicache" and leave only
the numeric citation [9] in the sentence (i.e., change "Replicache
(https://replicache.dev/)..." to "Replicache [9]..."); then add a corresponding
entry in the References section listing the full URL and any bibliographic
details for replicache.dev so that all in-text citations follow IEEE numeric
style.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: f3917f88-75f3-4401-ad38-83bd3eb2a99d
📒 Files selected for processing (3)
vol-1/part-1-thesis-and-pain/ch01-when-saas-fights-reality.mdvol-1/part-1-thesis-and-pain/ch02-local-first-serious-stack.mdvol-1/part-1-thesis-and-pain/ch03-inverted-stack-one-diagram.md
Comment on lines
+117
to
120
| In 2022, Western SaaS providers — Adobe, Autodesk, Microsoft, Figma, and dozens of others — suspended service across Russia and CIS markets under sanctions enforcement. Organizations across those markets, accounting for hundreds of thousands of seats built into workflows over more than a decade, found their operations interrupted not because their vendors failed them but because their vendors were directed to stop serving them. In February 2026, the US Defense Secretary designated Anthropic's AI services a national security supply-chain risk [1]. Federal agencies with active Anthropic deployments received direction to cease using them. Anthropic contested the designation legally [2], and a California court enjoined portions of the order for civilian agencies [3]. The Department of Defense exclusion stood [4]. Both Anthropic and its federal customers wanted to continue the relationship. Neither controlled the outcome. | ||
|
|
||
| The authority can act on the vendor. In 2022, Western SaaS providers - Adobe, Autodesk, Microsoft, Figma ([figma.com](https://www.figma.com/), the design tool), and dozens of others - suspended service across Russia and CIS (Commonwealth of Independent States) markets under sanctions enforcement; organizations across those markets, accounting for many hundreds of thousands of seats built into workflows over more than a decade, found their operations interrupted not because their vendors failed them but because their vendors were directed to stop serving them. Software that had been licensed, trained on, and integrated into operational workflows became inaccessible with days of notice, not months. In February 2026, the US Defense Secretary designated Anthropic's AI services a national security supply-chain risk [1]. Federal agencies with active Anthropic deployments - deployments they found valuable and wished to continue - received direction under executive order to cease using them. Anthropic contested the designation legally [2], and a California court subsequently enjoined portions of the order for civilian agencies [3]. The Department of Defense exclusion stood [4]. Both Anthropic and its federal customers wanted to continue the relationship. Neither controlled the outcome. The analytically significant detail in both cases: the restriction came from a party with authority over the vendor, independent of both the vendor's and the customer's preferences. | ||
| The authority can act on the customer instead. Russia's Federal Law 242-FZ has required since 2015 that personal data of Russian citizens be stored on servers located within Russia; organizations using Western SaaS found themselves structurally non-compliant not because their vendor did anything but because the SaaS architecture can't provide on-premises data residency by design. The European Court of Justice's 2020 Schrems II ruling constrained EU organizations from transferring personal data to US cloud providers without adequate supplemental safeguards. India's DPDP Act 2023 creates comparable obligations for Indian organizations using US-hosted services for Indian residents' personal data. | ||
|
|
There was a problem hiding this comment.
Add inline citations for uncited legal/regulatory claims.
These paragraphs introduce specific legal assertions (e.g., Schrems II constraints, DPDP Act, residency obligations) without inline numeric citations in the chapter body. Please attach citation markers to each concrete claim and keep numbering/order consistent with first appearance.
As per coding guidelines, "Use IEEE numeric citation style (in-text: [1], [2], [3] in order of first appearance)" and "Source sections inline by citing v13 §X, v5 §Y, R1/R2 where applicable."
Also applies to: 163-163
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@vol-1/part-1-thesis-and-pain/ch01-when-saas-fights-reality.md` around lines
117 - 120, The two paragraphs beginning "In 2022, Western SaaS providers —
Adobe, Autodesk, Microsoft, Figma..." and "The authority can act on the customer
instead." make specific legal/regulatory claims without inline numeric
citations; add IEEE-style numeric inline citations ([1], [2], [3], ...) to each
concrete claim in the order of first appearance (e.g., sanctions/service
suspensions; US Defense Secretary/Anthropic designation; Russia Federal Law
242-FZ residency requirement; Schrems II ruling; India's DPDP Act), and ensure
each citation maps to the corresponding source in the bibliography using the
required source-section tags (v13 §X, v5 §Y, R1/R2) per the coding guidelines so
numbering/order remains consistent across the chapter.
Comment on lines
5
to
6
| <!-- Target: ~4,000 words --> | ||
| <!-- Source: v13 §2.1–§2.4, §19; v5 §1–§3 --> |
There was a problem hiding this comment.
Trim at least one word to satisfy chapter target tolerance.
PR metadata shows this chapter at 4,401 words against a 4,000 ±10% target (max 4,400). Please cut at least one word before merge.
As per coding guidelines, "Word count must be within ±10% of target for each chapter."
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@vol-1/part-1-thesis-and-pain/ch02-local-first-serious-stack.md` around lines
5 - 6, The chapter exceeds the 4,000 ±10% target by one word; remove at least
one word from ch02-local-first-serious-stack.md so the chapter word count falls
at or below 4,400 (e.g., shorten a sentence in the intro or a long paragraph),
then re-run the word-count check; look for the HTML comment marker "<!-- Target:
~4,000 words -->" to locate the chapter target metadata and make a minimal
wording change that preserves meaning.
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
1 participant
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
icm/prose-review→icm/voice-checkWhat was cut (~1,108 words)
Test plan
icm/voice-check<word>#<digit>patterns in commit bodydocs(fleet-valid)🤖 Generated with Claude Code
Summary by CodeRabbit