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 sparki project. Read top to bottom if you're new; no prior context assumed.
More about this project on the Sparki hub.
Use when: onboarding to the sparki-tools monorepo; deciding which service owns a new feature; tracing a request across api-engine, deploy-loco and auth-shield
Use when: adding a new capability to api-engine; deciding whether a feature belongs in a subsystem or in core; debugging which subsystem owns a failing pipeline stage
Use when: writing or reviewing a sparki pipeline YAML; validating a pipeline-config payload before submission; adding a new step field to the v1 schema
Use when: investigating a stuck build that never reached a worker; deciding which queue a new event type should go on; tuning publisher confirms or retry backoff
Use when: debugging a stuck build; tuning the build context timeout; tracing how a BuildJob becomes a recorded build row
Use when: publishing a build from a non-engine service; diagnosing a malformed message in builds.failed; extending the message with new fields
Use when: wiring a new live event type into the dashboard; debugging missed updates on the build stream; estimating fan-out cost of a broadcast
Use when: writing a deployment status query; explaining why a deploy is `validating` vs `pending`; adding a new terminal status
Use when: choosing direct vs blue-green vs canary for a new service; investigating an unexpected auto-rollback; wiring a new platform adapter into deploy-loco
Use when: adding support for a new language or framework; debugging an incorrect framework attribution; writing a new project detector
Use when: adding a new metric type to the scoring engine; rendering a quality score on the dashboard; debugging a flaky-test detection result
Use when: deciding whether a new signal should be a metric, log, or trace; adding a span to a cross-service request; writing an SLO for a new pipeline stage
Use when: writing the Sparki tagline or homepage hero; explaining what category Sparki is in
Use when: writing audience copy for the landing page; briefing a designer on who the user is at the moment of contact
Use when: writing or reviewing any Sparki copy; deciding whether a tagline draft sounds like Sparki
Use when: explaining why Sparki publishes a design journal each sprint; framing the cross-channel cadence to a stakeholder
Use when: answering 'how is this different from X' on a sales call; writing a comparison block on the landing page