Interactive product demo
Follow a sourced EU regulatory development from official publication to affected system, assigned owner, next action and versioned evidence.
Illustrative Meridian Group example using fictional data.
Interactive product demo
See the official source, affected system, impact reasoning, owner, next action and evidence trail in one guided journey.
01 · verified official change
The fictional example uses the amended Annex III and Annex I dates recorded in the qualified release.
Available now
Explore the source, system, workflow and evidence capabilities available through Trusq today.
What Trusq reads, publishes and lets anyone check without an account.
Inspect the primary source and rule context behind a Trusq conclusion.
See sourced changes and what to check next.
Review upcoming dates and published calendar/feed formats.
Discover the public feeds, manifests and machine contracts.
Inspect what Trusq monitors and how publication and corrections are reported.
Map one system and receive a private teaser before account handoff.
Use the public entry flow that routes into the relevant assessment path.
Check a focused AI Act transparency question with source context.
Evaluate the bounded Article 50 contract through the public rate-limited endpoint.
Publish an opt-in dated result page after the snapshot flow.
Give every AI system a purpose, role, owner and declared operating context.
Maintain purpose, role and assessment context for registered systems.
Dry-run or reconcile inventory with stable external identifiers under channel-specific access.
Classify a system and produce source-linked obligations for review.
Review a positive match and record its workflow status.
Keep the record moving when a rule or a declared system fact changes.
Record a bounded before-and-after history when declared system facts change and receive a fail-closed human review trigger.
Validate and submit an explicit local or CI system manifest, inspect exact proposed differences and apply them only after tenant-admin review.
See per system which controls apply and why, who owns each one, what evidence is expected, and which controls a declared change or rule release puts back into review.
Declare, at category level only, a system's kind, accountable owner, documented intent, permitted tool and data categories and human approval points, and route any change through the same review trigger.
See which published changes positively match a registered system.
Hold the approval trail together and hand it to a reviewer.
Prepare sourced evidence while approval remains with an authorised human.
Export systems, evidence, rule updates and audit history under channel-specific entitlements.
Verify a dossier package through its package-level digest, key-id and signature result.
Connect the same objects to your own systems under a stated entitlement.
Read changes, releases, systems and dossier endpoints with a scoped credential.
Create a tenant-bound bearer credential with explicit API scopes.
Configure an endpoint and receive HMAC-signed, idempotent outbound delivery.
Inspect plan boundaries and open the workspace Plans page for current availability.
Adjacent public surfaces that support the same regulatory work.
Submit a private expert profile for manual review.
Request specialist expertise for manual Trusq review.
Have authorised staff manually review and match private requests and profiles.
Browse curated EU opportunity information outside the primary Impact route.
Use sector content outside the primary Impact route.
Accountable by design
Trusq keeps the source, system context, proposed action, reviewer and approval history together for your authorised decision-makers.
Map one real system or open the 12-system Meridian example register with its mapped obligations and source links.