01Acceptable use

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 reserved product services as open access.

Read Try demos Contact Respect reserved services Report issues
Public pagesAllowed
DemosUse as labeled
Reserved servicesPlanned
Product accessNot yet
ReportsMailbox route

These rules apply to the public pages. Using the product will need separate written approval and product terms.

02Boundary map

Allowed, blocked, and what access does not grant

Allowed Read, inspect, demo, and contact.

Use public pages, proof/status routes, labeled demos, and visible contact paths for normal review.

Blocked No probing, disruption, or bypass.

Do not attack delivery, test reserved services, bypass controls, or treat reserved surfaces as open access.

Integrity Keep status labels with public content.

When sharing Mullusi content, keep its Available, Not yet or Planned labels.

Product Separate written approval required.

Visiting the website does not grant API, dashboard, operator, pilot or product access.

03Use boundaries

Use boundaries

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 demo output as product evidence.

Status accuracy

Do not remove or alter status labels when presenting Mullusi public content elsewhere. If a route is marked Not yet or Planned, keep that label.

Contact responsibly

Do not send harmful payloads, credential material, spam, or unrelated bulk mail through public contact routes.

04Future product use

Future product use

If written approval to use the product is published, more rules may apply. Until then, visiting the website does not authorize product 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.

Violation reports: Send public-surface abuse or conduct reports to support@mullusi.com.

Route record (for auditors)

Acceptable-use route state: Published. Runtime conduct terms: AwaitingEvidence until separate written approval.