Distillation

Date: Aug 5, 2026

• 🔴 [reported-bug] (13:37) User stated they implemented the "standard.site" protocol for their blog, but validation of the latest post fails because document record key ultimate-setup-labs is not a valid TID: “TID is wrong length (expected 13 chars).”
• 🔴 (13:37) User stated that the site.standard.document lexicon requires the record key to be a TID.
• 🟡 (13:37) Assistant planned to trace how standard.site document record keys are derived, compare the implementation with the validator’s TID requirement, update the implementation, and verify generated output for the failing post.
• 🟡 (13:37) Assistant’s ordered work plan: 1. Inspect standard.site implementation and latest post output; 2. Implement TID-compatible document record key generation; 3. Run targeted tests/build and inspect the generated record.
• 🟡 (13:37) Repository files identified for investigation: /home/byk/Code/byk.github.io/scripts/publish-standard-site.mjs, /home/byk/Code/byk.github.io/src/lib/standard-site.ts, and /home/byk/Code/byk.github.io/src/pages/standard-site.json.ts.
• 🟡 (13:37) Repository implementation context: standard.site models one site.standard.publication record plus one site.standard.document record per post, with deterministic record keys; the publication key is self, while document keys currently include post slugs such as ultimate-setup-labs.
• 🟡 (13:37) Existing generated artifacts inspected included public/.well-known/site.standard.publication and dist/standard-site.json; the publication URI uses at://did:plc:kl3s4yablm3fgnxfkn47uy5r/site.standard.publication/self.