FAQ
Clear answers about what Socrates does and how to use it well.
The short version: Socrates gives professional teams a better structure for content generation. It does not replace research, editorial judgment, or domain expertise.
Is Socrates a general agent framework?
No. It is a focused generation layer for professional content systems. The goal is not to orchestrate arbitrary tools and agents. The goal is to make content standards explicit before drafting.
Does Socrates verify claims against the web?
Not in the current release. The review stage is aimed at publishability risks such as repetition, unsupported certainty, and AI-flavored phrasing. Teams should still handle factual verification separately.
When should teams use direct, guided, or full mode?
Use direct mode for utility transforms. Use guided mode for normal publishing work like blogs or LinkedIn. Use full mode for high-stakes content where structure and review materially affect the result.
Why not just write a more detailed prompt?
Because a large prompt still hides the standard inside prose. Socrates converts that standard into typed artifacts that are easier to inspect, test, and reuse across a product or team workflow.
Which providers does Socrates support?
The current release ships with an OpenAI-compatible chat-completions adapter. The provider boundary is intentionally narrow so additional adapters can be added cleanly.
Is the website itself production-ready?
The public product site is deployed as a static site and is designed to be served from either GitHub Pages or a standard Nginx docroot. HTTPS can be enabled as soon as the production domain resolves to the deployment server.
Continue
Move from overview to implementation.
The docs page covers installation and commands. The use-case page helps teams decide where the workflow depth is worth paying for.