VeraLearn with5–8 min · EN

← Vera · Clara · Lucia

How to use this function

Assess and construct company arrangements with Vera

Move from assessment to procedures: collect answers, design a proportionate control, review the manual and check adoption and operation separately.

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

Start this course

Codex

  1. Open Codex on your computer with Vera installed and select @Vera in a chat.
  2. Copy the request below, paste it into the chat and send it.
  3. 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.

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

Open Cowork with Vera installed and a connected folder for the lesson. Copy and send this request: the lesson takes place in writing in one conversation.

Officina Arco is a wholly fictional Italian company with twelve staff improving its monthly close. February is documented; March is late during Sara’s absence. Use resumable sessions: the introduction takes about 6–8 minutes; construction and the financial lab need additional time.

Scoped assessment and experimental construction in the same engagement. STUDIO-AA-0.1 and its 0–4 scale provide neither UNI certification nor an adequacy verdict. Synthetic checks are not a real-company professional pilot.

Open company-en.md, procedure-en.md and operation-en.md for 31 March 2026; then construction-en.md and construction-facts.json for discovery. These are fictional statements and teaching inputs, not approved decisions or results. Read financial-lab-en.md for the separate lab.

Vera, assess Officina Arco’s arrangements using these files. Then help me construct a proportionate monthly-close control in the same engagement, keeping unknowns, proposals, reviews, adoption and operating evidence distinct.
  1. Run the current assessment in the working chat, open its memo and trace a finding to its source and action. Start construction in the same engagement; retain the assessment record without converting delivery into approval.
  2. Follow construction-en.md: ask one contextual question at a time; preserve original answer, speaker, date and a separate summary. Open the offline HTML form, export Markdown before closing and import receipted originals. Resume the same practice; missing attachments and unknown answers remain visible.
  3. Qualify evidence and compare base, any reasoned professional override and target. Trace evidence → risk/finding → control → action. Design one control and register, then compile and open Word/PDF/Markdown and CSV outputs. Continue review, adoption, cycles and the financial lab in separate sessions without inventing approvals.
  1. Assessment memo and record with sources, limits and actions; interview originals and resumable snapshots with version history.
  2. Operating manual in Word, PDF, Markdown and JSON, editable CSV registers and hash manifest; professional review, adoption and operating review have separate states.
  3. In the lab: reviewed and versioned Business Plan/Budget/Forecast mappings and indicator observations with frozen formula/population; no unqualified automatic financial connection.

Open the actual files, including Word and PDF. Unknown is not zero; reported is not verified. Record reviews, overrides or adoption only on the competent participant’s explicit instruction. A manual, a declared signature or one cycle cannot prove continuous effectiveness. Construction export headings currently remain Italian; explain them in the lesson language.

  1. Before judging, identify an original answer, missing attachment and dated source: what information could change the judgment?
  2. Trace evidence–finding–control–action in the manual and distinguish draft, review and adoption. After new evidence, show the decision requiring review.

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

In a distinct exercise preserve the initial output, add update-en.md and construction-update-en.md to the same engagement and reassess at 30 April. Resume the imported snapshot and sources; check actual deadlines, review every action, change the control and compare the old manual needing review with a new draft. Ask for the learner’s actual request and decision; never simulate participation.

You can repeat assessment, discovery and design; trace sources and versions; distinguish review, adoption and execution; explain why missing data, an export and a KPI do not certify arrangements.

Start from entity, purpose, scope and actual evidence. Reuse the engagement with new versions and preserve history. Real work requires professional judgment, company decisions and a supervised operating pilot. What data reaches the model: conversation, returned originals, selected evidence, manuals, decisions and financial links may be read by the selected host account’s model, without automatic anonymization. The offline form sends nothing and captures no audio; returning Markdown brings it into model context. Teaching profile and progress stay local, without server feedback or teaching receipts.