Skip to content

Concepts: promotion — from a record to a chip - #42

Open
saucissefarciehumaine-prog wants to merge 1 commit into
TigerTag-Project:mainfrom
saucissefarciehumaine-prog:redo/promotion-section
Open

saucissefarciehumaine-prog wants to merge 1 commit into
TigerTag-Project:mainfrom
saucissefarciehumaine-prog:redo/promotion-section

Conversation

@saucissefarciehumaine-prog

Copy link
Copy Markdown
Contributor

One page, one subject, branched from current main (01fea74) — not stacked on anything.

The question this answers. "I have a chipless spool in my inventory — what do I get when I write it to a chip?" Seven places in the wiki say a record is promotable to a real chipglossary.md, guides/start-for-free.md, philosophy/second-life.md, products/tiger-studio.md, products/tigerpod.md, guides/README.md — and every one of them points at concepts/universal-filament-identity.md, which names promotion in a single clause and never says what comes out. This adds the answer to the page they all point at, as a section, not a new page — the home you suggested in #20.

The core is the line you confirmed. A promoted TigerData+ becomes a TigerTag+ — still identified, still not signed, as a two-row table (what you promote → what you get → why), then the two consequences: promotion never produces a Certified, and it is reversible because chips are never write-locked.

Dropped from #20. Link to twin Spool (no home in the repo) and the desktop-only / Connect cannot write a record claim (no pointable source). The page says only what is documented: Tiger Studio promotes in one step, atomically.

Dropped since #28 landed. The section originally closed on "with a TigerPOD, both chips are written in one pass". That fact now has a clear owner — guides/twin-tag-pair.md, plus products/tigerpod.md and guides/start-for-free.md — and pairing is not promotion, so the sentence is gone rather than restated.

One thing to confirm. The state diagram had TigerData+ --"write to a chip"--> TigerTag, which contradicts the bullet directly below it: "Write a catalogue product into that chip rather than hand-typed values and it is a TigerTag+". A TigerData+ carries a catalogue product by definition, so the edge has to land on TigerTag+. Moved in both languages — fenced code must stay identical for check:i18n. If the edge was intentional, say so and I'll revert that hunk; the section stands without it.

Not touched: the promote a chipless spool TODO in guides/README.md. That list is about guides, and whether a concept section retires a planned guide is your call, not mine.

Two files, both locales. Existing page, no new route, no sidebar entry. i18n/fr mirror updated with its sourceHash refreshed. pnpm check:docs, check:i18n and build all green locally (121 pages, all internal links valid).

🤖 Generated with Claude Code

A section of universal-filament-identity.md (its home), not a new page.
What promotion produces depends only on what went in: a TigerData becomes a
TigerTag; a TigerData+ becomes a TigerTag+ — still identified, still not
signed. Never a Certified. Reversible: chips are never write-locked.

Also makes the state diagram consistent with the text: the 'write to a chip'
edge from TigerData+ now lands on TigerTag+ (it pointed at TigerTag). Same
change in the FR mirror, as fenced code must stay identical.

i18n/fr mirror updated, hash current. check:docs, check:i18n and build green
locally.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@vercel

vercel Bot commented Sep 18, 2026

Copy link
Copy Markdown

@saucissefarciehumaine-prog is attempting to deploy a commit to the Tiger-Project Team on Vercel.

A member of the Team first needs to authorize it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant