INTERACTIVE SAMPLE / AI GOVERNANCE
Follow a possible finding from source to human review.
Explore three synthetic scenarios: a document checked against selected EU AI Act requirements, an AI-use signal that may belong in an inventory, and a changed file queued for scheduled review. Nothing here connects to your accounts or analyzes a real document.
A GUIDED WALKTHROUGH
Choose what you want to inspect.
Every source, finding and status below is fictional. Reveal each example to see the question a reviewer would take forward.
SELECTED SCENARIO
Where does a possible gap come from?
A fictional AI-use policy is compared with a requirement Fencia currently covers.
“The product owner reviews model risks when material issues arise.”
The excerpt is invented for this walkthrough. A real reviewer would inspect the whole document.
Reveal the sample finding to see what the source raises for a person to check.
This walkthrough uses written examples and a simulated reveal. It does not run a scan, connect an integration or return a legal conclusion.
WHAT THE EXAMPLES MEAN
A useful question, not a compliance verdict.
Fencia helps organize evidence and possible gaps. A person checks applicability, the original source and the next action.
Selected coverage
Document analysis addresses supported EU AI Act requirements and part of the GDPR. It does not scan documents for ISO/IEC 42001 certification.
Explore document analysisA candidate, not proof
Slack can contribute AI-use mentions. GitHub contributes supported dependency-manifest signals; it is not a document or patrol source.
See integration scopeChanges need context
Eligible connected document sources can be checked on a schedule. A new or changed file can raise a question for review; it does not confirm non-compliance.
See the workflowSTART WITH YOUR OWN EVIDENCE
Move from an example to a real review.
Begin with a supported document or discuss the right starting point for your team. Review any result with the person responsible for the decision.