Skip to content

Twitch: Documentation (CONTEXT.md) + ETL Scaffolding #271

@danielhe4rt

Description

@danielhe4rt

Parent

#266 — Twitch EventSub: ingestão de eventos via webhook (data lake)

What to build

Domain documentation for the integration-twitch module and empty ETL directory scaffolding for future event processing work.

End-to-end behavior

After this slice, the module has a CONTEXT.md with glossary and structure documentation, the CONTEXT-MAP.md includes Integration Twitch in the system map, the integration-discord CONTEXT.md has a broadened ETL definition, and the ETL/ directory structure exists and is ready for future Actions/DTOs/Console work.

What changes

New — Documentation:

  • app-modules/integration-twitch/CONTEXT.md — glossary (Transport, TwitchHelixConnector, TwitchOAuthConnector, App Access Token, EventSub, TwitchEventLog, ETL), structure diagram, module boundaries, dependencies

Updated — Documentation:

  • CONTEXT-MAP.md — add Integration Twitch context to table and relationship diagram, add dependency rule
  • app-modules/integration-discord/CONTEXT.md — broaden ETL definition from "historical data import" to "layer that transforms external data into domain entities" (covers both batch and real-time)

New — ETL Scaffolding:

  • ETL/Actions/ directory (empty, with .gitkeep)
  • ETL/Console/ directory (empty, with .gitkeep)
  • ETL/DTOs/ directory (empty, with .gitkeep)

Acceptance criteria

  • app-modules/integration-twitch/CONTEXT.md exists with glossary, structure, boundaries, and dependencies
  • CONTEXT-MAP.md includes Integration Twitch in the contexts table and relationship diagram
  • CONTEXT-MAP.md dependency rules include Integration Twitch
  • integration-discord/CONTEXT.md ETL definition broadened to cover batch and real-time
  • ETL/Actions/, ETL/Console/, ETL/DTOs/ directories exist with .gitkeep files
  • All documentation uses the project's domain glossary vocabulary

Blocked by

None — can start immediately.

Note: The CONTEXT.md and CONTEXT-MAP.md changes have already been drafted in the current branch. This issue covers reviewing, finalizing, and committing them alongside the ETL scaffolding.

Metadata

Metadata

Assignees

No one assigned

    Labels

    ready-for-agentFully specified, ready for an AFK agent

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions