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.
CI gates, build pipelines, and the rules that decide what reaches a deploy. Read before changing a workflow or wiring a new check.
Use when: interpreting a History row's status pill; wiring a CI exit-code policy; deciding whether flake_retries should escalate
Use when: writing the Sparki tagline or homepage hero; deciding whether a capability may be named in customer copy; explaining what category Sparki is in, today
Use when: writing audience copy for the landing page; briefing a designer on who the user is at the moment of contact
Use when: a design or copy review reaches for a comparison with another CI tool; answering 'how is this different from X' on a sales call; checking whether a landing-page block may mention a competitor
Use when: adding a new tutorial scenario to the gallery; applying the platform-hosted pattern to another resource; writing a Prometheus alert on the 3-concurrent cap
Use when: understanding the build process; making cross-repo changes; setting up local development
Use when: authoring a new graph.json; rendering a replay after the live graph changed; validating done_when items in CI
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: wiring STRATT into a CI pipeline; choosing between `verify` and `validate`; scoping which commands are safe in Phase 1
Use when: adding a new metric category to the dashboard; explaining why ci.pass_rate_pct reports 100 in a fresh deploy; wiring a real intelligence-signals source to replace the placeholder
Use when: a sparki PR shows no GitHub Actions checks and you wonder if CI ran; running the CI suite for a sparki repo by hand; deciding where a new check belongs after the eu-1 retirement
Use when: interpreting a `stratt ci` failure; writing a refinement that might cross a blocking check; auditing what each FM actually enforces
Use when: vendoring kahn_emit.py into a CI producer; validating a transitions.jsonl line; debugging an event rejected by Scope
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: freezing a baseline before a release review; diffing two baselines to produce a change report; syncing a frozen baseline into a workspace's requirements; wondering why baseline create/freeze returns BASELINE_WRITE_DISABLED
Use when: opening a PR and wondering why no CI ran; dispatching Traceo CI by hand before a merge; reading a red board full of jobs with no runner; asking whether CI blocks a merge (it never has)
Use when: estimating the impact of changing a shared rule; diagnosing a cycle reported by `stratt validate`; writing CI gates that block on fan-out size
Use when: adding a new permission to a tool; debugging 401/403 responses; wiring a CI job to read Traceo without a shared secret; assuming @require_permission protects a route (check ENABLE_RBAC first)
Use when: choosing an LLM invocation backend for the YAO/JAZZ pipeline; wiring a dry-run agent into a test or CI smoke check; adding a new pluggable agent impl behind createAgent
Use when: adding a new doc category to a consumer repo; debugging a docs-invariants CI failure; auditing whether the rank-graph DAG still holds