Notebook session ended
This session ended after eight hours.
Sign in again to continue from where you left off.
Notebook gate offline
The sign-in service is not responding right now.
Wait a minute and try again, or read what is already public from the hub.
Foundational walk through the nestr project. Read top to bottom if you're new; no prior context assumed.
More about this project on the Nestr hub.
Use when: onboarding to nestr-tools and deciding which submodule owns a change; someone describes nestr as a dependency cache with three components; checking what is live versus pre-production
Use when: adding a field to the pellet header or footer; debugging an E_PID_MISMATCH or payload hash failure; explaining what nest.lock commits to
Use when: tuning the zstd level for pack; explaining what extract verifies before writing a single file; someone treats nestr compression ratio as the product metric
Use when: reading the dashboard's cache page; deciding when to call /api/pellets/prune; explaining which hosted operations Community caps and which it never caps
Use when: wiring a client to the hosted engine; adding an engine route and choosing its middleware; auditing which routes are open, authenticated, rate-limited or capped
Use when: wiring web or another client to the engine with a JWT; debugging a 401 from the engine; explaining what the per-IP rate limiter really does
Use when: subscribing a new client to live cache events; deciding whether to invalidate a TanStack Query cache on an event; debugging why the dashboard never refreshes after a compress
Use when: writing a Grafana panel against engine series; a supply-chain panel shows zeros and you need to know whether that is real; adding a counter emitted by a CLI verb
Use when: diagnosing missing nestr_* series in the central Folio dashboard; tuning push interval to reduce egress cost; deciding whether to add a new metric upstream of the federation cut
Use when: deciding which Perch service answers a given operator question; adding a new SLO or cost rule; wiring a deploy gate to error-budget compliance
Use when: writing a fresh workspace config from scratch; adding a new service to an existing workspace; deciding what conflict_resolution mode is safe for sync
Use when: adding a dashboard route; debugging a 401 redirect or an engine call without a token; telling a prospect which dashboard screens show real data
Use when: adding a service that must clone after another; debugging an assemble that runs services in the wrong order; detecting a dependency cycle in CI
Use when: installing Perch in a fresh cluster; someone assumes the bridge or the custom services ship with the chart; wiring Perch to scrape the registry or the engine
Use when: writing the nestr.tools homepage hero or a one-line description; explaining what category nestr sits in to a non-engineer; someone still pitches nestr as package compression
Use when: deciding whether a feature request fits the audience; writing copy for an outbound channel; someone asks whether nestr is for anyone who wants faster installs
Use when: drafting any short-form copy: headline, social post, one-liner; deciding which verb a feature belongs to; checking whether a sentence overclaims what runs today
Use when: answering 'why should I trust this is still around in two years'; framing the founder story for a press or podcast intro; someone quotes old roadmap dates for Engine v1.0 or a Pro tier
Use when: answering 'how is this different from Nx or Turborepo'; someone calls nestr a dependency cache or a faster npm install; writing a comparison or FAQ answer
Use when: explaining the pricing page to a prospect; someone quotes the old $29 Pro tier or the $199 lifetime offer; deciding whether an item may be listed as included in Early Access
Use when: explaining what registry.nestr.tools does today versus by design; configuring the Rekor backend and witness pool; a customer asks how to publish or claim a namespace
Use when: setting up a signing key or a builder for a namespace; an install refuses with a provenance or signer error; explaining what 'SLSA L3' means in nestr and who decides it
Use when: describing how nestr contains install hooks; a hook fails with a sandbox denial; checking what may be said publicly about the syscall filter
Use when: changing anything that reads plan or billing state; support asks what a lapsed subscription removes; preparing the live-billing switch (G-13-5)
Use when: adding a route that should or should not count against Community; debugging a 402 E_FREE_QUOTA_EXCEEDED or 503 E_USAGE_UNAVAILABLE; explaining what the security record contains per plan