feat(workshops/enterprise-security-automation): add platform story coverage + delivery variants#118
Conversation
…verage + delivery variants - Add Platform Context section and cross-surface callout blocks to README.md (cloud baseline) - Create README.platform.md (Desktop + Cloud variant) reframing the workshop for Devin Desktop as primary interface - Add variant cross-references between README.md and README.platform.md - Fix AskDevin typo to Ask Devin in Lab 3
🤖 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:
|
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
There was a problem hiding this comment.
🚩 Pre-existing facilitator content pattern is widespread across workshops/
The same REVIEW.md violations found in README.platform.md (Post-Event, "Encourage participants", "Enterprise value props", "showing participants") also exist in the original README.md and in multiple other workshop files (workshops/cobol-modernization/README.md:243,266,278, workshops/quality-engineering-security/README.md:149,161, workshops/application-development-maintenance/README.md:674). This suggests a systemic pattern that predates this PR. While the new file shouldn't propagate these violations, fixing them in README.platform.md alone would create an inconsistency with README.md and other workshops. Consider a repo-wide cleanup.
Was this helpful? React with 👍 or 👎 to provide feedback.
There was a problem hiding this comment.
Acknowledged — this is a pre-existing pattern inherited from the baseline README.md and other workshops in the repo. Fixing it in README.platform.md alone would create an inconsistency with README.md. A repo-wide cleanup pass would be the right approach to address this systematically.
| ## Post-Event | ||
|
|
||
| - [ ] Collect participant feedback — especially: which lab was most compelling for enterprise adoption? | ||
| - [ ] Archive any event-specific branches | ||
| - [ ] Update challenge modules if issues were discovered | ||
| - [ ] Share session recordings/artifacts with participants |
There was a problem hiding this comment.
🟡 Post-Event checklist is facilitator-only content (explicitly prohibited by REVIEW.md)
The ## Post-Event section (lines 233-238) is a post-event checklist containing facilitator tasks: "Collect participant feedback", "Archive any event-specific branches", "Update challenge modules", "Share session recordings/artifacts". REVIEW.md explicitly calls out "post-event checklists" as facilitator-only content that belongs in the operator repo: "Flag any facilitator-only content (MCP setup, presales positioning, timing guides, pacing tips for facilitators, post-event checklists). These belong in the operator repo." These tasks are for the event organizer, not the attendee.
Prompt for agents
The Post-Event section (lines 233-238) in README.platform.md is a post-event checklist that REVIEW.md explicitly flags as facilitator-only content belonging in the operator repo. Remove this entire section from the attendee-facing file. The same issue exists in README.md at lines 217-222 (pre-existing). Both should be removed and relocated to the operator repo's facilitator guide for this workshop.
Was this helpful? React with 👍 or 👎 to provide feedback.
There was a problem hiding this comment.
Acknowledged — the Post-Event section is carried over from the baseline README.md (lines 217-222) for consistency. Removing it from README.platform.md while leaving it in README.md would create an inconsistency. A repo-wide cleanup to relocate facilitator-only sections to the operator repo would be the appropriate fix.
|
|
||
| ## Devin Features Checklist | ||
|
|
||
| Encourage participants to track their progress on the [Devin Features Appendix](../../modules/devin-features/README.md) throughout the session. Key activities for this track: |
There was a problem hiding this comment.
🟡 "Encourage participants" is facilitator-directed language in an attendee-facing file
Line 218 reads: "Encourage participants to track their progress on the Devin Features Appendix..." — this is addressed to a facilitator, not the attendee. An attendee doesn't "encourage participants" — they ARE the participant. REVIEW.md states: "This entire repo is for attendees. Flag any facilitator-only content." AGENTS.md reinforces: "This repo is written for the hands-on lab attendee — the person sitting at the keyboard."
| Encourage participants to track their progress on the [Devin Features Appendix](../../modules/devin-features/README.md) throughout the session. Key activities for this track: | |
| Track your progress on the [Devin Features Appendix](../../modules/devin-features/README.md) throughout the session. Key activities for this track: | |
Was this helpful? React with 👍 or 👎 to provide feedback.
| ## Context | ||
|
|
||
| - **Audience:** Enterprise engineering leadership evaluating Devin for organizational adoption | ||
| - **Delivery surface:** Devin Desktop (primary) + Devin Cloud (autonomous execution) | ||
| - **Narrative progression:** Reactive agent (Lab 1) → Coordinated agents (Lab 2) → Autonomous one-shot execution (Lab 3) | ||
| - **Platform story:** Each lab reinforces the local→cloud continuum — explore with Cascade, delegate to Cloud, monitor on the Kanban board, review with one-click checkout | ||
| - **Enterprise value props demonstrated:** | ||
| - Lab 1: Devin reduces MTTR for security findings to near-zero | ||
| - Lab 2: Devin scales security remediation across the entire portfolio, not one repo at a time | ||
| - Lab 3: Devin handles complex tech debt with minimal human oversight and honest self-assessment |
There was a problem hiding this comment.
🟡 "Enterprise value props demonstrated" is presales positioning content
Lines 205-214 contain a ## Context section with "Enterprise value props demonstrated:" and associated bullet points. REVIEW.md explicitly flags "presales positioning" as facilitator-only content that belongs in the operator repo. "Value props" is sales/delivery language — attendees don't need to know what value propositions are being demonstrated; they need lab instructions. The Audience, Delivery surface, Narrative progression, and Platform story bullets are also facilitator metadata rather than attendee-facing content.
Prompt for agents
The Context section (lines 205-214) in README.platform.md contains presales positioning language ("Enterprise value props demonstrated") and facilitator metadata ("Audience", "Delivery surface", "Narrative progression", "Platform story"). REVIEW.md explicitly flags presales positioning as belonging in the operator repo. Remove this entire section from the attendee-facing file and relocate it to the operator repo's facilitator notes for this workshop. The same issue exists in README.md at lines 196-203 (pre-existing).
Was this helpful? React with 👍 or 👎 to provide feedback.
Address Devin Review feedback: replace 'Spend 10 minutes showing participants' with attendee-focused 'Review' phrasing.
|
Based on review feedback from PR #128 (security demos), the following changes are needed across both 1. Replace "Devin API" with Devin Automations We now support Devin Automations as the trigger mechanism instead of calling the Devin API directly. All references to "Devin API" for event-driven triggering should be updated:
2. Replace "bot-loop prevention" with "Automation safeguards" (if present) The safeguards (invocation limits, ACU caps, trigger conditions) are built into Devin Automations. No need for manual bot-loop prevention patterns. 3. Use "safeguards" not "guardrails" "Guardrails" implies what the agent can/cannot do. "Safeguards" is the correct term for automation invocation controls. See the final state of PR #128 for reference on how these patterns were resolved. |
1 participant
Summary
Adds platform story coverage to the enterprise-security-automation workshop with two delivery variants.
README.md (cloud baseline) — additive changes only:
## Platform Contextsection after Overview explaining Devin Cloud via web app, with> **Tip:**callout linking to Desktop variantREADME.platform.mddevin)AskDevin→Ask Devintypo in Lab 3 step 3README.platform.md (Desktop + Cloud variant) — new file:
Link to Devin session: https://partner-workshops.devinenterprise.com/sessions/73ac5817eb1f4ea383e8c3cb359e04ed
Requested by: @bsmitches