Skip to content

Deploy previews under a preview rule with enforcement on (D7) - #4055

Draft
nick-potts wants to merge 6 commits into
mainfrom
t3/sec04-d7-previews
Draft

nick-potts wants to merge 6 commits into
mainfrom
t3/sec04-d7-previews

Conversation

@nick-potts

Copy link
Copy Markdown
Contributor

Draft. Slice D7 of the 0.4 security program, "Previews under a rule" (checkpoint C3). Work in progress; this body is rewritten before it leaves draft.

The first commit records the program root's preview template decisions (d-plan.md gap 10), taken on 2026-11-10 under the operator's autopilot grant after D7's prototype stopped at its gate.

@coderabbitai

coderabbitai Bot commented Nov 10, 2026 •

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: c2d3c235-3d9c-448e-bb76-56dec39625cd

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

A preview build's grant and a preview's Container changes carry the preview rule, the
image token and, for a reviewed build, the review. The Machine checks each against what
it holds: the derived Namespace, the trusted account or the review, the head it reads,
the inherited Sealed values, and the template. Setup Commands run only in a preview's
first Hook Container here.
…rules

A PR Environment under a preview rule takes the Namespace every Server derives from the
rule and its branch, generated domains holding it, Own Copy Volumes named for their
parent's, and the parent's Sealed values naming the parent. A preview rule's plan
rehearses opening one and undoes it, so the template a Device signs is what every
preview lowers to.
ployz github preview approve rehearses a preview of the environment, prints
what every preview runs, reads and shares from it, refuses shared mounts
without --share-mounts, and signs the rule with the device key. end signs
the rule's last generation. The user docs describe previews on servers
that enforce device approval.
A preview's GitHub build follows its push's run and checks in and asks its
grant under the preview rule the Store finds for the PR Environment's
Deployment. The runner hands each Server a PreviewProof with every
EnsureContainer. A preview build's Actions cache scope names the rule, so
no preview build writes layers a production build reads.

This branch has not been deployed

No deployments
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