epic/portfolio-research-ops: portfolio-linked daily and earnings workflows

[adolago]

Problem

Portfolio operations need direct integration with automated research outputs.

Outcome

Daily and event-driven portfolio workflows consume Stanley research artifacts by default.

Scope

• Portfolio-aware briefing templates.
• Watchlist/holdings delta analysis.
• Scheduled and event-triggered research ops.

Dependencies

• Depends on news/earnings intelligence and thesis tracking.

Acceptance criteria

• Daily briefs include holdings and watchlist deltas.
• Earnings workflows produce pre/post summaries.
• Ops can run unattended with audit logs.

Metrics

• Daily brief generation success rate.
• Earnings packet turnaround time.

Execution tracking

• [child] daily portfolio brief workflow for holdings and watchlist #512 - [child] daily portfolio brief workflow for holdings and watchlist
• [child] earnings pre/post event research packets #513 - [child] earnings pre/post event research packets (depends on [child] daily portfolio brief workflow for holdings and watchlist #512)
• [child] unattended scheduling, delivery, and audit trail #514 - [child] unattended scheduling, delivery, and audit trail (depends on [child] earnings pre/post event research packets #513)

Dependency chain: #512 -> #513 -> #514

[adolago]

Child execution issues created:

• [child] daily portfolio brief workflow for holdings and watchlist #512 (owner suggestion: Portfolio Ops Owner)
• [child] earnings pre/post event research packets #513 (owner suggestion: Earnings Workflow Owner; depends on [child] daily portfolio brief workflow for holdings and watchlist #512)
• [child] unattended scheduling, delivery, and audit trail #514 (owner suggestion: Operations Automation Owner; depends on [child] earnings pre/post event research packets #513)

Dependency chain: #512 -> #513 -> #514

[adolago]

Closed after child issues #512, #513, and #514 merged on main and the portfolio research ops acceptance is now implemented in production code.