feat(workshops/cobol-modernization): add platform story coverage + delivery variants#121
Conversation
…livery variants - Add Platform Context section and cross-surface callout blocks to README.md - Create README.platform.md for Desktop + Cloud delivery variant - Add variant cross-references between both files
🤖 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}
| ## Post-Event | ||
|
|
||
| - [ ] Collect participant feedback — especially: which lab phase was most valuable for their modernization program? | ||
| - [ ] 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 that belongs in the operator repo
The ## Post-Event section (lines 362-367) is a post-event checklist with tasks like "Collect participant feedback", "Archive any event-specific branches", and "Update challenge modules" — all facilitator/organizer tasks, not attendee actions. REVIEW.md explicitly states: "Flag any facilitator-only content (MCP setup, presales positioning, timing guides, pacing tips for facilitators, post-event checklists). These belong in the operator repo."
Prompt for agents
The Post-Event section (lines 362-367 in README.platform.md) contains facilitator-only content that violates the content separation rule. Per REVIEW.md, post-event checklists belong in the operator repo (https://github.com/Cognition-Partner-Workshops/operator), not in this attendee-facing repo. Remove the entire Post-Event section from this file. Note: the same section exists in the original README.md (line 297) and likely should be addressed there too, though that's outside this PR's scope.
Was this helpful? React with 👍 or 👎 to provide feedback.
There was a problem hiding this comment.
The Post-Event section is carried over from the original README.md (lines 278-283) to maintain structural parity between variants per WORKSHOP-VARIANTS.md rule 4: "All variants share the same lab structure (tracks, lab numbering) for cross-referencing." Removing it from only the .platform.md variant while leaving it in the baseline would create an inconsistency. If both should be moved to operator, that's a broader cleanup outside this PR's scope.
| - **Desktop + Cloud value props:** | ||
| - Cascade enables fast, interactive research before delegating heavy tasks to Cloud | ||
| - Agent Command Center provides a single view of all sessions — local and cloud — especially useful when running parallel migrations | ||
| - One-click checkout keeps the review loop inside the editor, eliminating context switches | ||
| - Spaces group all workshop sessions, PRs, and files into a single organizational unit | ||
| - ACP extensibility means teams can bring additional agents (Codex CLI, Claude Agent, Gemini CLI, and others) into Desktop alongside Devin |
There was a problem hiding this comment.
🟡 "Enterprise value props" and "Desktop + Cloud value props" sections are presales positioning
Lines 318 and 323 use explicit sales framing — Enterprise value props shown hands-on: and Desktop + Cloud value props: — in the attendee-facing Context section. REVIEW.md flags "presales positioning" as facilitator-only content that belongs in the operator repo. The bullet content underneath is factual and useful, but the framing as "value props" is sales/delivery positioning that an attendee doesn't need. The "Desktop + Cloud value props" subsection (lines 323-328) is entirely new to this PR and doesn't exist in the base README.md, making it net-new presales content.
Was this helpful? React with 👍 or 👎 to provide feedback.
There was a problem hiding this comment.
This follows the pre-existing pattern in the original README.md which has "Enterprise value props shown hands-on" in the same ## Context section. The review itself notes this: "the 'Enterprise value props shown hands-on' subsection has the same issue but follows a pre-existing pattern in the original README.md." The Desktop + Cloud value props mirror that structure with surface-specific points. If this pattern should move to operator, it should be addressed holistically across workshops rather than in one variant file.
| ## Context | ||
|
|
||
| - **Audience:** Enterprise modernization teams with COBOL estates | ||
| - **Narrative progression:** Understand (Lab 1) -> Plan (Lab 2) -> Safeguard (Lab 3) -> Execute (Lab 4) | ||
| - **Enterprise value props shown hands-on:** | ||
| - Lab 1: Devin compresses months of discovery into hours — dependency maps, data dictionaries, and hotspot analysis without SME interviews | ||
| - Lab 2: Devin produces decision-ready modernization blueprints with multiple strategy options, not just "rewrite everything" | ||
| - Lab 3: Devin builds the migration safety net (tests, reconciliation) before any code changes — reducing migration risk | ||
| - Lab 4: Devin bridges the COBOL-to-Java language barrier that blocks most development teams | ||
| - **Desktop + Cloud value props:** | ||
| - Cascade enables fast, interactive research before delegating heavy tasks to Cloud | ||
| - Agent Command Center provides a single view of all sessions — local and cloud — especially useful when running parallel migrations | ||
| - One-click checkout keeps the review loop inside the editor, eliminating context switches | ||
| - Spaces group all workshop sessions, PRs, and files into a single organizational unit | ||
| - ACP extensibility means teams can bring additional agents (Codex CLI, Claude Agent, Gemini CLI, and others) into Desktop alongside Devin | ||
| - **Suitability:** Medium -> High depending on toolchain access (see notes below) | ||
|
|
||
| ### Suitability Notes | ||
|
|
||
| | Scenario | Rating | Why | | ||
| |----------|--------|-----| | ||
| | Full toolchain access (CI, emulator, batch runs) | **High** | Devin can verify outputs automatically and iterate on migration | | ||
| | Code access only (no COBOL runtime) | **Medium-High** | Devin reverse-engineers, documents, plans, and generates migration code + tests; humans validate outputs | | ||
| | Code not accessible (manual/GUI only) | **Low** | Devin cannot analyze what it cannot access | | ||
|
|
||
| ### Key Constraints | ||
|
|
||
| - **Hidden tribal knowledge** — ops runbooks, scheduler configs, dataset naming conventions, and exception handling may not be in the code | ||
| - **Environment gaps** — mainframe-specific runtimes (CICS, IMS, JES) and data access (VSAM, DB2) cannot run in Devin's Linux VM; analysis is static | ||
| - **Data representativeness** — migration safety depends on realistic test inputs and reconciliation rules, not just happy paths |
There was a problem hiding this comment.
🚩 Context/Suitability sections mirror pre-existing facilitator-facing pattern
The entire ## Context section (lines 314-343) including Suitability Notes and Key Constraints is copied from the original README.md. This content helps organizers decide whether the workshop is suitable for a given scenario — clearly facilitator/planner content rather than attendee instructions. However, since this mirrors a pre-existing accepted pattern across multiple workshop files (workshops/enterprise-security-automation/README.md, etc.), and only the "Desktop + Cloud value props" addition (reported as BUG-0003) is clearly new presales content, I limited bug reports to the most clear-cut violations rather than flagging the entire section.
Was this helpful? React with 👍 or 👎 to provide feedback.
Change 'Encourage participants to track' to 'Track your progress' per AGENTS.md audience rule (content addresses attendees, not facilitators)
There was a problem hiding this comment.
🚩 Post-Event and value-props patterns exist across multiple workshops in the repo
The Post-Event checklist and "Enterprise value props" framing flagged in this PR are pre-existing patterns found in other workshops too (workshops/enterprise-security-automation/README.md:201, workshops/quality-engineering-security/README.md:161). This suggests a systematic repo-wide issue rather than something unique to this PR. A repo-wide sweep to move facilitator sections to the operator repo would address all instances consistently.
Was this helpful? React with 👍 or 👎 to provide feedback.
1 participant
Summary
Adds Cognition Platform story coverage to the COBOL Modernization workshop with two delivery variants per the
.md/.platform.mdconvention.README.md(cloud-agent baseline) — updated:## Platform Contextsection after Abstract: explains this is the Devin Cloud / web-app workflow, with a> **Tip:**callout linking to the Desktop + Cloud variant and CLIREADME.platform.mdREADME.platform.md(Desktop + Cloud variant) — new:No existing lab structure, prompts, timing, or track numbering was altered in
README.md.Link to Devin session: https://partner-workshops.devinenterprise.com/sessions/efacb5d6b3a546c08218697e2d4214fc
Requested by: @bsmitches