Activity across datum-cloud/enhancements, datum-cloud/infra, and datum-cloud/network-services-operator. Period: January 1 – March 10, 2026.

The activity system went from an idea to a fully deployed production service. Work spanned the activity-apiserver (sharing the etcd cluster, infra#1875), activity-processor with NATS mTLS (infra#1584, infra#1587), a ClickHouse full-text index fix for v26.1 (infra#1885), the activity-ui (infra#1581), ActivityPolicy support wired into dns-operator ([infra#1832](https://github.com

The authoritative DNS service solves two distinct but related problems:

User-facing DNS management: Datum Cloud customers own domain names (e.g., example.com) and want Datum to serve authoritative DNS for them. Users create a Domain resource to claim ownership, a DNSZone resource to declare a hosted zone, and DNSRecordSet resources to manage records. Datum's infrastructure then serves live DNS responses for those zones.

This should instead be:

• Whatever you're working on needs an issue somewhere
• Every day look through the open issues assigned to you
  • Do they have a recent status? If not, add one.
  • Is the status still accurate? If not, fix it.
  • Does the status have a time component? If not, add when others can expect the next action to be completed.
  • Is the issue blocked? If so, reach out to whomever is blocking the work. Push it forward.
  • Is the issue's purpose and next action clear? If not, go get clarity.
  • Is the work still relevant? If not, or if it's unclear and you're unable to get clarity, add a comment describing that's the case and unassign yourself.

HTTP/3 represents the most significant architectural change in web communication since the internet's inception. While previous versions of HTTP (the protocol that allows your browser to fetch web pages) made incremental improvements, HTTP/3 fundamentally reimagines how data travels across the internet. It replaces the 50-year-old foundation (TCP) with an entirely new transport system called QUIC, designed for the mobile-first, always-connected world we live in today.

Key takeaway: HTTP/3 is not just a faster version of HTTP/2. It is a ground-up redesign that solves problems the original internet architects never anticipated: smartphones switching between WiFi and cellular networks, video calls that cannot tolerate delays, and billions of simultaneous connections that must remain secure without sacrificing speed.

I want to build a model and its APIs using the kubebuilder pattern. Don't use code examples or any particular programming language. Walk me through at the REST API layer or other interfaces how I would need to build in my language of choice

I'll walk you through the conceptual architecture and interfaces you need to build, independent of language.

You're essentially building two parallel systems that share data sources:

1. The Reconciliation System (Kubebuilder's domain)
2. The REST API System (Your webapp domain)