Safety by design
The gate is not optional.
Weapons and violence requests are refused by one server-side gate, before a model call, a tool action, a Blender or OOO job, a dispatch, a file share, or an outbound message. A client may check early so the overlay can say no quickly. That check is not the authority.
What Doud refuses
Doud Core screens every design request, shared-space model call, and export. It refuses requests to design or produce:
- firearms
- firearm parts, including receivers
- suppressors
- explosives
- weapons meant to harm people
- other items that are illegal or clearly harmful, including counterfeit currency and bioweapons
A refusal is logged and no geometry is created. Ordinary shop parts are allowed: phone stands, brackets, planters, and similar objects. A car exhaust silencer is not treated as a firearm suppressor.
It fails closed
The gate is not configurable.
- There is no settings flag that turns it off.
DOUD_SAFETYand any other environment variable are not read.- A client field such as
safety: falseordisableSafety: trueis ignored. - A prompt that says to ignore the policy is still screened. The instruction does not disable the check.
- Passing a replacement policy has no effect.
The gate screens the words that came in and the text that would go out, including tool results and model replies. If the classifier throws, the decision is a refusal. Nothing is built, sent, or stored as a successful result.
The audit log
A refusal is written to the audit log as safety.refused, with the category and the channel. The record does not include instructions for making the refused object.
Approval
Doud does not edit geometry, share a file, pay a provider, or send an outbound message without an explicit approval from someone allowed to give it. Viewers cannot run changes. Editors cannot approve an external share. A provider cannot approve a revision of someone else’s project.
Untrusted input
Screenshots, documents, window titles, and messages from outside the person’s own request are data. They are screened, and they cannot change the request or turn the safety rules off. Doud does not start the camera or a screen capture on its own. “Hey Doud” listens only after the person turns that control on. The keyboard shortcut summons Doud without a microphone.
What a file is, and is not
A named Seal is an intentional milestone. An automatic checkpoint is not a Seal. An STL that fails the manifold and watertight checks is not exported as a production file. A production package is a digital file plus estimates. It is not a finished physical part, a certification, or a price. Export controls, intellectual property, and machine safety still apply. Doud does not grant a license to reproduce someone else’s work, and it does not claim a print is safe to run.
This build records usage notes only. It does not charge a card or mark anything paid.