Comment by spacebacon
12 hours ago
Thank you, I would appreciate additional feedback on how I can improve that?
Edit: its not GPT nor off rocker. This repo empirically proved computational semiotics with the reference to C.S. Peirce, Paul Kockelman, and many other respected contemporary semioticians.
Just try to explain why I should use it and why it's different or better than alternatives - in terms of some qualities of the results rather than how it's implemented
The technical implementation details are also useful to have, but they're a bit hard to parse into "what is this?"
FWIW I'm sympathetic to vibe-coded docs as I'm doing it myself a bit lately, but the agents are bad at it by default because all their context is the how and why of technical decisions made while coding with you
they need specific coaching to get them to try to write for the perspective of a new user
The main reason to use it is the output quality. SRT steers the model toward a consistent target voice or discourse style more reliably than prompting or basic steering, while keeping the base model frozen. The results feel more coherent in tone and perspective across longer outputs, especially when the target style comes from a specific corpus or community. On the sympathetic point about vibe-coded docs: exactly.
1 reply →
Thanks for the feedback … rough and precise equally appreciated. Computational semiotics was empirically proven with this repo. I will work hard to make the findings and content more accessible for everyone.
You should write your readmes by hand. You’ll learn a lot more that way, and it’ll help to ground the project.
It’s not as if they were one shot. 5 repos prior, two published pre-prints on SSRN and thousands of hours back my research that is right there for you to peer review and use freely.