PULSE

BUILD

Use the Left Arrow and Right Arrow keys. Home opens the first slide. End opens the last slide.

Current slide: 1 / 21

1 of 21

OPENMINED ENGINEERING · 10 AUGUST 2026

PULSE — the path from repository to production

Create a repository. Declare intent. Ship through one safe, observable platform path.

Stephen Gabriel

Member of Technical Staff · PULSE · OpenMined Platform Engineering

A rocket carries a repository through platform controls to a cloud
Repository → controls → cloud

BUILD · OUR GOAL

Our promise: teams focus on products, not platform plumbing

Fast delivery

A reviewed change reaches a useful environment in minutes.

Safe defaults

Identity, policy, isolation, and audit exist before the first release.

Evidence by default

Every service has deployment proof, health, logs, traces, metrics, and documentation.

One path, clear extensions

Teams use a standard path. They extend it through reviewed contracts when needed.

PULSE owns repeated platform work. Product teams own product decisions and delivery outcomes.

Goal: a repository and domain become a controlled service through one platform product 03 / 21

BUILD · RESULTS

Four applications now use one automated development path

4 applications

All use the SF development delivery path.

~15–20 minutes

A main merge reaches verified SF development.

7 live hostnames

Platform and tenant hostnames were live on 2026-08-10.

Zero stored cloud credentials

GitHub OpenID Connect (OIDC) supplies cloud identity.

Operating now: AKS · OIDC · Argo CD · Kargo · Envoy · OpenTelemetry · SigNoz · Hub · Docs · Status.

28 days since the greenfield rebuild · 271 merged PRs · PR #19 → PR #312 04 / 21

CHAPTER 2 · ARCHITECTURE

One service crosses five connected technical layers

AUTHOR
  • GitHub repository
  • CI checks
  • OIDC identity
  • Container build
DELIVER
  • ACR digest
  • Kargo freight
  • Git pin PR
  • Argo CD sync
  • AKS rollout
SERVE
  • Cloudflare edge
  • Envoy Gateway
  • HTTPRoute
  • Tenant service
PROTECT
  • JWT audience
  • Header policy
  • Admission policy
  • Network policy
  • RBAC
EXPLAIN
  • OpenTelemetry
  • SigNoz
  • Gatus
  • PULSE Hub
  • Docs
Git records intent · immutable digests prove versions · telemetry explains runtime behavior 05 / 21

ARCHITECTURE · TWO DELIVERY PLANES

Cloud resources and cluster state meet at one reviewed boundary

Cloud plane · Terraform

Creates AKS, ACR, DNS, workload identity, storage, and cloud policy.

CI plans · reviewed apply · no local apply

Git boundary

Git records every desired version and configuration change. Required checks verify the rendered result.

Human and machine changes use the same review path

Cluster plane · Argo CD

Reconciles gateways, platform services, policies, and tenant workloads from Git.

No direct kubectl · drift becomes visible

OIDC removes stored cloud secrets. Immutable image digests connect source, deployment intent, and running pods.

ARCHITECTURE · CURRENT FRICTION

Teams still maintain delivery plumbing that should become a product

Current team burden

  • Maintain CI workflow details.
  • Maintain application charts.
  • Understand registry and GitOps wiring.
  • Repeat observability setup.

PULSE standard

  • Supported CI templates.
  • Standard application contract.
  • Automatic policy and telemetry.
  • Versioned migration path.

Extension contract

  • Teams keep application choices.
  • Teams extend approved interfaces.
  • Exceptions remain reviewed and visible.
  • PULSE improves the shared pattern.

Standardize repeated work. Preserve clear extension points. Let engineers focus on delivery.

Today: working delivery after manual onboarding · Target: supported self-service 07 / 21

ARCHITECTURE · DOCUMENTATION

Documentation is part of the platform interface

  1. 1 · Decide

    Architecture decision records explain technical choices and limits.

    ADRs

  2. 2 · Operate

    Runbooks give tested procedures for access, delivery, recovery, and onboarding.

    Runbooks · checks · receipts

  3. 3 · Discover

    The Docs site and PULSE Hub make services, guides, status, and ownership easy to find.

    Docs · Hub · Status

  4. 4 · Preserve

    The ledger, roadmap, source, and Talks archive keep decisions and outcomes auditable.

    Ledger · roadmap · talks

