Skip to content

docs(governance): record the decisions delegated on 2026-09-14 - #48

Merged
EstebanGZam merged 1 commit into
mainfrom
docs/record-decisions-2026-09-14
Sep 14, 2026
Merged

EstebanGZam merged 1 commit into
mainfrom
docs/record-decisions-2026-09-14

Conversation

@EstebanGZam

Copy link
Copy Markdown
Contributor

What changes

docs/Governance and IaC standards program.md §11 gains "Decisions delegated
by the maintainer, 2026-09-14": six decisions, each with what was taken and
where it was delivered. It also names one gap found on the way: no rebuilt root
creates the AWS Load Balancer Controller's IAM role.

Why

On 2026-09-14 the maintainer asked for the remaining pre-bring-up decisions to
be taken and implemented, leaving only the bring-up of the full environments.
Those decisions change what the registers and the roots do, so they are
recorded where the 2026-09-11 delegated decisions already are, and each stays
open to the maintainer overturning it.

Tasks

  • microservice-app-ai-agents specs/001-governance-and-iac-program T022, T028,
    T043, T045 — each decision is recorded here; the register annotations are in
    the microservice-app-ai-agents pull request opened alongside this one

  • microservice-app-ops specs/004-naming-convention-rebuild T003 and the new
    T031 — ticked and added in the microservice-app-ops register pull request
    opened alongside this one

  • The task register is updated in this pull request — not here: this
    repository holds no register for these tasks

  • Every task ticked here was verified by locating its artifact — none is ticked here

How it is verified

Every claim in the table was checked against its artifact on 2026-09-14:

  • cloudtrail-trail-v1.0.0 resolves: terraform init downloads it for
    shd/security.

  • CloudTrail Lake's maintenance date: AWS What's New "AWS Service Availability
    Updates", through the aws-knowledge MCP server.

  • The shd/security saved plan reads Plan: 10 to add, 0 to change, 0 to destroy, with every change a create.

  • gitops#108's approval and merge were re-read with gh pr view 108 --json reviews,mergedAt before ops spec 004 T003 was ticked.

  • The default VPC's emptiness was read through aws ec2 describe-* for its
    network interfaces, instances, endpoints, NAT gateways, peering connections,
    and transit gateway attachments. The backup directory holds 19 JSON files
    and SHA256SUMS.

  • microservice-app-ops#103 and #101 are merged. The gitops Load Balancer
    Controller vendoring is infrastructure/aws-load-balancer-controller/vendor/v3.5.0
    on gitops main.

  • Infrastructure changes: the documentation consulted through the required MCP servers is listed above — N/A: documentation only

Risk and rollback

Documentation only. A decision the maintainer overturns is struck through and
amended in place, as D2 was. Rollback is reverting this pull request.

What this PR does not do

It applies nothing, and changes no rule text or register.

🤖 Generated with Claude Code

Records the decisions the maintainer delegated before the full environments
come up: the CloudTrail design for the state bucket (T043), the teammate
approval that satisfies ops spec 004 T003, how capacity limits L1-L6 apply to
the full roots (T028), who deletes the default VPC (T045), the modules branch
protection (T022), and the Karpenter node identity and queue key. Names the gap
found on the way: no rebuilt root creates the AWS Load Balancer Controller's
role.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@EstebanGZam
EstebanGZam merged commit 5852efd into main Sep 14, 2026
1 check passed
@EstebanGZam
EstebanGZam deleted the docs/record-decisions-2026-09-14 branch September 14, 2026 20:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant