Skip to content

feat: make the runtime layer a zoom tier you can dial away (#86) - #121

Merged
lex00 merged 1 commit into
mainfrom
feat/86-runtime-zoom-tier
Aug 3, 2026
Merged

feat: make the runtime layer a zoom tier you can dial away (#86)#121
lex00 merged 1 commit into
mainfrom
feat/86-runtime-zoom-tier

Conversation

@lex00

@lex00 lex00 commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

Part of #86 — its "new zoom tier below resources" criterion.

behold already descended below the declaration boundary: attachRuntimeContainment nests each owner-referenced child under its declared parent, so a Pod hangs off its Deployment. What it could not do was not descend — the attachment ran at every zoom level, so a project's composites view carried its Pods.

A layer you can't turn off isn't a tier, and "descend below the declaration boundary" implies being able to stay above it. zoom: runtime is now its own stop, and every tier above stops where your source stops.

Why it's a separate stop rather than a detail level

composites / resources / attributes are granularity over what you declared. Runtime is a different axis: what your declaration produced. It's also live-only by nature — owner-referenced children exist in the cluster and never in source — so it rides the overlay and means nothing without an env.

Details worth noting

pruneRuntimeChildren drops the edges touching a removed node along with it. An edge to a node that isn't in the graph renders as a dangling stub, which is worse than the noise it was meant to remove.

A graph with no owner chain is untouched, so AWS and Azure overlays are byte-identical either way — the "gracefully unavailable, never broken or blank" criterion, now true by construction rather than by accident.

399 tests pass, tsc clean, build clean.

Doesn't close #86 — its events/conditions criterion is chant#1402 (conditions landing) plus the behold side to render them.

🤖 Generated with Claude Code

https://claude.ai/code/session_01FBkcXzqjyY1YKWdaDFuqKs

behold already descended below the declaration boundary — `attachRuntimeContainment`
nests each owner-referenced child under its declared parent, so a Pod hangs off
its Deployment. What it could not do was NOT descend. The attachment ran at every
zoom level, so a project's `composites` view carried its Pods.

A layer you cannot turn off is not a tier, and "descend below the declaration
boundary" implies being able to stay above it. `zoom: runtime` is now its own
stop, and every tier above stops where your source stops.

It sits apart from composites/resources/attributes deliberately: those are
granularity over what you DECLARED, and this is a different axis — what your
declaration produced. It is also live-only by nature, since owner-referenced
children exist in the cluster and never in source, so it rides the overlay and
means nothing without an env.

`pruneRuntimeChildren` drops the edges touching a removed node along with it. An
edge to a node that is not in the graph renders as a dangling stub, which is
worse than the noise it was meant to remove.

A graph with no owner chain is untouched, so AWS and Azure overlays are
byte-identical either way — the same "gracefully unavailable, never broken or
blank" the issue asks for, now true by construction rather than by accident.

399 tests pass.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FBkcXzqjyY1YKWdaDFuqKs
@lex00
lex00 merged commit 389bfff into main Aug 3, 2026
1 check passed
@lex00
lex00 deleted the feat/86-runtime-zoom-tier branch August 3, 2026 04:37
@lex00 lex00 mentioned this pull request Aug 3, 2026
4 tasks
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.

runtime tier — descend below the declaration boundary via ownerReferences

1 participant