Code, decisions, operating steps, and proof change through the same reviewed repository.

PROVE · CURRENT RESULT

ScreamingFace proves the complete development path

4 applications

Different application shapes use one delivery contract.

15–20 minutes

A main merge reaches verified SF development.

One traceable version

Commit, image digest, Git pin, Argo state, and pod digest connect.

No platform ticket

Automation proposes and verifies the development deployment.

This proves the architecture. Production, pull request previews, and automatic onboarding remain future work.

Current boundary: SF development · Production requires Milestone 2 09 / 21

CHAPTER 3 · OPERATE

Five clicks show how an engineer uses PULSE today

  1. 1 · HubOpen the service, documentation, status, and platform tools.
  2. 2 · SourceOpen the commit and the immutable image digest.
  3. 3 · DeliveryCompare the Git pin, Argo state, and running pod digest.
  4. 4 · RequestSend one allowed request through Cloudflare and Envoy.
  5. 5 · EvidenceOpen pre-filtered SigNoz logs for that service and time.

No new deployment is required. The demonstration follows one service from source to runtime evidence.

Simple demonstration · four minutes · fallback captures in Backup 2 10 / 21

OPERATE · REQUEST ARCHITECTURE

One request crosses four verifiable boundaries

1 · EDGE
  • Cloudflare DNS
  • Cloudflare Tunnel
  • Access identity
2 · GATEWAY
  • Envoy Gateway
  • JWT audience
  • Header removal
  • Route policy
3 · WORKLOAD
  • Tenant namespace
  • Service account
  • Network policy
  • Application
4 · EVIDENCE
  • OpenTelemetry
  • Logs
  • Traces
  • Metrics
  • SigNoz

Envoy creates verified identity headers. OpenTelemetry carries service and tenant context into operational evidence.

OPERATE · AI CONTROLS

AI increases change speed and the need for controls

  1. 1Person sets intent
  2. 2Artificial intelligence (AI) proposes a change
  3. 3Checks and review verify the change
  4. 4Cluster policy enforces the contract
  5. 5Telemetry returns operational results

AI lowers the cost of changes. The platform must lower the cost of proving changes.

OPERATE · SECURITY POSTURE · LIVE NOW

Security is enforced at every platform layer

A shield connects source, identity, Kubernetes, network, and audit controls
Defense in depth
SOURCE + CI
  • Required checks
  • Secret scan
  • SHA-pinned tools
  • Dispatch allowlist
  • Drift detector
IDENTITY + SECRETS
  • OIDC identities
  • Key Vault
  • External Secrets
  • Workload identity
  • Break-glass rotation
KUBERNETES
  • AAD RBAC
  • Local accounts off
  • Pod Security
  • Quotas + limits
  • Admission policy
NETWORK + EDGE
  • Cilium default deny
  • Private origin
  • Access + Entra
  • Envoy JWT policy
  • Header replacement
AUDIT + EVIDENCE
  • AKS audit logs
  • Git receipts
  • Argo health
  • Gateway probes
  • Security docs

Controls live in code, policy, tests, and logs. One failed layer does not remove every boundary.

OPERATE · SECURITY PRODUCT · NEXT

Before production, security becomes visible and reusable

BEFORE PRODUCTION

  • Split production, development, and preview identities.
  • Scan, sign, and attest immutable artifacts.
  • Admit approved registry images only.
  • Add managed data, backups, recovery, and high availability.
  • Sandbox workloads that execute untrusted code.

Reusable low-level utilities

  • Terraform stack allowlists and secure module defaults.
  • Kubernetes render and schema validation.
  • Control-drift, Argo-health, and pin-staleness checks.
  • Gateway conformance and admission policy libraries.
  • Secret rotation and repository onboarding recipes.

Developer visibility

  • Checks explain why a change failed.
  • Hub, Docs, and Status expose the supported path.
  • Links open GitHub, Argo CD, and pre-filtered SigNoz evidence.
  • The control plane will show controls, exceptions, owners, age, and evidence.
  • Unknown evidence stays Unknown.

