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 traceo project. Read top to bottom if you're new; no prior context assumed.
More about this project on the Traceo hub.
Use when: deciding which service owns a new endpoint; debugging cross-service request flow; onboarding to the Traceo backend; adding a route and wondering why it 404s in production
Use when: adding a new requirement field to migrations; writing a new traceability relationship type; debugging why a link exists in one direction only; working out which tenant a user belongs to
Use when: approving a requirement for implementation; deprecating an obsolete requirement; filtering the traceability matrix by layer; assuming the server will stop an out-of-order status change (it will not)
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: adding a new tenant-scoped table; debugging empty result sets that should have rows; auditing cross-tenant leakage risk; writing a test that claims to prove isolation
Use when: tuning MCP_RATE_LIMIT or ENGINE_RATE_LIMIT; debugging unexpected 429 responses; exempting a new health-check path; assuming the MCP server is rate limited (it is not, in production)
Use when: uploading a CSV requirement set through the engine; debugging a stuck `running` job; extending the ingestion validators; wondering why ingested rows never appear in the requirements table
Use when: registering a new MCP tool; auditing the tool catalogue; working out what actually guards a tool call in production
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: tuning embedding recall vs latency; rebuilding the HNSW index after a model swap; adding a new RAG-backed tool
Use when: writing an alert and checking the metric is actually emitted; scraping Traceo with Prometheus; answering 'do we have correlation IDs?'; reading the tenant-resolve counters
Use when: writing the Traceo homepage hero or one-line description; explaining what category Traceo lives in
Use when: deciding which case study or testimonial to lead with; qualifying an inbound lead before a demo
Use when: writing copy for the Traceo site, docs, or a launch post; reviewing a draft for voice match before it ships
Use when: explaining what success looks like for Traceo's first program; answering 'why not just ship the MCP server first'
Use when: answering 'how is Traceo different from DOORS, Polarion, or Jama'; answering 'how is Traceo different from a Linear-style tool for specs'
Use when: touching checkout, change-plan or entitlements in the web client; explaining why Solo limits are shown but never enforced; turning the founding offer on or off; debugging a CHECKOUT_DISCOUNT_REFUSED or BILLING_NOT_CONFIGURED response
Use when: a merge is green but production might not have it; reading a deploy-observability failure page in #pipeline; classifying a Railway deploy status you have not seen before; deciding how long an in-flight deploy may sit before it counts as stuck
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: auditing whether a control (test, middleware, gate) actually runs; writing a card, runbook or comment that says a mechanism does something; three documents agree and you are about to stop checking