Storage · /home/box/agents/fyj-founder-bot/directory/hashing-and-legal-tech-valuation/sources/skill/references/markdown-contract.md

Markdown archive contract

One file, UTF-8, GitHub-flavored Markdown. Filename: {slug-of-title}.md.

Required sections (in order)

Title — # {share title}
Deck — one line: complete archive of a Gemini {model} conversation
Integrity note — faithful export; user text verbatim; Gemini Markdown original
Document control — table: title, short URL, alternate short URL (if any),
canonical URL, share ID, conversation ID, model + fingerprint, participants,
turn count, created/published labels from the share page, first/last message
in UTC and in the user’s timezone when known, attached media summary, tools used
Contents — linked TOC. Heading slugs: lowercase, non-alphanumerics → -,
trim hyphens. Keep TOC links in sync with those slugs.
Timeline — table of turn #, role, UTC, local, message ID
Attached media — every file: name, MIME, upload time, share-API status,
subject. Embed recovered images. State clearly when a binary is unrecoverable.
Conversation — one ### Turn N — {short heading} per turn:
- one-line italic blurb
- #### User · {timestamp}
- attachment callout if any
- user body in a ```text fence (verbatim, trailing spaces stripped only
at the fence edge)
- #### Gemini {model} · response \{rc_…}`- tools callout if search/etc. ran - Gemini body as **raw Markdown**, not re-fenced, not rewritten ----` between turns
Search queries / tools — table of query × turn; note if citation URLs
were absent from the payload
Technical identifiers — IDs + unix/nano timestamp table
Status of the thread — last open question; whether thinking blocks,
Canvas, generated images, or code cells existed
Provenance — source links; “archive, not legal advice / not independent
verification” if the thread cites market figures

Rules

Do not summarise, paraphrase, or “clean up” user spelling (sme’s, levarging).
Do not drop Gemini’s factual asides (e.g. security-by-obscurity correction).
Do not add a new analysis section unless the user asked for one on top of the archive.
Prefer tables over prose for metadata.
If a typeset HTML reader wraps Markdown images, render <img> only — never
<figure> inside a <p> (hydration mismatch).

# Markdown archive contract One file, UTF-8, GitHub-flavored Markdown. Filename: `{slug-of-title}.md`. ## Required sections (in order) 1. **Title** — `# {share title}` 2. **Deck** — one line: complete archive of a Gemini {model} conversation 3. **Integrity note** — faithful export; user text verbatim; Gemini Markdown original 4. **Document control** — table: title, short URL, alternate short URL (if any), canonical URL, share ID, conversation ID, model + fingerprint, participants, turn count, created/published labels from the share page, first/last message in UTC and in the user’s timezone when known, attached media summary, tools used 5. **Contents** — linked TOC. Heading slugs: lowercase, non-alphanumerics → `-`, trim hyphens. Keep TOC links in sync with those slugs. 6. **Timeline** — table of turn #, role, UTC, local, message ID 7. **Attached media** — every file: name, MIME, upload time, share-API status, subject. Embed recovered images. State clearly when a binary is unrecoverable. 8. **Conversation** — one `### Turn N — {short heading}` per turn: - one-line italic blurb - `#### User · {timestamp}` - attachment callout if any - user body in a ` ```text ` fence (verbatim, trailing spaces stripped only at the fence edge) - `#### Gemini {model} · response \`{rc_…}\`` - tools callout if search/etc. ran - Gemini body as **raw Markdown**, not re-fenced, not rewritten - `---` between turns 9. **Search queries / tools** — table of query × turn; note if citation URLs were absent from the payload 10. **Technical identifiers** — IDs + unix/nano timestamp table 11. **Status of the thread** — last open question; whether thinking blocks, Canvas, generated images, or code cells existed 12. **Provenance** — source links; “archive, not legal advice / not independent verification” if the thread cites market figures ## Rules - Do not summarise, paraphrase, or “clean up” user spelling (`sme’s`, `levarging`). - Do not drop Gemini’s factual asides (e.g. security-by-obscurity correction). - Do not add a new analysis section unless the user asked for one on top of the archive. - Prefer tables over prose for metadata. - If a typeset HTML reader wraps Markdown images, render `<img>` only — never `<figure>` inside a `<p>` (hydration mismatch).