The collection

Look inside somebody else's project.

Not a feature tour. These are real exports — open one and read the decisions someone actually made, the reason underneath each, and the traps they already hit. Then hand it to your own agent.

Publish a Trail from your own project…
Reserved

Nobody has published a Trail yet. Yours would be the first in the case.

Inside · Sync Loop
sha256 d3ce0827a010…

The context sync loop and the services around it.

working on
Harden the extraction retry path
decision
Store context as JSONB rather than normalized tablesThe shape changed every few weeks and migrations became the bottleneck.
decision
Dedupe hot paths on the normalized pathAgents submitted the same file with ./ prefixes and trailing slashes.
landmine
npm ci fails on npm 11 because the lockfile pins helmet 7.2.0
key file
apps/api/src/services/contextSyncService.jsSync service
finding
Two zod instances across workspace packages threw on schema objects crossing the boundary
still open
Should retries share a budget across projects?
Download .dawn10.0 KB

Not pinned to a commit — treat its file-level claims as unverified.

Why this is readable at all

Nothing here is locked up.

A .dawn file is plain JSON. No account to download one, no viewer to install, no format you need our software to open. Diff two in git. Write your own reader. A format you cannot inspect before committing to is not open, whatever its docs say.

Every Trail here went through the same publish gate you would use — scanned for credentials, emails, home paths and names, with each finding resolved by hand before anything went public. How Trails work.

Publishing yours
  1. 1 · work
    Connect DeerDawn and keep working. The brief accumulates on its own — a Trail is what your project already knows, not something you sit down and write.
  2. 2 · review
    When you publish, the scan shows every credential, address and path it found. You clear them one at a time; there is no approve-all.
  3. 3 · publish
    It lands in the case, pinned to the commit it describes.

Your project knows more than you can hand over.

Months of decisions, dead ends and hard-won detail live in one person's head and three chat threads. DeerDawn keeps it as a brief while you work. A Trail is what you hand someone when they need all of it at once.

How Trails work →