Skip to content

2026-08-07 Agentic monorepo delivery research

Researched current primary-source practices for rapid integration, secure CI/CD, releases, progressive delivery, and agent evals.

Work Done

  • Researched current (2025–2026) agentic-monorepo software delivery patterns and delivered a sourced report distinguishing documented facts from recommendations.
  • Covered isolated agent worktrees and repository instructions, small PRs, CODEOWNERS, GitHub merge queues and the merge_group CI event, affected builds and remote caching, SLSA/Sigstore/GitHub attestations, monorepo versioning with Changesets and release-please, GitOps/canaries with Argo Rollouts/CD, and agent eval/telemetry using OpenAI and OpenTelemetry guidance.
  • Consulted primary documentation from GitHub, Nx, Bazel, SLSA, Sigstore, Changesets, release-please, Argo, OpenAI, OpenTelemetry, and DORA. No application code or infrastructure was changed.

Lessons Learned: Pitfalls

  • The configured Serper web-search skill had no API key, so source discovery through that route was unavailable. Known primary-source URLs were fetched directly and checked for successful redirects instead.
  • The knowledge-repository git pull --ff-only initially failed with “Cannot fast-forward to multiple branches” despite a normal-looking branch; explicit git fetch origin main plus git merge --ff-only origin/main worked. The begin-work instruction may need a more deterministic pull command.
  • Several vendor documentation URLs redirect as navigation structures change; durable notes should favor canonical destination URLs or periodically validate links.

Lessons Learned: Improvements

  • A durable infrastructure SOP could record an approved baseline for agent-authored changes: isolated worktrees, narrow change manifests, merge-queue configuration including merge_group, trust boundaries for PR versus release jobs, and minimum eval evidence.
  • A repository-specific decision record mapping current tooling to the desired operating model would make generic guidance actionable: affected-task engine/cache, release/version groups, provenance/signing policy, deployment controller, SLI thresholds, and telemetry schema.
  • Add a link-checking job for external primary sources if this research is promoted into durable wiki documentation.
Navigation

Type to search…

↑↓ navigate↵ selectEsc close