Independence is described accurately, not claimed where it does not exist.

The relationship between Veyra and the engaging client appears in the executive summary of every deliverable.

Every executive summary and technical report carries a first-class Independence Disclosure section. The section is not a footnote, an appendix, or an “About the assessor” sidebar — it is a numbered section in the document body. The disclosure is current as of the report date and re-evaluated on a rolling 12-month basis.

Where no disclosable relationship exists, the section says so explicitly with the dated language: “As of the report date, Veyra Security is independent of the engaging client. No commercial, equity, advisory, or family relationship has been identified within the 12 months preceding the engagement.”

Four categories trigger disclosure.

The relationship audit checks four categories before each engagement and again before report finalization. Any positive answer triggers the disclosure section and, where the relationship is material, the independent reviewer process below.

When a relationship exists, a named external reviewer signs off on the engagement record.

When the relationship audit returns a positive answer in the categories above, an independent technical reviewer — a credentialed assessor with no relationship to the engaging client and no equity in ARK Solutions LLC — reviews the engagement record and the report before delivery.

The reviewer is named in the report by full name, role, and relevant credential. The reviewer's role is described accurately: review of the engagement record, review of finding evidence, and concurrence on severity scoring. The reviewer does not re-perform the engagement.

The disclosure is dated and re-evaluated.

The disclosure section in every report bears the report date. Veyra refreshes the underlying relationship audit on a rolling 12-month basis and at the start of every new engagement, whichever is sooner. A material change between report draft and report finalize triggers a re-issued disclosure and a re-signed reviewer concurrence.

The engagement engine will not finalize a report without a current disclosure snapshot.

The Veyra Engagement Engine carries a disclosure-snapshot check as a hard gate on the report finalize action. The check verifies the disclosure section is present, the date matches the report date, and the reviewer name and credentials are populated when the relationship audit requires them. Reports without a passing snapshot cannot be moved from DRAFT to FINAL.

The same banner re-renders on the engagement portal at intake (Stage 1), at SOW signing, and on the report cover. Each surfacing has its own audit row.

Independence is not claimed where it does not exist.

Veyra will not describe an engagement as “independent third-party” when an equity, advisory, or material commercial relationship exists. Veyra will not omit a disclosure to make a deliverable easier for a reviewer to accept. Veyra will not describe the disclosure section as optional, additive, or “available on request.”

Disclosed relationships do not affect the validity of findings, evidence, severity scoring, or remediation status documented in the report — and the disclosure says exactly that.