← LuciaCONTENT HISTORY

Update to Lucia

Snapshot Nov 11, 2026 · 18:09 UTC · version 0.1.230

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save Lucia and check future changes in Following.

Up to 3 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Execute Lucia's prepared legal, tax or compliance research with repeated source investigation, continuous validation and adversarial challenge. Use the shared method also used by Vera, then complete final answer review. Direct invocation enters quesito-legale-fiscale first.",
  "included_files": [],
  "name": "deep-research",
  "skill_md_contents": "---\nname: deep-research\ndescription: Execute Lucia's prepared legal, tax or compliance research with repeated source investigation, continuous validation and adversarial challenge. Use the shared method also used by Vera, then complete final answer review. Direct invocation enters quesito-legale-fiscale first.\n---\n<!-- MPARANZA_REPORTING_BEGIN -->\n## Task reporting and recovery\n\nFor every substantive user mandate, follow\n`skills/lucia/references/workflow-usage.md` from this installation's root.\nStart one primary task before preparation, using `usage/pipelines.json`; nested\nspecialists, retries and Studio Archive infrastructure reuse that task. Record\nonly the observed whole-task outcome. Discover `lucia_incident_host_link`,\nincluding deferred tools, and verify this run's Computer ID on the server.\nBuild the report input from actual phases even for chat-only drafts; missing\nclient files or a prepared input JSON do not waive reporting. Show the readable\nlocal model-data report under `skills/lucia/references/model-data-report-contract.md`, link its\nactual signed receipt, and ask once for the user's 1–5 stars after delivery.\nOnly user-authored feedback is submitted; tests remain explicitly marked.\nFollow `skills/lucia/references/incident-recovery.md` for automatic technical\nreporting, evidence requests and targeted remedies. Use the HTTPS browser recovery page in that reference if\nlocal execution is unavailable. Never ask the user to relay logs or repeat consent\nfor technical reporting. Recovery requires an observed successful retry of the\noriginal task and inputs, bound to the original report and current remedy.\nTutorials remain local-only and are excluded from task usage and ratings.\n<!-- MPARANZA_REPORTING_END -->\n\n\n# Research the prepared question\n\nWithout an accepted preparation, enter `../quesito-legale-fiscale/SKILL.md`\nfirst. Preparation-only and supplied-answer review requests retain their scope.\n\nResolve `../../modules/deep-research-validator` from this skill directory when\nit exists; otherwise resolve `../../../deep-research-validator` in repository\nsource. Read its `skills/deep-research/SKILL.md` completely and follow it.\nTreat the Lucia root as the invoking product root. Do not fork the shared method.\nUse the current host model and tools. New answers use\n`generation_route: codex_direct`; research into a supplied answer's review gaps\nretains its existing contract and document provenance.\nPreserve the lawyer's governing-law, source and professional-approval rules.\n\nAfter substantive use of this workflow, read and follow the `Plugin Improvement Feedback` section in `../lucia/SKILL.md`.\n"
}

SHA-256 of public snapshot: d619767ee061f5c4d94542164010a702afc61c955669bfdbbd5c5c41644c81e7