Skip to content

docs: keep a real tuned roster, and the script that sizes it #55

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
CryptoJones merged 1 commit into from
Aug 27, 2026
Merged

docs: keep a real tuned roster, and the script that sizes it #55

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -144,6 +144,11 @@ declare the same `lineage:`. It is never fatal — a deliberate duplicate is a
legitimate thing to want — but it must not be silent, because it is invisible in
the answers themselves and it falsifies the one claim the tool makes.

Two config files ship with the repo. `FlatlineRoundtable.yaml.example` is the
annotated template — every option, with the reasoning for each. `examples/full-roster.yaml`
is a real thirteen-lane roster, kept because a tuned config is mostly *numbers
you had to measure*, and those are worth reading before you pick your own.

Every run writes a transcript to
`~/.local/share/flatline-roundtable/transcripts/`, because answers that exist
only in a terminal scrollback are answers waiting to be lost.
Expand Down
Loading
Loading