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 choco project. Read top to bottom if you're new; no prior context assumed.
More about this project on the Choco hub.
Use when: onboarding to a new choco service repo; deciding which layer a new service belongs in; tracing a request from edge to vault
Use when: publishing a new domain event proto; debugging causation chains in distributed traces; writing a NATS consumer that needs to dedupe by content
Use when: wiring a new consumer to the right stream; deciding which event domain a new proto belongs in; naming a stream for a new factory-equipment service
Use when: debugging a site stuck mid-provision; extending the saga with a new state; extracting the orchestrator into choco-forge
Use when: adding a new fork branching on platform vs user_git; writing a CHECK constraint for a sibling resource table; applying the platform-hosted pattern to another resource
Use when: wiring an analytics consumer to onboarding signals; adding a new step to the onboarding flow; distinguishing skipped from abandoned in the dashboard
Use when: deciding which factory service should own a new pipeline step; tracing a document from ingest to publish; wiring a new factory-equipment service alongside the existing four
Use when: auditing the five-ticket cap enforcement; verifying a ticket signature in a downstream consumer; extending the anti-gaming rules
Use when: adding a new slash command to the editor palette; debugging a smartblock that didn't fan out to webhooks; deciding whether a new editor action needs its own NATS event
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: writing the choco.tools homepage hero; answering 'what should we use for docs?' in a Slack thread
Use when: deciding which audience a marketing page is written for; auditing copy that tries to talk to everyone at once
Use when: drafting a tagline or headline; rejecting a draft that sounds like a generic devtool
Use when: explaining why choco.tools is built on choco; framing the launch sequence to a stakeholder
Use when: rejecting a homepage mock that drifts toward devtool clichés; explaining what choco is not, before saying what it is