Read/write separation
SignalFang separates read-style verification from write-style event creation. Demo access can expose read-only verification paths without granting permission to create or modify decision events.
Verification-first design
The public value of SignalFang is the ability to verify receipts and integrity state. The system is designed so proof can be checked without exposing write authority.
Payload minimization
SignalFang avoids unnecessary payload storage. The safer default is to store decision metadata, hashes, and integrity material instead of copying protected content into the proof layer.
Operational direction
The product direction includes tamper checks, replay checks, hash-linked event records, local-first evidence capture, and clean exportable receipts.
Quick answers
Can a demo read key write events?
The intended model is no. Read keys should only access read-only verification endpoints.
Does SignalFang expose the write key publicly?
No. Write access should remain protected and server-side.
Why separate verification from writing?
Because users, reviewers, or demo visitors may need to verify evidence without having authority to create evidence.
Need proof around a workflow?
SignalFang is exploring pilot workflows where signed decision receipts, payload-safe evidence, and local verification matter.