18-05-2026, 12:53 AM
(18-05-2026, 12:29 AM)Torsten wrote: You are not allowed to view links. Register or Login to view.(17-05-2026, 10:56 PM)Dunsel wrote: You are not allowed to view links. Register or Login to view.And here's another thought along that line. No mistakes? If you're creating a hoax like the one I described, mistakes are irrelevant. Wrote the wrong letter? So what, now we have a hapax token.
In self-citation, copying words and modifying them IS the text generation method. Every word is a "mistake" in the sense that it's a modification of a source word. The hapax legomenon isn't a mistake — it's a moment where the modification produced a form that happened not to be repeated. The word "daiin" with 836 instances isn't more "correct" than the hapax "You are not allowed to view links. Register or Login to view." on You are not allowed to view links. Register or Login to view. — both were produced by the same process. One was used as a source for further copying, the other wasn't.
The scribe's real challenge is managing repetition. If you copy with too few modifications, you produce text like "qokeedy.qokeedy.qokeedy.qotey.qokeey.qokeey.otedy" on You are not allowed to view links. Register or Login to view. — which doesn't look like language. So you modify: substitute a glyph, add or remove a prefix, combine elements. The "mistakes" create the vocabulary. The exact repeats are what the scribe needs to avoid.
That's very close to what I found in the generator experiments. One of the major problems was preventing obvious visible repetition chains, so the generator ended up developing a kind of “don’t look stupid” local suppression behavior where recent words and near-clones are discouraged even though the system is fundamentally copy/mutate driven.
It never intentionally generates “mistakes.” But because the ledger itself is built from the Voynich vocabulary, including rare and malformed forms, the system naturally reproduces the same kinds of anomalies and hapaxes simply by reusing the same constrained ecology.
Right now, I'm preloading the validation ledger with the Scribe 1 Herbal structure. However, I have also experimented with loading it only with the You are not allowed to view links. Register or Login to view. structure and then, have the 'scribe' expand the ledger whenever they add' a new midfix, suffix, etc. I haven't gotten that working perfectly but I think that was a very viable method. They essentially created the validity ledger as they created the pages. Or, as I suggested in a previous reply, if f1r was not the first page in this production, then the ledger was possibly built from preexisting work.

