Resources & Access
Project Resources
Section titled “Project Resources”Kanban Board
Section titled “Kanban Board”All work on the roche-data platform is tracked on this board. Every feature, bug, access request, and investigation has a corresponding issue. Nothing happens without a tracked item.
The board uses a standard Kanban workflow:
| Column | Meaning |
|---|---|
| Backlog | Planned work, not yet started |
| In Progress | Actively being worked on |
| In Review | Pull request open, awaiting review |
| Done | Merged to main, deployed |
How to request work: Create an issue in the repository using the appropriate template, and it will automatically appear on the board.
Git Repository
Section titled “Git Repository”The monorepo containing all platform code, templates, generated artifacts, and documentation. Key directories:
| Directory | Contents |
|---|---|
cli/ | Rust CLI toolbox source code |
models/ | RTiS model snapshots and generated contracts |
dbt/ | Generated dbt models (Bronze/Silver/Gold) |
snowflake/ | Generated Snowflake DDL scripts |
apis/ | Generated OpenAPI and MCP tool definitions |
k8s/ | Generated OPA Kubernetes manifests |
adr/ | Architecture Decision Records |
docs/ | This documentation site (Astro/Starlight) |
Branch strategy: Feature branches from main. Pull request required for all changes. CI validates on every PR. Deployment on merge to main.
The GitHub team responsible for the roche-data platform. Team membership grants:
- Read/write access to the repository
- PR review assignment eligibility
- Notification routing for mentions and reviews
- Access to team-level discussions
AD Group (CIDM)
Section titled “AD Group (CIDM)”GLOAZUGH_MODEL
The Active Directory group that governs access to platform infrastructure. This CIDM group is used for:
| System | Access granted |
|---|---|
| GitHub | Repository access (via team sync) |
| Snowflake | Service account roles for dbt execution and data access |
| CaaS | Kubernetes namespace access for OPA deployments |
| VPN-gated systems | RTiS, GUPRI, MRHub access through Roche network |
To request access: Submit a CIDM request for the GLOAZUGH_MODEL group through the standard Roche access request process. Approval is managed by the platform team lead.
Getting Started
Section titled “Getting Started”For new team members
Section titled “For new team members”- Request access — Submit a CIDM request for
GLOAZUGH_MODEL - Clone the repo —
git clone https://github.com/roche-private/model-dp-rdt - Read the ADRs — Start with
adr/0001-project-vision.mdfor full context - Build the CLI —
cd cli && cargo build - Run in dry-run mode —
cargo run -- pipeline run --entity waste-tracking --dry-run - Check the board — Pick an unassigned item from the Backlog column
For stakeholders
Section titled “For stakeholders”- Review the board — Kanban view shows current progress
- Read this documentation — Start with Vision & Business Value
- Watch the repo — Star the repository to receive notifications on releases
Phase Roadmap
Section titled “Phase Roadmap”| Phase | Focus | Status |
|---|---|---|
| -1: Project Setup | Repository, CLI skeleton, documentation, ADRs, access requests | Active |
| 0: Foundation | RTiS client, GUPRI client, model pull, contract generation | Pending |
| 1: Bronze | DDL generation, dbt Bronze models, G1 quality checks, CI/CD | Pending |
| 2: Silver | MRHub integration, dbt Silver views, G2 validity checks, Collibra | Pending |
| 3: Gold | dbt Gold views, Semantic Layer, G3+G4 quality checks, Cortex Analyst | Pending |
| 4: AI Layer | MCP tools, OpenAPI specs, LLM-based inference, AI tool registration | Pending |
| 5: Scale | Multi-domain onboarding, pipeline orchestration, self-service | Pending |
Each phase builds on the previous one. Platform access requests (tracked as A01–A15 on the board) are being processed in parallel and will unblock stub-to-real client transitions as they resolve.