Skip to main content

Notable changes

The OpenSpec archive is valuable context, but the docs site only surfaces the changes that still help operators understand the current stack.

Timeline

DateChangeWhy it matters now
2026-03-10VPC and ClickPipes connectivity explorationexplains why networking docs mention public IAM + TLS, multi-VPC connectivity, and historical ClickHouse integration work
2026-03-11Kafka export and ClickHouse POC iterationscaptures the experiments that led to the current optional MSK Connect S3 sink path
2026-03-12Kafka UI added behind the shared ALBexplains the third public hostname and extra ECS service in the roots
2026-03-15Public ALB replaced API Gateway + VPC Linkexplains why the current ingress model is simpler than older design documents
2026-03-15S3 gateway endpoint added for private subnetsexplains why the VPC module now includes an S3 gateway endpoint
2026-03-16Terraform roots split into staging and prodestablishes the current environment model
2026-03-16Events service clarified and dashboard backend addedexplains the dual-service ECS model, dashboard ECR, dashboard secret, and RDS
2026-03-27Staging operating hours automation and manual Kafka cleanupexplains why staging now schedules only start/stop while keeping Kafka topic cleanup as a manually invoked Lambda
2026-03-31Scoring service and Camunda addedexplains the extra ECS services, scoring ECR/secret, Camunda secret/RDS, and internal Service Connect path
2026-04-02Scoring moved off the public ALBexplains why scoring no longer has a public hostname and is now reachable only over internal Service Connect
2026-04-04DevOps Agent investigation test and broader alarm coveragerecords the DevOps Agent proof of concept while explaining the per-service ECS alarms and the new RDS CPU and DB load alarms that remain operational
2026-04-24ClickHouse Cloud Prometheus agent added for New Relicexplains the ClickHouse Cloud metrics ingestion path, dedicated collector secret, and New Relic dashboard-first rollout now available through both environment roots
2026-05-08Second staging workload root added on the shared staging foundationexplains why terraform/staging2 exists, why it reuses the staging VPC/subnets/security groups/MSK/ECRs, and why its ECS task definitions are treated as bootstrap-only artifacts

How to use the archive

  • Use the archive when you need rationale, migration context, or earlier tradeoff discussions.
  • Do not treat every archived proposal as still implemented.
  • Cross-check the Terraform roots before promoting archive notes into operator runbooks.
note

The Decisions section is intentionally curated. It is not a generated mirror of openspec/changes/archive.