Use public pages, proof/status routes, labeled demos, and visible contact paths for normal review.
Acceptable use.
Use Mullusi public pages normally: read product information, review status, try public demos, and contact Mullusi through visible mailboxes. Do not disrupt the site, attack reserved routes, or treat staged product services as open access.
These rules apply to public pages now. Future runtime conduct will require separate written approval and product terms.
Choose the trust surface.
Move between website security, privacy, terms, use rules, and disclosure without losing the current public boundary.
Do not attack delivery, test reserved services, bypass controls, or treat staged surfaces as open access.
When sharing Mullusi content, preserve visible route state, proof boundary, and AwaitingEvidence context.
Public website access does not grant API, dashboard, operator, pilot, or product runtime authority.
Allowed
Read public pages, use public demos as labeled, review status or proof pages, and contact Mullusi through visible mailboxes.
Not allowed
Do not attempt unauthorized access, disrupt delivery, bypass security controls, probe reserved services, or present simulated output as live product proof.
Status accuracy
Do not remove or alter status labels when presenting Mullusi public content elsewhere. If a route is staged, describe it as staged.
Contact responsibly
Do not send harmful payloads, credential material, spam, or unrelated bulk mail through public contact routes.
Future runtime conduct
If a separate written runtime approval is published, additional restrictions may apply. Until then, runtime conduct is Not open and public website access does not authorize product runtime use.
- No unauthorized external side effects.
- No use to hide, automate, or route prohibited actions.
- No attempts to bypass review, approval, budget, record, or status checks.
- No use against systems or data you do not own or have authority to test.