Add scoped Labyricorn authoring guidance

2026-08-11 22:48:09 -07:00
parent feea2e67de
commit a4ad2ad10a
3 changed files with 160 additions and 0 deletions
@@ -0,0 +1,43 @@
+# Instructions for the Thinkloom exhibition record
+
+These instructions supplement `.labyricorn/AGENTS.md` and apply to the
+`project/` directory.
+
+## Record structure
+
+- Maintain exactly one project record at `project/contents.lr` using
+  `_model: project`.
+- Keep `project_id: thinkloom` stable. It is the durable identity used by the
+  Labyricorn importer and public URL.
+- Keep the repository URL pointed at the canonical Thinkloom source repository.
+  Ask before changing the repository, default branch, project status, author,
+  or start date.
+- Store project-owned visual attachments in this directory and reference them
+  by filename from `contents.lr`.
+- Use descriptive, web-appropriate alternative text whenever the content schema
+  introduces images that require it.
+
+## Editorial guidance
+
+- Write the exhibition page as a concise project narrative, not as a copy of
+  `README.md` and not as release documentation.
+- Verify technical and status claims against the current repository before
+  editing them.
+- Distinguish completed work, formal design work, experimental work, and future
+  work. Do not imply implementation or conformance that the repository does not
+  support.
+- Preserve Thinkloom's established product boundaries: native, local-first,
+  user-controlled, preview-first model assistance, and no hosted browser
+  companion unless the project itself explicitly changes those boundaries.
+- Do not manually add latest-commit, README, license, language, release, issue,
+  or other repository-derived metadata to the body. The Labyricorn importer and
+  repository information card own those values.
+- Keep the summary suitable for project listings and social previews. Keep the
+  body useful to visitors who want to understand the project rather than build
+  it.
+
+## Review requirements
+
+- Check that `logo` and other attachment references resolve within `project/`.
+- Check that Markdown links are intentional and use HTTPS.
+- Re-read the rendered prose for unsupported claims before committing.