<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>Founder Engineering Field Notes</title>
  <id>https://psbrau-tech.github.io/founder-engineering-field-notes/</id>
  <updated>2026-09-24T00:15:42+00:00</updated>
  
  <entry>
    <title>A Successful Docker Build Does Not Mean You Built a Runnable Release</title>
    <id>https://psbrau-tech.github.io/founder-engineering-field-notes/articles/container-startup-health-before-push/</id>
    <link href="https://psbrau-tech.github.io/founder-engineering-field-notes/articles/container-startup-health-before-push/"/>
    <updated>2026-09-23T00:00:00+00:00</updated>
    <summary>CI should start and health-check the exact container image before publishing it, because a successful image build does not prove the packaged process can run.</summary>
  </entry>
  
  <entry>
    <title>CloudFormation Generated Role Names Can Break Least-Privilege IAM Twice</title>
    <id>https://psbrau-tech.github.io/founder-engineering-field-notes/articles/cloudformation-generated-role-names-and-rollback/</id>
    <link href="https://psbrau-tech.github.io/founder-engineering-field-notes/articles/cloudformation-generated-role-names-and-rollback/"/>
    <updated>2026-09-23T00:00:00+00:00</updated>
    <summary>When CloudFormation generates IAM role names, least-privilege policies must match the physical role identity on both the forward and rollback paths.</summary>
  </entry>
  
  <entry>
    <title>CloudFormation Least Privilege Can Fail Outside the Service You Think You Are Deploying</title>
    <id>https://psbrau-tech.github.io/founder-engineering-field-notes/articles/cloudformation-provider-side-api-dependencies/</id>
    <link href="https://psbrau-tech.github.io/founder-engineering-field-notes/articles/cloudformation-provider-side-api-dependencies/"/>
    <updated>2026-09-23T00:00:00+00:00</updated>
    <summary>CloudFormation resource operations can depend on adjacent-service APIs, so least-privilege fixes should follow the exact denied action rather than the template&apos;s obvious service boundary.</summary>
  </entry>
  
  <entry>
    <title>GitHub Actions OIDC AccessDenied May Be a Trust-Policy Problem, Not a Permission-Policy Problem</title>
    <id>https://psbrau-tech.github.io/founder-engineering-field-notes/articles/github-actions-oidc-trust-policy-diagnosis/</id>
    <link href="https://psbrau-tech.github.io/founder-engineering-field-notes/articles/github-actions-oidc-trust-policy-diagnosis/"/>
    <updated>2026-09-23T00:00:00+00:00</updated>
    <summary>When GitHub Actions cannot assume an AWS role, diagnose OIDC trust claims before widening the role&apos;s service permissions.</summary>
  </entry>
  
</feed>
