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.
Field-repair playbook. Symptoms, likely causes, and the fixes that worked last time. Read top down when something is on fire.
Use when: debugging packet corruption; adding a new envelope field; explaining wire format to someone
Use when: tuning MCP_RATE_LIMIT or ENGINE_RATE_LIMIT; debugging unexpected 429 responses; exempting a new health-check path
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: issuing tokens from an external auth provider; debugging TOKEN_VERIFICATION_FAILED in dev; adding a new authorization claim
Use when: adding a new wire message type; debugging an INVALID_MESSAGE error; porting changes to the TypeScript mirror
Use when: wiring a new document property; debugging RELAY_DATABASE_URL outside Docker; writing a test that needs a fresh document
Use when: writing a pre-send validator that aborts bad inputs; writing a post-send checker that drives the verified counter; debugging why kick aborted before sending
Use when: computing prompt usage stats outside of eva show; debugging promotion gate counts; auditing performance medians for a prompt
Use when: designing gate conditions; debugging unexpected vetoes; understanding fail-open vs fail-closed behaviour
Use when: understanding how iris-service stores data; debugging registry behaviour; planning the PostgreSQL migration
Use when: understanding cross-system identity mapping; implementing namespace resolution; debugging mapping conflicts
Use when: onboarding a new producer repo; debugging why Scope shows stale data; deciding where to add a new write path
Use when: adding a new field to the pellet manifest; debugging a checksum mismatch on extract; deciding whether a workspace is frontend, backend, or polyglot
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: 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: debugging a redirect loop between /auth/login and a protected route; adding a new protected URL prefix; investigating why the session cookie is missing in production
Use when: adding support for a new language or framework; debugging an incorrect framework attribution; writing a new project detector
Use when: writing a unit import statement; debugging a `parseUri` failure; registering a new domain in the schema enum
Use when: deciding which service owns a new endpoint; debugging cross-service request flow; onboarding to the Traceo backend
Use when: adding a new field to LCBMessage and need to update all serialisation sites; debugging a wire-format mismatch between two peers running different versions; reviewing the on-wire byte layout produced by to_bytes()
Use when: onboarding onto the TimeChain access-control layer; debugging an unexpected AccessDenied error from AegisSystem; deciding which AEGIS subsystem owns a new security feature
Use when: designing a new AEGIS commitment for a previously untracked attribute; debugging a commitment verification mismatch in CommitmentManager; understanding why a nonce is generated with blake3 rather than a CSPRNG
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: debugging AUTH_REQUIRED errors on the relay; adding a new privileged message type; wiring a new identity provider
Use when: adding a new privileged WS handler; debugging clients that never receive broadcasts; tracing why a connection was dropped
Use when: adding a new operation type; debugging operation_rejected on the relay; implementing client-side optimistic apply
Use when: writing a new sync query; designing a snapshot compaction job; debugging slow timeline queries
Use when: authoring a new meta.yml; debugging eva doctor failures on required fields; preparing a prompt for skill export
Use when: debugging why a {{var}} did not substitute; deciding between --var, --var-file, and --case; writing a guard.sh that overlays variables
Use when: starting a new GRACE session; debugging context loss between turns; explaining how GRACE maintains state
Use when: creating or validating a new sprite; understanding the JSON Schema structure; debugging fingerprint mismatches
Use when: designing a new chain; debugging chain execution failures; understanding step-to-step data flow
Use when: creating a council via the API; executing chains programmatically; debugging 409 GATE_VETO responses
Use when: debugging unexpected redirect loops back to airlock; rotating MERIDIAN_SESSION_SECRET; reasoning about session age on the F9 dashboard
Use when: wiring an external IdP to the Engine via JWKS; tuning rate limits before a load test; debugging a 429 in production
Use when: adding a new dashboard route; writing a Playwright test for a new pellet flow; debugging a 401 redirect after token expiry
Use when: writing a migration that touches user identity; debugging duplicate subscription rows; implementing GDPR delete
Use when: adding a new event type to a protobuf file; debugging duplicate event delivery; tracing a request across services with correlation_id
Use when: adding a new achievement definition; debugging why an achievement did not unlock; writing a unit test for criteria evaluation
Use when: adding a new leaderboard variant (per-tier, monthly); debugging stale rank values; estimating Redis memory for N users
Use when: debugging why a slug returns 404 instead of redirecting; understanding how the edge worker decides between redirect, proxy, and landing; explaining the request path to an infrastructure engineer
Use when: debugging 429 errors for specific users; adjusting rate limits for a new subscription tier; understanding how Redis enforces sliding windows
Use when: explaining link health scores to a user; debugging why a link's pawprintz dropped suddenly; designing new gamification mechanics
Use when: setting up a new environment (kitten/cat/lion); debugging why the landing page is not loading; understanding the Cloudflare → Vercel routing
Use when: adding a new BFF route exposed to the browser; debugging CORS or cookie failures on a fetch from rover; deciding whether a call belongs in a Server Component or via the proxy
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: adding a new metric type to the scoring engine; rendering a quality score on the dashboard; debugging a flaky-test detection result
Use when: adding a new XP source for a content action; debugging a leaderboard rank that disagrees with a user's profile
Use when: checking whether a timeline counts toward the active_timelines stat; deciding which TimelineStatus to pass when forking an ephemeral branch; debugging why nodes_before_timestamp returns an empty slice
Use when: adding a new permission to a tool; debugging 401/403 responses; wiring a new role tier
Use when: anchoring an AEGIS proof batch to the VEST audit chain; debugging why ConsistencyProofManager.verify_proof returns false on a freshly created proof; reviewing the XOR consistency check used as a placeholder for Merkle linking
Use when: debugging a site stuck mid-provision; extending the saga with a new state; extracting the orchestrator into choco-forge
Use when: implementing a new timeline UI control; debugging timeline_snapshot returning the wrong content; tuning timeline bucket size for chatty edits
Use when: adding a new case to eval.yml; choosing between assertions and a rubric judge; debugging a failing eva eval run
Use when: exporting a ready prompt as an Anthropic skill; debugging an export-skill blocked by doctor; understanding the SKILL.md frontmatter eva produces
Use when: monitoring FNP systems; setting up alerts; debugging performance issues
Use when: authoring a new STRATT unit and choosing its type; debugging an invalid lifecycle transition error; resolving a CRDT merge conflict on unit status
Use when: adding a choco:// import to a STRATT unit; debugging an FM-02 broken-import on a foreign URI; wiring up the HTTP-mode resolver for production
Use when: verifying sprite identity across IRIS and MERIDIAN; debugging fingerprint mismatches in federation; understanding the 5-stage verification pipeline
Use when: deploying iris-service locally or in production; understanding the full infrastructure stack; debugging observability issues
Use when: designing a graph.json for a new repo; debugging why a node never starts; tuning max-parallel for a fleet run
Use when: vendoring kahn_emit.py into a CI producer; validating a transitions.jsonl line; debugging an event rejected by Scope
Use when: implementing authentication in a new LORE page; understanding role-based access control in LORE; debugging permission denial issues
Use when: understanding how LORE and CAIRNET share the graph component; porting the graph to a new app; debugging graph rendering issues
Use when: understanding how LORE decisions trace back to CAIRNET stones; debugging the graduation backlink display; implementing a new provenance feature
Use when: debugging users who land on stratt.dev unauthenticated despite an airlock session; wiring a new devarno-cloud apex to airlock SSO; rotating airlock's Ed25519 signing keypair
Use when: shipping an audit-record link to a third party; debugging an Audit page that renders 'unable to verify'; reasoning about whether STRATT infrastructure is required to verify a record
Use when: debugging why the CASA Petrova zone is stale; rotating HUBBLE_INGEST_TOKEN; explaining the daily 07:00 UTC snapshot path
Use when: submitting a RALPH run from the console UI; debugging an SSE stream that stalls mid-run; moving the worker between in-process and sidecar transport
Use when: adding a new push notification type; scaling realtime-gateway horizontally; debugging dropped SSE events
Use when: debugging why a slug does not redirect; understanding the edge worker's internal flow; optimising redirect latency
Use when: debugging stale link data; designing cache invalidation for a new feature; explaining why the same slug resolves differently on different devices
Use when: debugging why a new link is not immediately resolvable at the edge; understanding the async write pattern for edge cache; designing bulk operations that affect many links
Use when: implementing a white-label short link; debugging why a proxied page shows broken assets; understanding path rewriting at the edge
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: debugging a stuck build; tuning the build context timeout; tracing how a BuildJob becomes a recorded build row
Use when: debugging a 401 or 429 response that never reached a downstream service; adding a new route group that proxies to a backend service
Use when: deciding whether to prune stale branches before storage overhead exceeds the configured cap; tuning max_active_timelines based on measured fork probability; debugging unexpectedly high storage usage in a multi-branch deployment
Use when: adding a new requirement field to migrations; writing a new traceability relationship type; debugging missing reverse links
Use when: uploading a new CSV requirement set; debugging a stuck `running` job; extending the ingestion validators
Use when: debugging a VestError::InvalidSignature returned from ProofVerifier::verify_signature; constructing a valid AuditSignature for a new signer in an integration test; tracing how current_hash propagates through a multi-depth chain
Use when: implementing a new MCP tool for CAIRNET; understanding how agents interact with the platform; debugging MCP provider issues
Use when: implementing agent authentication in CAIRNET; understanding Sybil attack risks in auto-graduation; debugging identity provenance issues
Use when: investigating runaway position-id growth; debugging concurrent insert ordering; porting the position generator to a new client
Use when: implementing or debugging fingerprint computation; cross-system identity verification; understanding the STRATT-compatible hash pipeline
Use when: designing a new API endpoint between LORE and pebble; debugging shape mismatches between LORE and pebble responses; understanding failure semantics in LORE
Use when: debugging missing or duplicate click counts; understanding how analytics data flows from edge to warehouse; explaining the async tracking design to a product manager
Use when: implementing password-protected links; debugging why a protected link shows a prompt instead of redirecting; understanding the edge vs. API split for protection
Use when: debugging why a user's tier did not update after payment; adding a new subscription plan; understanding webhook idempotency
Use when: adding a new tenant-scoped table; debugging empty result sets that should have rows; auditing cross-tenant leakage risk
Use when: verifying that a specific operation is included in the audit log without replaying the full log; computing the root hash from a leaf after receiving a ProofPath over the wire; debugging why MerkleProof::verify returns false for a newly created proof
Use when: implementing a gRPC client that submits or fetches VESTProof messages; adding a new compliance framework marker to an existing AuditEntry; mapping Rust struct fields to their protobuf counterparts when debugging serialisation mismatches
Use when: validating that a Roughtime timestamp meets the ±100ms legal precision target from SRS SEAL-NF-003; debugging a TimestampProof that passed threshold but has a radius_us outside acceptable bounds; selecting between RoughtimeProof, RFC3161Proof, and BlockchainProof for a given compliance requirement
Use when: debugging why a message is stuck in the DAG and never delivered to the application; tracing a causal ordering violation in a test replay; reviewing Algorithm 1 correctness under concurrent message arrivals
Use when: debugging why two peers have diverged state_hash values after a merge; adding a new operation type to AutomergeState and need to understand the serialisation contract; reviewing whether the state_hash algorithm is suitable for integrity checking
Use when: implementing the graduation flow; debugging a graduated stone; understanding the CairnGraduationService
Use when: understanding the end-to-end insert operation; implementing insert operations; debugging insertion issues
Use when: designing chain execution logic; debugging vetoed or failed chains; understanding the synchronous execution model
Use when: tracing a chain execution through the entire system; debugging performance bottlenecks; understanding the full request lifecycle
Use when: implementing a new LORE page or route; understanding how LORE pages connect to each other; debugging a data flow issue in the LORE API
Use when: understanding how decisions relate to each other; debugging the force-directed layout; porting the graph primitive to another system
Use when: understanding why LORE and CAIRNET data are separate; designing a new query that touches both domains; debugging a graduation issue
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
Use when: designing a new feature that touches users, links, or achievements; understanding the API response shape for the dashboard; debugging why a link shows the wrong status or score
Use when: debugging login loops or session expiry; understanding how meow-web authenticates without its own user database; implementing SSO with Airlock in another project
Use when: debugging encoding errors; optimizing packet size; implementing a new encoder
Use when: debugging why the broadcast root keeps changing unexpectedly under topology churn; evaluating whether the Prim's-algorithm rebuild every 200 ms is creating a latency spike; tracing the broadcast path for a message originating from a non-root peer
Use when: debugging 401 errors across different clients; adding a new auth mechanism to purr-api; auditing the security surface of the API