Expansion · 03 of 03 · Honest notes

A LambdaFunction, today and next

Today the XR wires up everything around the function and trusts you to have made the function. Next, the XR makes the function too, and that is where the architects' and security team's rules get to live.

A LambdaFunction, today and next Two columns. Left, built on October 3, 2026: a LambdaFunction XR with runtime, architecture and region composes a source repo (handler, Containerfile and cicd.yaml), Glidepath CI/CD that builds one architecture and deploys, and a catalog entry with service-class function. Below, labelled bring your own, today: the function, its execution role and its ECR repository are created by hand before onboarding, and Glidepath's CI/CD only updates them. Right, a proposal: the same LambdaFunction XR with the same few fields also composes the repo, CI/CD and catalog entry as today, plus, drawn as proposals, the Lambda function itself in an approved region with tags and log retention, an execution role with least privilege and a permission boundary, an ECR repository with scan on push and encryption, and a release pin pull request from ADR-0020 that gives cloud services an approval step for Flight environments. BUILT · OCTOBER 3, 2026PROPOSAL · NEXTLambdaFunction XRruntime · architecture · regionSource repohandler · Containerfile · cicd.yamlGlidepath CI/CDbuilds one architecture, deploysCatalog entryservice-class: functionBRING YOUR OWN, TODAYFunction, role and ECR repocreated by hand, before onboardingLambdaFunction XRthe same few fieldsRepo, CI/CD and catalog entrythe same as todayLambda functionapproved region · tags · log retentionExecution roleleast privilege · permission boundaryECR repositoryscan on push · encryptedRelease pin PRADR-0020 · approval for FlightSame request, same few fields. The difference is how much the platform does for you.LEGENDThe requestComposed todayMade by handProposalDeploys into

Shipped small

Bring your own function let the first cloud targets land in two days, with no cloud credentials held by the control plane.

Tested end to end

Lambda, Azure Functions and every cloud target have run end to end. The gap that is left, composing the cloud resource, is written down, not hidden.

Same contract

When the XR starts composing the function, the request does not change. That is the point of putting an API in front.

Hangar · Airframe · Expansion