Work, not chat
Projects, decisions, evidence, and next actions persist beyond any single conversation.
The starting point
A chat is too small a container for serious work.
A project crosses sessions, models, machines, and people. It needs state that can be inspected, versioned, verified, and handed to the next participant without a reconstruction exercise.
Ragenie will start with the work itself. Conversations are one interface to that work, not the container that owns it. The harness will run agents inside a durable system whose records remain useful when the model, tool, or operator changes.
What synthesis-native means
The work system is part of the product's structure.
Evidence with progress
A completed claim carries the build, test, diff, receipt, or source that makes it inspectable.
Human judgment stays central
Agents execute and keep records. People set direction, make consequential calls, and own what ships.
Portable by design
Work state uses inspectable formats and a public contract instead of belonging to one model provider.
Native, not exclusive
Ragenie will implement the contract. It will not own the contract.
The synthesis work system must remain usable without Ragenie. Other harnesses need to be able to support the same durable projects, gates, coordination, and lifecycle without depending on this codebase.
Ragenie will be the reference implementation that shows what native support can feel like. It must earn use on its own merits while the underlying contract stays open and vendor-neutral.
The product plan
Move from a settled direction to a proven harness.
Write the harness charter
Define the user and project model, runtime boundaries, tool execution, sandbox, model adapters, interfaces, and the migration boundary around the existing code.
Build the independent runtime
Make durable work the architectural center. Model access, tools, and conversations attach to the project instead of becoming its source of truth.
Make the work system native
Bring session context, policy, gates, coordination, lifecycle, and doctors into one coherent experience, with incomplete layers visible.
Prove portability
Publish the contract and conformance tests, then demonstrate that another harness can implement the same work system without privileged access to Ragenie.
The repository today
The current code and the product direction are not the same thing.
At the current public commit, the repository contains seven FastAPI services for accounts, documents, conversations, model access, file watching, and embeddings, with PostgreSQL, Redis, Qdrant, MinIO, and Docker Compose infrastructure.
The existing quick start and architecture guides describe that implementation. No released synthesis-native harness exists in the repository yet. The product-direction document is the source of truth for what Ragenie is becoming.
Run the current backend implementationRead and follow
The public record
Product directionVision, mission, strategy, plan, boundaries, and current stateGitHub repositorySource code, documentation, issues, and change historyThe Synthesis ManifestoThe values behind the work system Ragenie will implement nativelySynthesis WorkThe whole-system door and installation pathsRagbotThe separate chat-led runtime in the synthesis ecosystemSynthesis CodingThe coding practice used to build and verify the work