README

This category is a record of facts.

Each topic here documents a specific limitation of Talkyard discovered through active use. Not opinions, not complaints — observed behaviors that constrain what can be built or expressed within Talkyard's current design.

Why This Exists

Talkyard is the interim platform LOGOS runs on. It is good software, deliberately kept simple by its developer. That simplicity involves tradeoffs. When those tradeoffs collide with what LOGOS needs, the collision gets recorded here.

These topics are the source events. The LOGOS Requirements subcategory is the read model projected from them. Each limitation discovered here generates one or more concrete requirements for the LOGOS software being built to replace Talkyard.

How Topics Are Structured

Each limitation topic contains:

• What the limitation is — precise description of the behavior
• How it was discovered — the specific situation that surfaced it
• Impact — what it prevents or forces
• Workaround — what's being done in the meantime, if anything
• Status — whether a workaround is in place, feedback submitted, etc.

The LOGOS requirement generated by the limitation lives in LOGOS → Requirements, not here. Cross-references link the two.

What This Is Not

These are not bug reports. Talkyard's limitations are deliberate design decisions made by its developer with different priorities than LOGOS has. They are recorded here without judgment — as constraints that the LOGOS software will not have.

Immutability

Limitation topics are not edited once posted except to add workaround status updates. The discovery is an immutable fact. If understanding of a limitation deepens, a new topic is created or a reply is added — the original post is not rewritten.