How to use this function

Run a synthetic company-transformation case

Prepare and review a synthetic dossier, trace its evidence and reopen decisions when a liability changes.

The explanation and a short practice take about 5–8 minutes. Processing and your questions can extend the session.

Start this course

Codex

Open Codex on your computer with Vera installed and select @Vera in a chat.
Copy the request below, paste it into the chat and send it.
Turn on Codex voice in this chat. The assistant will guide you to open the second working chat in another window: listen and ask questions here, and watch the work and results there.

Request to send to Vera

Vera, start the prepared lesson “Run a synthetic company-transformation case” in English. Teach me to use this function with the included fictional files. Use this chat to explain the steps and answer my questions. Create or resume a second working chat to run the current workflow, and guide me to open it in another window. Help me turn on voice. Show me the actual results, then let me try the practice exercise.

The fictional lesson files are already included in the plugin. You can also take the lesson in writing. This button copies the request; the lesson starts when you send it in Codex.

Start in Claude Cowork

This function is not included in the Cowork plugin lessons. Use the Codex route above.

When to use it

Fictional Officina Selce SNC considers becoming an SRL. Two participants have separate capital, voting and profit rights. The valuation arrives after the creditor list.

Italian prototype with invented data, in desktop Codex and local Work where supported. Cowork has no teaching course. Native dossiers remain Italian. No legal or tax qualification, authenticated signature, Studio Archive integration or filing.

Files and request

Open files/input/case.json, participants.json and creditors.json. Hold valuation.json for the second stage and valuation-update.json for the final change. Null means unknown, never zero or consent; numeric strings are exact. Do not supply real clients.

Vera, guide me through the synthetic Officina Selce case. Import the brief, participants and creditors first, show what blocks capital, then acquire the valuation. Propose evidence-linked findings, show the decisions to review and export the dossier without external actions.

Run the workflow

In the working chat, Vera reads the installed procedure and creates a fresh local synthetic folder. Import the first three files as evidence. Propose separate capital, creditor-collection and tax branches. Capital depends on the unreceived valuation; collection can continue, but release and opposition remain separate open questions. Export this first version.
Import valuation.json. The model proposes calculations, rights and findings with exact document dependencies and inspectable reasons. Review capital coverage and allocation, separating capital/vote/profit and book/estimated/tax values. Do not invent legal authorities: tax questions and missing receipts stay open. Show proposal, digest and dossier before review.
Record only decisions actually expressed by the participant, with reviewer, reason and digest; label any simulation. Keep the export. Reimport valuation-update.json under the same valuation evidence ID: capital becomes stale while independent collection stays current. Document changes do not update old calculations: correct numeric inputs and findings, resubmit and request a fresh decision. Open dossier.md, case.json, manifest.json and history/.

Use the result

Versioned Markdown and JSON dossier with documents, dependencies, amounts, rights, blockers, open issues and decisions; file-hash manifest.
Earlier exports and chained history, plus the readable local model-data report. Prepared files are not these execution outputs.

Trace a finding to evidence/<hash> and its original document. Check exact amounts and separate rights. An arithmetic margin is not distributable reserves. An unknown receipt establishes neither release nor opposition outcome. Recorded review does not authenticate a reviewer and approves at most synthetic preparation.

Pause and check

Before valuation, identify the blocked branch and the branch able to collect information; find a missing receipt and tax basis.
Before deciding, inspect the evidence and each participant’s three shares. After the update, show stale and a preserved independent decision.

These pauses help you learn how to use the function. They are not a technical detail quiz.

Try it yourself

Create a second case from files/practice/, keeping the demo. Use assets 640000 and liabilities 270000; repeat import, proposal and review. Then import valuation-update.json with liabilities 305000 under the same ID. Identify stale branches, correct coverage and findings, seek fresh review and export without closing tax questions or inventing receipts.

In the demo check net assets 450000, arithmetic margin 350000 and capital amounts 60000/40000; after liabilities become 310000 check 390000/290000 following reassessment. In practice check 370000/270000 then 335000/235000. Find voting rights 1/2–1/2, profit rights 7/10–3/10, the previous decision in history, the tax blocker and export hashes. These are review criteria, not already executed results.

Repeat only with synthetic data, a fresh folder and the actually installed Vera skill. A supervised professional pilot still needs qualification and acceptance. Explanation and brief attempt target 5–8 minutes; full review and practice may take longer. Profile, progress and files remain local; the native model may read selected documents, so processing is not local-only.