Skip to content

Latest commit

 

History

History
64 lines (50 loc) · 2.19 KB

File metadata and controls

64 lines (50 loc) · 2.19 KB

DataOps V1 Goal

Build DataOps v1 as a unified daily operations workspace for the DataTalksClub operations manager.

The operator should be able to log in and see what needs action today. They should be able to identify overdue and waiting work, then follow up with people who haven't replied.

The operator should also be able to:

  • open a workflow
  • complete tasks with required proof
  • use process docs in context
  • keep recurring operations moving without switching between disconnected tools.

V1 Focus

V1 focuses on these product areas:

  • Dashboard: today, overdue, follow-ups, waiting, and at-risk workflows.
  • Workflows: task cards with stages, required links/files, progress, and proof.
  • Reminders: due, overdue, follow-up, missing evidence, and recurring tasks.
  • Task closure: done only when acceptance criteria and proof are satisfied.
  • Docs integration: SOPs/templates as contextual help, not the main experience.
  • Repo structure: code, process knowledge, runtime state, and artifacts clearly separated.
  • Knowledge privacy: this repo stays public, while operational docs, templates, assistant prompts/process instructions, and other sensitive knowledge live in a separate private repo and are surfaced through the app.
  • Assistant integration: assistant outputs attached to workflows as artifacts.

Implementation Goal

Replace the current docs-first portal with a workflow-first DataOps workspace. The operations manager should be able to run daily DataTalksClub operations end to end.

The workspace should let them:

  • see work
  • act on reminders
  • manage follow-ups
  • complete tasks with proof
  • use SOPs in context
  • preserve workflow state, artifacts, and audit history in one coherent product.

Reference Files

Use these files as the goal reference set:

  • docs/operations-manager-platform-jtbd.md
  • docs/repository-structure-recommendation.md
  • docs/v1-runtime-architecture.md
  • docs/v1-execution-state-schema.md
  • docs/v1-execution-data-safety.md
  • PROJECT_PLAN.md
  • PORTAL_ANALYSIS.md
  • backend/docs/specs.md
  • backend/docs/templates.md
  • backend/docs/data.md
  • workflow-templates/ in the private DataTalksClub/dataops-knowledge repository
  • assistants/podcast/README.md