feat: add general-themes narrative content with shared context layer improvements

[devin-ai-integration]

Summary

Adds shared/general-themes/ — a set of 7 markdown documents that provide reusable narrative content for positioning Devin in workshops, solution briefs, and customer engagements. These are tech-stack-agnostic reference materials that workshop events can link to for consistent messaging.

Documents added:

• README.md — Index with one-line summaries for each document
• when-to-use-devin.md — Trigger categories (event-driven, large-scale campaigns, capacity-constrained O&M) and "the sweet spot" criteria
• architecture-strengths.md — Clean-room execution model with a Shared Context Layer subsection covering VM blueprints, knowledge notes, playbooks, MCP servers, secrets, and Git connections
• design-patterns-for-devin.md — 6 patterns: locally testable code, event-driven triggers, divide-and-conquer, human-in-the-loop, toolchain-agnostic stubs, context layer configuration
• platform-capabilities.md — Scheduled sessions, playbooks, child agents, team-based operation (with full shared config enumeration), Devin Review, session lifecycle
• collaboration-model.md — PR feedback loop, multi-user communication, CI monitoring, hibernation/resume, continuous improvement cycle
• value-narratives.md — Audience-segmented value framing: capacity unlocking, velocity multiplication, quality, risk reduction, cost optimization (with strengthened licensing cost narrative)

Key editorial choices:

• The clean-room execution section deliberately pairs worker isolation (security) with the shared context layer (productivity) — this is the central architectural insight the docs aim to convey
• Clean-room is framed as isolation between workers in a controlled environment that preserves existing access control/governance — not as "Devin missing access to things"
• Secrets are positioned as belonging to a service account identity, separate from individual user permissions
• Licensing cost reduction is called out as urgency-oriented work (sunset timelines, compliance mandates, burdensome licensing) rather than purely cost-motivated
• Cross-references link between documents (e.g., collaboration-model → architecture-strengths#shared-context-layer) for navigability

Updates since last revision

Addressed review feedback from PR #64 comments:

• Reframed clean-room isolation — Positioned as worker isolation in a controlled environment that preserves existing security posture, not as "access to nothing" (architecture-strengths.md)
• Existing governance preserved — Security-by-default bullet now explicitly notes existing access control and governance mechanisms remain in place
• Playbooks enable scale — Added that playbooks are what enable scaling how many workers you kick off, since each executes the same validated process
• Service account identity — Secrets bullet clarifies credentials belong to the service account, not conflated with user identity
• Context retention — Collaboration model clarifies Devin retains its conversation context on resume (no re-reading from scratch)
• Off-machine runners — Design patterns doc now acknowledges CI pipelines and external test systems as alternative verification paths when local execution isn't fully possible
• Team-based coworker framing — Platform capabilities now explicitly positions Devin as a team-based coworker agent, not an individual user's AI assistant
• Urgency-oriented — "Cost-motivated" sweet-spot criterion renamed to "Urgency-oriented" with broader drivers (license sunsets, compliance mandates, platform EOL)
• Burdensome licensing — Language/framework translation row uses "pathway away from products with burdensome licensing models"

Review & Testing Checklist for Human

• Verify shared context layer claims are accurate — The Shared Context Layer subsection in architecture-strengths.md lists 6 components (VM blueprints, knowledge, playbooks, MCP, secrets, Git connections) with specific claims about service account identity separation and playbook-based scaling. Confirm these match current platform capabilities.
• Validate the "existing governance" framing — The security-by-default bullet now states Devin "operates within your existing access control and governance mechanisms." Confirm this is an accurate and approved way to describe the security model to customers.
• Check cross-document consistency — The shared context layer is enumerated in architecture-strengths.md, platform-capabilities.md, design-patterns-for-devin.md, and collaboration-model.md. The lists are intentionally not identical (each emphasizes what's relevant in context), but verify they don't contradict each other.
• Validate cross-reference anchors — Several docs link to architecture-strengths.md#shared-context-layer. Confirm the ### Shared Context Layer heading renders as that anchor on GitHub.
• Review tone and positioning — These are customer-facing narrative documents. Check that the framing (e.g., "team-based coworker agent not individual AI assistant", "urgency-oriented", velocity examples, service account identity claims) aligns with what the org wants to communicate externally.
• Confirm no customer-identifying content — Scan all files for customer names, partner org names, or identifying references.

Notes

• Pure markdown/narrative — no code, no structural changes to the repo outside shared/general-themes/.
• PR improve general-themes: shared context layer, softened overstatements, stronger licensing narrative #64 (now superseded) targeted content-seed with the same base content. This PR targets main directly as requested. Review comments from PR improve general-themes: shared context layer, softened overstatements, stronger licensing narrative #64 have been addressed here.
• The webinar event in PR feat: add 2026-05-20 virtual webinar event — autonomous software engineering intro #63 (events/2026-05-20-virtual-webinar/) cross-references these general-themes documents, so this PR should merge first.

Link to Devin session: https://partner-workshops.devinenterprise.com/sessions/bae5c32308f24765b549ec97e4930d7c
Requested by: @bsmitches

---

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 1 additional finding.