Defensive publications preserve technical disclosures in a dated, inspectable and cryptographically bound public record.
Each DotShield record is designed to distinguish what is claimed, what was publicly disclosed, and what can be independently verified from the published artefacts.
A credible defensive publication should make clear what is asserted, what entered the public record, and what can later be independently verified.
Development history and technical provenance may form part of the disclosure, but earlier activity should remain identifiable as a claim unless it is supported by separate evidence.
The publication preserves the technical subject matter placed into the public record at the stated publication date, in a form that can be inspected and retained.
Cryptographic hashes, downloadable artefacts and independent timestamp evidence allow the integrity and existence of the published record to be examined separately.
Multi-modal biometric verification using EEG↔speech correlation to defeat synthetic voice and replay attacks.
The following summary preserves the technical scope of the original v1.0 disclosure while the publication artefacts remain the authoritative record.
This defensive publication discloses a multi-modal biometric authentication system that resists AI voice cloning, deepfake audio, and replay attacks by verifying a neural–acoustic correlation between EEG activity and speech production.
Conventional voice biometrics rely primarily on acoustic characteristics and can be defeated by modern speech synthesis and conversion. The disclosed method introduces a physiological verification layer that confirms speaker presence and cognitive intent by assessing timing and statistical alignment between EEG features and phoneme-level speech events.
Captures EEG activity and speech audio during enrolment and authentication.
Aligns EEG features to speech events using a synchronisation layer capable of handling timing offset and drift.
Computes a neural–acoustic correlation score using techniques such as cross-correlation, coherence, mutual information or sequence alignment.
Applies policy gating using voice-match and correlation thresholds, then records the resulting audit or evidence outcome.
This webpage summary is provided for readability. It does not expand, amend or replace the technical disclosure contained in the published v1.0 PDF and Markdown artefacts.
The record distinguishes historical assertions from the event that can be independently examined through the published artefacts.
Australia/Melbourne · AEDT · UTC+11
Australia/Melbourne · AEDT · UTC+11
6 February 2026 · 11:55 AM UTC
Earlier dates remain part of the disclosed development history. The public disclosure is supported by the publication artefacts, cryptographic hashes and timestamp evidence presented below.
The publication and its associated integrity evidence are available directly from the DotShield resource repository. Each artefact can be retained and independently examined.
The original publication was made under the former NOMATEQ web presence. Independent archive captures preserve that historical record and its associated publication artefacts.
References to NOMATEQ in archived pages and original artefacts form part of the publication provenance. Migration to DotShield does not rewrite or replace those historical identifiers.
Preserved record of the independent archive references associated with the original publication.
Independent capture of the former NOMATEQ Defensive Publications page following the v1.0 disclosure.
Historical screenshot evidence showing the publication page as independently captured.
Independent archive capture of the original v1.0 PDF publication.
Independent capture of the Markdown form of the technical disclosure.
Independent capture of the SHA-256 integrity values associated with the original publication artefacts.
The original publication page recorded an intention to develop a later v1.1 with additional technical detail and figures. That historical development note does not alter the preserved v1.0 record.
This record is a defensive publication intended to place the disclosed subject matter into the public record as potential prior art. It is not a patent application, patent grant, licence, or freedom-to-operate opinion.
The scope of this publication is limited to the subject matter actually disclosed in its published artefacts. Other GABEY Consulting and DotShield technologies may be protected separately through patent applications, copyright, confidential know-how, trademarks, contractual controls, or other intellectual-property rights.
Making technical information publicly accessible does not itself grant a licence to software, implementations, source code, proprietary methodologies, trademarks, or separately protected inventions.
Nothing on this page should be interpreted as expanding the scope of the original defensive publication, abandoning rights in separately protected technology, or granting permission beyond rights that otherwise exist under applicable law or an express written licence.
Earlier NOMATEQ disclosures also placed technical concepts into the public record. Where a separate publication package, cryptographic manifest or timestamp artefact has not been identified, DotShield distinguishes those historical web disclosures from later cryptographically bound defensive publications.
An earlier defensive disclosure covering a family of related trust, delivery and post-gateway resilience concepts.
Trust-state model associated with the movement and handling of information beyond conventional gateway controls.
Educational framework describing the distinction between successful network delivery and delivery into a trusted state.
Three-mode interactive journey used to demonstrate how the same information flow can produce materially different security outcomes.
Educational sequence addressing the security problem that remains after information has passed an authorised gateway.
Original terminology and historical provenance are retained where they form part of the disclosure record. DotShield does not retrospectively assign publication packages, hashes, timestamps or identifiers that have not been independently recovered.
DotShield® Defensive Publications preserve technical disclosures as inspectable public records. These questions explain what that means — and what it does not mean.
A patent and a defensive publication serve fundamentally different purposes.
A patent, where granted and enforceable, may provide exclusive rights for a limited period. A defensive publication instead places technical subject matter into the public record with the intention that it may constitute prior art relevant to later patent claims.
| Aspect | Patent | Defensive publication |
|---|---|---|
| Primary goal | Obtain exclusive rights, subject to jurisdiction, examination and grant. | Place technical subject matter into the public record so it may be available as prior art. |
| Timing | Filing, examination and grant can take considerable time. | Public disclosure occurs when the material is published. |
| Outcome | Potential enforceable rights where a valid patent is granted. | Publicly accessible technical disclosure and evidence of the published record. |
| Implementation | May require permission from the relevant rights holder. | Publication makes the disclosed information public, but does not itself grant an IP licence. |
A defensive publication is not a patent application, patent grant, legal opinion or licence. Whether a particular implementation may be used commercially depends on the wider intellectual-property, contractual and regulatory circumstances.
DotShield uses defensive publication where placing a technical concept into an identifiable public record is preferable to leaving that work undocumented or privately asserted.
Preserve the disclosed subject matter in a form that can subsequently be examined and referenced.
Record when particular technical material entered the public domain and provide evidence associated with that publication.
Publish cryptographic hashes, timestamp evidence and associated artefacts so the record is not dependent on a webpage assertion alone.
Some migrated publications may retain GABEY or NOMATEQ names, identifiers or references inside the original publication artefacts. Those historical identifiers form part of the record and are not silently rewritten during migration to DotShield.
A defensive publication makes the disclosed technical information publicly accessible. It does not, by itself, grant a patent licence, copyright licence, trademark permission or freedom to operate.
You may be able to develop an implementation based on publicly disclosed concepts, but the rights and obligations associated with a particular implementation must be considered separately.
Defensive publications are provided as technical disclosures. Any implementation should be independently validated against its intended environment, threat model and applicable obligations.
Each publication may include SHA-256 values that allow you to calculate a digest locally and compare it with the published record.
Retrieve the publication artefact from the DotShield resource repository.
Compute the SHA-256 digest locally.
Compare your result with the published hash manifest.
Where supplied, independently examine the OpenTimestamps proof.
Get-FileHash -Algorithm SHA256 .\filename.pdf
shasum -a 256 filename.pdf
sha256sum -c GABEY-DP-2026-02-06-MULTIMODAL-VOICE-VERIFICATION-v1.0.HASHES.txt
The calculated digest matches the published hash for that artefact.
Do not assume the files are equivalent. Re-download the artefact from the official DotShield resource page and check again.
Timestamp evidence associated with a published digest or hash manifest.
Cryptographic digests used to identify the exact publication artefacts.
Independent web archive captures may provide additional evidence that a publication or page existed at a particular time.
Agreement between artefacts, hashes, timestamps and independent archival records strengthens provenance assessment.
Include the Document ID and the relevant artefact — PDF, Markdown, HASHES or OpenTimestamps proof — when referring to a particular defensive publication.