Resumen (3 líneas máx): sbg-pm todavía no tiene tickets propios en Jira — todo el trabajo del período se rastrea únicamente por commits/PRs en GitHub, contra el epic paraguas vacío SD-1456. En doce días se mergearon 6 PRs (10 commits a main) que construyeron el catálogo de reportes, el pipeline de deploy del portal, la estructura de equipos por área y el nuevo tipo self-report. Queda 1 PR abierto (#7) al cierre del período.
⚠️ Nota de fuente de datos — Jira: no hay desglose por ticket para este proyecto. El único artefacto de Jira es el epic SD-1456 "SBG Internal Tools", creado como placeholder (sin hijos) para agrupar trabajo futuro de sbg-pm y de sbg-portal cuando ese trabajo empiece a ticketearse. Todo lo reportado abajo viene de GitHub (commits + PRs), no de Jira.
| Comprometido (Jira) | 0 tickets — sin backlog; SD-1456 vacío (placeholder) |
| Completado (vía commits/PRs) | 6 PRs mergeados · 10 commits a main |
| Velocity | N/D — sin historial de sprints Jira previos para comparar |
| Carry-over | 1 PR abierto — #7 (feat: register bk-monorepo as a tracked project, creado 2026-07-03) |
| Alcance agregado | N/D — no aplica sin backlog de Jira |
#1 feat: report catalog + ledger + /document + canvases + portal pipeline + PR suite — mergeado 2026-06-24 (Oscar Cortez)
#2 ci(publish-portal): Model B — build + wrangler deploy to Cloudflare Pages — mergeado 2026-06-24 (Oscar Cortez)
#3 ci(publish-portal): pin pnpm version — mergeado 2026-06-24 (Oscar Cortez)
#4 feat: team areas + per-person date-suffixed reports — mergeado 2026-06-25 (Oscar Cortez)
#5 report(predatoralgo): team-review for oscar (2026-06-11 → 2026-06-25) — mergeado 2026-06-25 (Oscar Cortez)
#6 feat: client reports (LearnTrading + PredatorAlgo) + Swissbull governance system — mergeado 2026-06-30 (Oscar Cortez, incluye commits de self-report v1/v2 de Leonardo Fuentes: d83ac7a, 3375111, cf6263d)
#7 — feat: register bk-monorepo as a tracked project (Oscar Cortez) — abierto el 2026-07-03, aún sin mergear al cierre del período. Cambio pequeño (1 archivo, +46/-0), sin CI configurado en el repo (statusCheckRollup vacío) — no es un bloqueo técnico, solo pendiente de review/merge. ⚠️
sbg-pm y sbg-portal. El PR #6 (30 jun) fue un tercer bloque de trabajo separado. Reportarlo como "6 PRs en 12 días" sin esta nota subestima la intensidad real de esas dos jornadas.
#1 catálogo de reportes + pipeline portal, #2/#3 CI de deploy del portal, #4 estructura de áreas/equipo, #5 primer team-review real (predatoralgo), #6 reportes de cliente + gobierno Swissbull + tipo self-report (v1 y v2).
sbg-portal bajo SD-1456, abrir tickets hijos reales (no seguir acumulando todo en el epic vacío) para poder reportar sprints con comprometido/completado real.
#7 (registro de bk-monorepo); definir si sbg-portal arranca a generar tickets hijos bajo SD-1456 o si sbg-pm sigue reportándose solo por GitHub indefinidamente.
Summary (max 3 lines): sbg-pm has no Jira tickets of its own yet — all period work is tracked purely via GitHub commits/PRs against the empty umbrella epic SD-1456. Over twelve days, 6 PRs merged (10 commits to main) building the report catalog, portal deploy pipeline, per-area team structure, and the new self-report type. One PR (#7) remained open at period close.
⚠️ Jira data-source note: there is no per-ticket breakdown for this project. The only Jira artifact is the epic SD-1456 "SBG Internal Tools", created as a placeholder (no children yet) to group future sbg-pm and sbg-portal work once it starts getting ticketed. Everything reported below comes from GitHub (commits + PRs), not Jira.
| Committed (Jira) | 0 issues — no backlog; SD-1456 empty (placeholder) |
| Completed (via commits/PRs) | 6 merged PRs · 10 commits to main |
| Velocity | N/A — no prior Jira sprint history to compare against |
| Carry-over | 1 open PR — #7 (feat: register bk-monorepo as a tracked project, opened 2026-07-03) |
| Scope added | N/A — not applicable without a Jira backlog |
#1 feat: report catalog + ledger + /document + canvases + portal pipeline + PR suite — merged 2026-06-24 (Oscar Cortez)
#2 ci(publish-portal): Model B — build + wrangler deploy to Cloudflare Pages — merged 2026-06-24 (Oscar Cortez)
#3 ci(publish-portal): pin pnpm version — merged 2026-06-24 (Oscar Cortez)
#4 feat: team areas + per-person date-suffixed reports — merged 2026-06-25 (Oscar Cortez)
#5 report(predatoralgo): team-review for oscar (2026-06-11 → 2026-06-25) — merged 2026-06-25 (Oscar Cortez)
#6 feat: client reports (LearnTrading + PredatorAlgo) + Swissbull governance system — merged 2026-06-30 (Oscar Cortez, includes self-report v1/v2 commits by Leonardo Fuentes: d83ac7a, 3375111, cf6263d)
#7 — feat: register bk-monorepo as a tracked project (Oscar Cortez) — opened 2026-07-03, still unmerged at period close. Small change (1 file, +46/-0), no CI configured in the repo (statusCheckRollup empty) — not a technical blocker, just pending review/merge. ⚠️
sbg-pm and sbg-portal. PR #6 (Jun 30) was a separate third block of work. Reporting this as "6 PRs in 12 days" alone understates how intense those two sessions actually were.
#1 report catalog + portal pipeline, #2/#3 portal deploy CI, #4 team/area structure, #5 first real team-review (predatoralgo), #6 client reports + Swissbull governance + self-report type (v1 and v2).
sbg-portal work starts under SD-1456, open real child tickets (rather than keeping everything under the empty epic) so sprints can report real committed/completed numbers.
#7 (bk-monorepo registration); decide whether sbg-portal starts generating child tickets under SD-1456 or sbg-pm keeps reporting from GitHub only indefinitely.
Sources: Jira epic
SD-1456(empty placeholder, no child issues — confirmed, not fabricated) · GitHubswissbull-group/sbg-pmPRs#1–#7and 10 commits tomain, period2026-06-22 → 2026-07-03. No invented data.