The goal is not hidden security work. The platform gives safe defaults, clear exceptions, and evidence that developers can inspect.

OPERATE · SMALL-TEAM DECISION

Own the platform contracts; evaluate managed operations

EVALUATION PROPOSED SIGNoz

We own the telemetry contract

Keep OpenTelemetry collectors, attributes, dashboards, alerts, export rules, and Git configuration.

A provider can operate storage, queries, upgrades, scaling, and availability.

RESEARCH ENVOY

We own the gateway contract

Keep Gateway API resources, identity rules, headers, rate limits, telemetry, tests, and rollback.

Evaluate managed operations only when a provider preserves exact behavior and exit options.

This model lets a small team own architecture and policy without owning every database, upgrade, and capacity event.

Decision gates: security · compatibility · reliability · cost · export · rollback · support · exit

SigNoz Cloud has a documented dual-send evaluation. Managed Envoy operations remain research. 15 / 21

CHAPTER 4 · NEXT

The control plane will answer platform health questions

ILLUSTRATIVE — NOT LIVE Platform-wide product · SF is the first focus

ILLUSTRATIVE — NOT LIVE

What runs now?

Show services, capacity, health, and last deployment.

ILLUSTRATIVE — NOT LIVE

Does deployment match intent?

Compare Git intent with every running image digest.

ILLUSTRATIVE — NOT LIVE

What has a problem or delay?

Show the affected scope, evidence time, and owner.

ILLUSTRATIVE — NOT LIVE

Where can I inspect details?

Open pre-filtered SigNoz, GitHub, and Argo CD views.

The first product is read-only. Missing evidence shows Unknown. Later scopes add engineering health, cost, security, and capacity.

NEXT · REPOSITORY PRODUCT

Our vision: a repository becomes a production-ready service in minutes

1 · Declare intent

platform.yaml

service: new-product
owner: product-team
domain: app.openmined.org
data: internal

2 · Protect repository

Automation adds owners, required checks, OIDC, CI, CLAUDE.md, and lifecycle rules.

3 · Create delivery

Automation adds image builds, development, previews, and a reviewed production promotion path.

4 · Add operations

Automation adds routes, identity, policy, logs, traces, metrics, alerts, status, and documentation.

5 · Ship

A merge reaches development. A pull request gets a preview. A reviewed action promotes production.

The engineer supplies a few lines of intent. PULSE supplies the complete delivery and operating path.

VISION — NOT LIVE Pull request previews and automatic onboarding remain future work. Production requires Milestone 2.

Today, development delivery works after manual onboarding.

NEXT · VERIFIED DELIVERIES

Individual deliveries move the platform toward the vision

  1. IN PROGRESSM1.8 security hardening

    Finish admin-edge, registry integrity, drift detection, and identity cleanup.

  2. DEFERREDPull request preview environments

    Create one preview per pull request with split identity and automatic removal.

  3. NOT STARTEDM2 reviewed production promotion

    Prove the exact release and running digest before a reviewed production action.

  4. NOT STARTEDIdentity cluster and HA Keycloak

    Move identity to a private, highly available service with controlled administration.

  5. NOT STARTEDP7 self-service platform

    Turn declarative intent into supported onboarding, delivery, operations, and policy.

  6. PLANNEDControl-plane live health beta

    Connect live evidence, health views, source links, and explicit Unknown states.

NEXT · TECHNICAL LEADERSHIP

Working patterns can become OpenMined technical leadership

RESEARCH DIRECTION

Controlled AI delivery

Publish a reference architecture.

RESEARCH DIRECTION

Multi-tenant AI gateway

Publish a reusable template.

RESEARCH DIRECTION

Portable managed services

Publish an evaluation method and upstream work.

RESEARCH DIRECTION

Declarative platform products

Publish technical guides and product contracts.

NEXT · OUR PROMISE

What PULSE promises OpenMined

