Allowed
Reading public pages, using the simulated playground, reviewing proof-state records, and contacting Mullusi through visible mailboxes.
Acceptable-use boundary
Acceptable use.
Mullusi public routes exist to publish product boundaries, proof states, documentation entry points, and governed contact paths. Use must preserve those boundaries.
Blocked
Attempting unauthorized access, disrupting delivery, bypassing security controls, probing reserved operator surfaces, or misrepresenting simulated output as live proof.
Proof integrity
Do not remove, alter, or quote claims without their evidence state when presenting Mullusi public content elsewhere.
Contact integrity
Do not send harmful payloads, credential material, or unrelated bulk mail through public contact routes.
Future runtime conduct
If a separate written runtime approval is published, additional restrictions may apply. The default floor is fail-closed: hard safety, law, authority, and security uncertainty blocks execution until sensing or governance review closes the gap.
- No unauthorized external side effects.
- No use to hide, automate, or launder prohibited actions.
- No attempts to bypass approval, budget, lineage, or proof-state checks.
- No use against systems or data you do not own or have authority to test.