modules/patent-box-review/references/implementation-status.md

# Development status and acceptance boundary

Source: Discord channel 1552206201134129152; request 1554537839595884666;
written brief 1554538351997227140; original contribution 1552213594513612880.
Recovered on 2026-09-29. The original archive has 56 entries, with 55 verified
manifest hashes. Original contributor: francesco062691.

This release makes the implemented workflow available as a controlled preview.
The full recovered specification remains the acceptance target. Technical tests
do not establish installed-runtime or professional acceptance; the remaining
conditions below stay explicit when the preview is distributed.

## Observed implementation

| Area | Present behavior | Unfinished boundary |
|---|---|---|
| Case/evidence | Actual running Studio Archive context, selected receipts, original/snapshot hash checks, distinct versions | Host file access alone does not confer professional authority |
| Controls | Software, patent, design, premial, history, supplier/group, extraordinary-operation and penalty branches; corrected core aggregation | Professional conclusions in all 32 scenarios remain unaccepted |
| Import | CSV/XLSX and host-proposed PDF rows, literal citations, complete mapped populations, reviewed FX/payroll/credits and duplicate dispositions | Representative-client extraction and fiscal meaning need UAT; no OCR |
| Case records | Located facts, rights/activity/supplier chains, targeted requests, source-specific incentive formulas, annual return reconciliation and adversarial records | Actual legal rules and annual model mappings remain unapproved |
| Sources | Bounded public HTTPS discovery, immutable originals/text versions, coverage records and 24-hour source preflight for signed review | One official annual-instructions scope was verified live; not comprehensive Patent Box research approval |
| Source comparison | Separate byte/text comparison, extraction-only change detection and conservative private impact queue | Professional impact and reopening acceptance remain unfinished |
| Monitor service | Default-off host coordinator, persisted jobs/notices, elapsed-hour cadence, complete-baseline preservation and opening/closing preflights | Native scheduling and notification delivery require configuration and live host acceptance |
| Calculation | Decimal engine, component-level outcomes and draft artifacts after exact review | Real runs require current approved sources/rules and configured firm authorization; bundled real rules remain DRAFT |
| Documents | Shared A/B document model exported as editable Word and PDF; citations, amounts, open paragraphs and audit records | Template applicability and professional acceptance remain required; exports are unsigned drafts |
| Formalities | Real local CMS/PDF/RFC3161 verification, exact byte binding, certificate chain, CRL, digest/key-use checks and reviewed-deadline comparison | Qualified status, powers meaning, LT/LTA/DocMDP, statutory conservation and qualified-provider/Windows acceptance remain open |
| Identity | Actual signature plus pinned firm-administrator signature on an exact client/engagement/period mandate; revocations rechecked | No real firm policy, mandate or reviewer is configured; firm-attested professional status is not an independent register check |
| Final review | Separate signed request binds exact results, all artifact hashes and earlier control approval; exclusive writes preserve prior versions | Synthetic technical approval is not genuine professional acceptance or independent retention against privileged deletion |
| Reopening | Fresh signed reopening links revised work to preserved approvals; completed runs continue using exact selected archive artifacts | Historical trust/time, professional acceptance and independent retention remain unverified |

## Current verification

On 2026-09-30 the component and extracted-package suite passes **300 tests**,
with **84.36%** coverage over the package and scripts. These include actual
synthetic cryptographic signatures, revoked certificates/mandates, changed
inputs/output files, cross-client scope, source freshness and an authenticated
archive-to-draft-to-final-review path, followed by signed reopening in the same run or a new run after archive completion. All certificates and identities in those
tests are synthetic. Mypy passes for 19 source files with the component configuration, which enables
errors instead of inheriting the repository-wide suppression.
Monitor tests also exercise unchanged results, partial/failed research, pending-job reuse, extraction-only changes and the preservation of approved-case hashes. These tests do not activate a native schedule or prove notification delivery.
Black/Isort and whitespace checks pass; Bandit finds no medium/high issues.
The privacy register is complete and current. An additional integration test extracts each of the three Vera archives and runs its own packaged Studio Archive and Patent Box modules in a separate process, producing synthetic Word/PDF output; task receipts record the result for the exact package generation.

All four pages of the synthetic Word-rendered dossier and all four PDF pages
were visually inspected; exact artifacts and hashes are recorded in task output
`document-acceptance-20260930/final/visual-qa.json`.

The dependency recipe and revision are synchronized across Vera, Clara and
Lucia. Exact candidate versions are recorded in each product's canonical plugin
manifest; the Patent Box component is 0.1.1. The integrated release preserves
Composizione negoziata, Trasformazione, Fusione, Adeguati assetti and the ESG
evidence foundation. Server deployment and Marketplace publication are recorded
separately in the release receipts and publication ledger. Build and acceptance
receipts identify the exact archive hashes; regenerate and verify archives after
source edits.

## Broader repository gates

The full repository test attempt stopped during collection with 26 errors from
an installed SciPy native-library loader failure and dependent imports. It did
not establish full-suite success or repository coverage. Repository-wide Black
and Isort checks also report formatting issues outside this component; no broad
reformat was performed. Targeted component formatting and unsuppressed type
checks pass. Baseline failures are reported separately from regressions. Required release CI
must pass before merging this preview.

## Remaining acceptance

All 32 professional UAT scenarios remain NOT_RUN. Genuine guided client-case
acceptance, approved current/period-specific rules and annual mappings,
qualified-provider formalities, production authority administration/retention,
monitor false-positive/false-negative review, configured scheduled monitoring and
notification delivery, professional reopening acceptance, green release CI and
installed-runtime checks remain required.

Preview deployment does not complete professional acceptance or prove an enabled
installation has updated. Do not mark the full implementation goal complete from
technical tests or publication alone.