Known limitations

Current common limitations

• Installed taxonomy and jurisdiction capabilities vary. Inspect the exact filing instead of assuming uniform support.
• The synthetic pilot fixture taxonomy and its reference ZIP are non-authoritative and non-regulatory.
• Implemented validation can have disclosed unsupported rules; a clean result is not proof of regulatory completeness.
• Mapping suggestions, mechanical validation corrections, asset enrichment, portfolio readiness, and reviewer briefs are controlled aids. They do not replace source reconciliation, professional judgment, or approval.
• A reviewer brief exists only when an earlier comparable filing and relevant recorded evidence exist. None is not proof that a risk is absent.
• GLEIF, ECB, customer security-master, and other reference evidence has source-specific coverage and timing limits. Open-data enrichment does not imply licensed-provider coverage.
• Export generation is separate from portal submission, receipt, and authority acceptance.
• Authority instructions and portals can change outside the product release cycle.
• Invitation and password-reset email require configured SMTP delivery. Single sign-on and a self-service active-session dashboard are not included in the current profile. A successful password reset revokes the account's existing sessions.
• The supported runtime is the PostgreSQL web application. Browser offline persistence and synchronization are not yet implemented, and there is no supported Node SQLite or packaged desktop runtime.
• Losing an encrypted bundle passphrase makes that bundle unrecoverable without customer-managed escrow.
• A portable bundle does not replace coordinated service backups.
• Independent security, parser, accessibility, performance, and partner-acceptance evidence remains deployment- and release-specific.

Before a real filing

Confirm the approved taxonomy and jurisdiction release, validation coverage, source mappings, enrichment sources, materiality policy, supported artifact, authority process, security boundary, backup and restore rehearsal, retention agreement, support owner, and external acceptance evidence.

Report a newly discovered limitation

Stop the affected high-risk action, preserve safe diagnostic context, and follow Contact support safely. Do not compensate for a product gap by making an unsupported submission claim.