Motivation
OpenWorker's security and devops coworkers do impressive work decomposing tasks onto the TeamStore board and collecting verified scan evidence into JournalStore cases. However, at the conclusion of an engagement or incident triage, there is no single-command CLI verb or tool to export that case into a clean, human-shareable Markdown/HTML executive report deliverable.
Proposed Solution
- Add an export verb to the
ocw CLI:
ocw journal export --case <case_id> --format markdown > security-audit-report.md
- Include an
export_journal_report(case: str) agent tool for lead coworkers (devsecops-lead, triage-lead), enabling them to compile findings, severity ratings, and reproduction commands directly into a clean output file.
Implementation Scope & Alignment
- Scope: ~130–170 lines in
coworker/teams/journal.py, coworker/teams/cli.py, and coworker/teams/tools.py.
- Zero New Dependencies: Uses standard library string formatting and dataclasses.
- Alignment: Directly fulfills the project's headline promise: "Delivering finished work, not just chat."
Motivation
OpenWorker's security and devops coworkers do impressive work decomposing tasks onto the
TeamStoreboard and collecting verified scan evidence intoJournalStorecases. However, at the conclusion of an engagement or incident triage, there is no single-command CLI verb or tool to export that case into a clean, human-shareable Markdown/HTML executive report deliverable.Proposed Solution
ocwCLI:export_journal_report(case: str)agent tool for lead coworkers (devsecops-lead,triage-lead), enabling them to compile findings, severity ratings, and reproduction commands directly into a clean output file.Implementation Scope & Alignment
coworker/teams/journal.py,coworker/teams/cli.py, andcoworker/teams/tools.py.