LIVE NOW

  • One reviewed path connects source, delivery, runtime, trust, evidence, and documentation.
  • A main merge reaches a running SF development service in minutes.
  • OIDC, policy, and Git audit protect human and machine changes.
  • Product teams can find services, status, guides, and operating evidence.

NEXT

  • A small declaration starts the complete repository path.
  • Every pull request can receive an integrated preview.
  • Every release can use a reviewed production promotion.
  • The control plane makes delivery, health, cost, and security clear.
Live and next remain separate commitments 20 / 21

BUILD PRODUCTS · PULSE PROVIDES THE PATH

Create the repository. Declare intent. Ship.

pulse.dev.openmined.org/talks/

PULSE turns repositories into controlled, documented, and observable services.

Our goal is simple: make the safe delivery path the fast delivery path.

Questions and discussion are welcome.

Stephen Gabriel · PULSE ·

Quick response code for pulse.dev.openmined.org/talks
pulse.dev.openmined.org/talks
Prepared for the August 10, 2026 event 21 / 21

Backup 1 · Architecture detail

PULSE owns the shared path; teams own their workloads

DELIVERY · SHARED

Teams own repositories and CI. PULSE owns ACR integration, Kargo, Git checks, Argo CD, and cluster delivery.

RUNTIME · SHARED

Teams own workloads. PULSE owns Cloudflare, Envoy, routes, identity, and shared cluster services.

TRUST · PULSE

PULSE owns OIDC, role-based access control, admission rules, quotas, network policy, and storage policy.

SIGNALS · SHARED

Workloads emit telemetry. PULSE owns OpenTelemetry transport, SigNoz integration, and status views.

Backup 2 · Demonstration fallback

Four local captures can replace the live demonstration

PRE-EVENT CAPTURE REQUIRED

Service view

Intended version, running version, health, and last deployment.

PRE-EVENT CAPTURE REQUIRED

Deployment record

Commit, automation record, and image digest.

PRE-EVENT CAPTURE REQUIRED

Request results

One allowed read and one refused write.

PRE-EVENT CAPTURE REQUIRED

Pre-filtered logs

Request route, time, and response status.

Local fallback set · no credentials, tokens, or private log data B2 / 6

Backup 3 · Decision summary

Eight decisions define the current platform contract

8 architecture decision records (ADRs)

Repository and delivery

ADR-0001: Group files by tool. ADR-0002: Use one delivery service across defined operational areas.

Portal and tenancy

ADR-0003: Use one URL with replaceable views. ADR-0004: Use namespaces before virtual clusters.

Gateway and workloads

ADR-0005: Share gateway tiers. ADR-0006: Separate platform boundaries from workload ownership.

Telemetry and delivery contract

ADR-0007: Use SigNoz with OpenTelemetry. ADR-0008: Automate tenant development delivery.

Each architecture decision record opens in GitHub. B3 / 6

Backup 4 · Managed services

A managed-service trial must preserve control and exit options

Architecture

Keep configuration in Git. Keep standard interfaces. Require no tenant application change.

Security and data

Approve the data region, contract, tenant isolation, and supported query paths.

Operations

Test reliability, support, routine scaling, maintenance, and documented availability.

Economics and exit

Measure usage and price. Verify export, reversal, and service exit procedures.

PROPOSED SigNoz dual-send trial · RESEARCH managed Envoy operations

Backup 5 · Control-plane evidence

Four source groups can answer platform health questions

ILLUSTRATIVE — NOT LIVE Platform-wide product · SF is the first focus

What runs?

Argo CD, Kubernetes, and status checks show services and health.

Does deployment match intent?

Git, Kargo, ACR, Argo CD, and image digests form the verification chain.

What has a problem or delay?

Health checks, GitHub records, and telemetry provide current evidence.

Where are the details?

Pre-filtered links open SigNoz, GitHub, and Argo CD.

First product: read-only · every answer includes an evidence time B5 / 6

Backup 6 · Cost and security posture

Inventory gives PULSE a starting point for cost and security work

904

Azure resources

99

resource groups

884

untagged resources

  • Current: The phase-two cleanup scope exists.
  • Next: Milestone 2.x requires cost controls before graphics processing unit use.
  • Later control-plane scope: cost, security, and capacity evidence.