Problem
The README currently overstates some behavior relative to the implementation.
Examples worth checking:
- “50 personas attack your site in 60 seconds”
- “30 are generated specifically for your audience using Gemini”
From the current backend, the default flow appears closer to a sampled static persona pool with a default agent count of 30.
Proposal
Align product copy with the current implementation, or implement the missing audience-conditioned persona generation for real.
Two valid paths:
- simplify the copy now
- build true audience-conditioned persona overlays/generation and then keep the current copy
Suggested file targets
README.md- frontend landing copy in
app/page.tsx
- any persona-generation path in backend if implemented
Acceptance criteria
- README claims match actual backend behavior
- if audience-conditioned personas exist, they are clearly implemented and traceable in code
Problem
The README currently overstates some behavior relative to the implementation.
Examples worth checking:
From the current backend, the default flow appears closer to a sampled static persona pool with a default agent count of 30.
Proposal
Align product copy with the current implementation, or implement the missing audience-conditioned persona generation for real.
Two valid paths:
Suggested file targets
README.mdapp/page.tsxAcceptance criteria