1
Create disclosure policy
The customer defines language, placement, persistence, acknowledgement, and block-if-hidden rules for a specific AI touchpoint.
ARTICLE50_UX_POLICY_SAVED
Workflow evidence walkthrough
How SUNURA turns workflow actions into operational evidence.
This walkthrough shows the operating pattern reviewers asked for: a customer configures a control, deploys it in the real workflow, records evidence, and exports a hash-linked evidence pack.
Example sequence
AI-disclosure evidence from setup to gate proof
The dashboard is used by the SUNURA customer. The customer application calls the SUNURA API when the disclosure is rendered, acknowledged, and checked before the first AI response.
2
Generate banner artifact
SUNURA creates the persistent notice, machine-readable metadata, integrity hash, and disclosure session.
ARTICLE50_TRANSPARENCY_BANNER_GENERATED
3
Record rendering and acknowledgement
The deployed AI interface calls SUNURA when the notice is visible and when acknowledgement is collected if required.
DISCLOSURE_RENDERED / DISCLOSURE_ACKNOWLEDGED
4
Check first-interaction gate
Before the first AI output, the application checks whether the disclosure obligations for that session have been satisfied.
DISCLOSURE_GATE_PASSED
Evidence model
What a client can expect to see when reviewing SUNURA
Every major workflow is designed to produce an operational record that can be shown in the dashboard, copied as JSON, downloaded, or included in a broader evidence pack.
AI interaction disclosure
Policy, persistent banner, render evidence, acknowledgement evidence, gate decision, event hash, and previous-hash linkage.
Synthetic content identification
Watermark ID, visible label status, provenance metadata, signature, C2PA status, receipt JSON, and verification result.
Publication and editorial review
Content reference, public-interest classification, source declaration, editorial owner, exception rationale, and publication notice.
Evidence export
Customer-workspace evidence packs combine Article 50 events, hash-chain evidence, timestamps, IDs, and customer-responsibility notes.
Hash-chain evidence pattern
SUNURA records evidence events with a current event hash and the previous event hash. This creates a tamper-evident sequence that can be exported and reviewed with the evidence pack.
Event payload
Policy, session, media, publication, billing, or audit action.
SHA-256 hash
Canonical payload hash recorded with the event.
Previous hash
Links the event to the prior customer-workspace event.
Continue the review
Article 50 control matrixMap obligations to controls, exports, and customer deployment responsibilities.Sample evidence packageReview a representative package structure with events and hashes.Security and privacy trust pageReview how SUNURA describes workspace-data separation, access, retention, and incident controls.