Repository navigation
docs(concepts): lift the supply-chain, sandboxing, packages, and stacks guides - #938
Conversation
…ks guides Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 51 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (5)
Comment |
| You can force the CLI to build artifacts locally using a combination of the `--no-fetch` and `--no-cache` flags. | ||
|
|
||
|
|
||
| ## The task sandbox |
There was a problem hiding this comment.
Should we mention the session sandbox here? Its the sandbox you drop into when you use a session, the union of [session] and [stack] stuff in your minimal.toml as well as your loadout.
| - The repository's files and directories, from the repository root downward, but not above it. | ||
| - A `/state` directory, which can be shared between tasks and task invocations by specifying a task `state_key`. Package managers | ||
| are typically wired to cache source downloads and intermediate build artifacts in this directory. | ||
| - Pinhole filesystem mappings, as declared by packages. For instance, the `claude-code` package wires the `~/.claude` directory into task sandboxes so claude-code |
There was a problem hiding this comment.
I think we can drop this one for now while we figure out what to do with [task.patches] sections
De-emphasize `mip` per review feedback: `min` is the primary product surface, while `mip` drives the advanced build plane. Qualify the stacks intro as a build-plane command and drop the `mip update` reference from the upstream config comment in favor of a tool-neutral phrasing, without changing the underlying mechanics. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Layers add definitions rather than override them (from_profile excepted), locked_commit is pinned by min update, the build cleanroom's network carve-out is stated, the claude-code pinhole example is dropped pending the task.patches decision, a session-sandbox section is added per review, profile packages are scoped to tasks, stack docs route dependency adds through min add, and the stacks table defers to the registry as source of truth. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Lifts four concept guides into
docs/concepts/: software-supply-chain, sandboxing, packages (the content-addressed package model), and stacks (renamed from harnesses, all harness/profile wording retired). Links converted to repo-relative.md;minimal <cmd>corrected tomipper the clap definitions. Cross-links to../reference/stack-specs.mdand../reference/cli-mip.mdcurrently dangle and resolve once #863 (and the per-binary CLI reference pages) merge. Verification done: no em-dashes, no harness/profile mentions, no private-repo names, all internal links repo-relative.Note
Add concepts documentation for supply chain, sandboxing, packages, stacks, and profiles
Adds five new Markdown pages under
docs/concepts/covering core Minimal concepts:minimal.toml, and how software is expressed as configuration/state, pinhole mappings, and network access rulesmip init, and declaring build/runtime dependenciesChanges since #938 opened
locked_commitdocumentation to reflectmin updatebehavior [ff5a61c]min addflags [ff5a61c]mip inittomin init[ff5a61c]Macroscope summarized 3d8b938.