Clara's intelligence
Reads the materials, keeps sources organized, surfaces gaps, prepares questions and turns scattered inputs into working drafts.
Clara
Use Clara when the useful information is split across files, notes, calls and half-formed views. She keeps the trail clear, shows what still needs review, and helps prepare drafts that can be checked before anyone shares them.
Clara prepares the intelligence layer. The consultant keeps the professional judgement and decides what is ready to use.
Reads the materials, keeps sources organized, surfaces gaps, prepares questions and turns scattered inputs into working drafts.
The consultant explains the situation, corrects the reading, chooses what matters and decides what can be relied on.
The local case folder keeps materials, voice notes, judgement calls, open questions and drafts together across sessions.
Use ordinary Codex requests. Clara handles the case folder and reports what changed.
Voice is a way to capture a debrief without turning the conversation into a form. The imported file returns to the same local case.
| Step | What happens | Result |
|---|---|---|
| Launch from Codex | The user asks Codex to start voice capture for the active case. | The plugin opens the hosted voice screen with a short-lived launch token. |
| Authorized voice session | The hosted server creates the realtime voice session for authorized users. | The user does not manage a local API key for voice. |
| Debrief and sparse follow-ups | The voice model listens and asks only sparse follow-ups when useful. | The session captures reasoning, caveats and open questions without treating the recording as final advice. |
| Local JSON file | The browser downloads a JSON file at the end of the session. | The server is not the case archive; the JSON file is imported locally. |
| Local import and review | Codex imports the downloaded JSON file into the Clara workspace. | Transcript is source material. Extracted entries stay separate until they are reviewed. |
The case folder is the source of truth. A later Codex session can reopen the same folder and continue from the existing files instead of relying on chat history.
| File or folder | Content |
|---|---|
| case_manifest.json | Client, project, objective, audience, language and case status. |
| case_brief.md | Derived working brief for resuming the case; the JSON files remain the source of truth. |
| material_registry.json | Indexed source materials with path, type, summary and status. |
| judgement_log.json | Facts, working judgement, Codex inferences and decision implications with inclusion status. |
| open_questions.json | Targeted unresolved questions and why they matter. |
| voice_sessions/ | Imported voice transcripts and extracted candidates. |
| exchange_exports/ | ZIP updates created for another local workspace. |
| exchange_imports/ | Local files received from imported update packages. |
| exchange_log.json | Record of imported case-update packages. |
Clara is designed for one consultant owning the live case. If delivery support is useful, the consultant asks in normal language and Clara prepares a clean local package. The helper receives context; the local case remains the source of truth.
Delivery support
Working briefs, source registers, open-question lists and reviewed drafts are meant to be read before they are shared.
Output package
Unreviewed judgement is not silently promoted into final drafts. Clara keeps the boundary visible.
One ZIP installs all Mparanza plugins except Pro reporting engines. Clara is included; Reporting remains the Pro-only link.
"Use Clara on this case folder."
Download ZIP