Notes / Projects / Platform Shipsolid / 00 Start Here

Team Charter & Ownership Model

Who owns the platform, how decisions get made, and what teams can expect from us.

Updated June 9, 2026 · §202606092046-5 ·

Chapter Navigation

On This Page

Purpose

Who owns the platform, how decisions get made, and what teams can expect from us.

[stub: charter-mission] — fill this in. Greppable doc-debt marker.

Person	Role	Area
Amit Singh	Observability Architect	Platform direction, architecture
Platform SRE	Engineer	`[stub]`
Service Team Lead	Engineer	`[stub]`
On-call Engineer	Engineer	`[stub]`

Platform team owns: the data plane (Grafana Cloud stacks), the collector fleet (Alloy), shared dashboards/alert libraries, onboarding paved roads, and cost governance.
Service teams own: their own instrumentation, SLOs, alert routing, and runbooks.
Shared responsibility: label schema, retention/sampling policy, incident response.

[stub: raci-matrix] — fill this in. Greppable doc-debt marker.

Architecture decisions are captured as ADRs under 01-platform-architecture/adrs/ (global numbering, scope: platform, -shipsolid suffix).

Local graph

Linked from 2 notes

Vision & Mission

Why the ShipSolid observability platform exists and where it is going.

00 — Start Here

Orientation for anyone joining or consuming the ShipSolid observability platform.

Related notes

Engagement Model

How teams engage the platform team — intake, support tiers, and SLAs.

Logs Instrumentation Guide

How to instrument a service for **logs** on the ShipSolid observability platform.

Metrics Instrumentation Guide

How to instrument a service for **metrics** on the ShipSolid observability platform.

Naming & Label Schema

The canonical label and resource-attribute schema every signal must follow.