Acceptance of these terms.

By using the website at ai-smart-buildings.com, subscribing to the Mix Daily, applying to Beta Squad, or entering a commercial engagement with us, you agree to these terms. If you do not agree, do not use the service.

For commercial engagements (Beta cohort, Tier 1, Tier 2), the master engagement contract you sign with us governs the engagement. These terms apply where the master contract is silent. If there is any conflict between these terms and the master contract, the master contract controls.

If you are accepting these terms on behalf of an organisation, you confirm that you have authority to bind the organisation. The organisation is the contracting party; you are the authorised representative.

What BEAST OS is.

BEAST OS is a stealth-stage commercial-real-estate operating system. It comprises eight production agent squads (CRE-KE, CRE-AD, CRE-PM, CRE-CON, CRE-TS, CRE-EN, CRE-SS, CRE-SP) plus a Deal Intelligence sub-squad and a substrate gate stack (Coherence Loop, Provenance Hardening, Pessimism Gate, Stillness gates, Tool Guardrail). The operational shape is documented in the About, Detections, and PropOS Architecture pages.

The operator of the service is the legal entity behind the BEAST OS brand, currently in stealth and APAC-resident. Master engagement contracts identify the contracting entity by full legal name.

Beta Squad cohort terms.

If you have been admitted to the Beta Squad cohort, the following terms apply in addition to the master Beta engagement letter.

Charge.

The Beta cohort runs at $0 for twelve months from the cohort start date. There is no automatic conversion to commercial pricing; renewal at Tier 1 / Tier 2 is by mutual written agreement at month nine.

Service level.

Beta does not carry a contractual SLA. Best-effort uptime, best-effort response, with realistic targets documented in the engagement letter. Critical incidents (security, privacy breach) acknowledged within 24 hours; everything else within 3 operating days.

What you commit to.

• One real portfolio. Sandbox / demo data does not satisfy Beta — the OS needs to run against decisions you would have made anyway.
• Quarterly 30-minute Founder review. Four reviews over the cohort year. Receipts walked together. Honest signal back on what is missing.
• Anonymised aggregation in the public Receipts ledger. Asset names redacted, jurisdictional metadata preserved. Anonymisation parameters in §06 below.
• Data hygiene partnership. If your CDE / CMMS / BMS integrations need work, we wire them up with your team rather than abstracting around them.
• Honest signal back when something does not work. The day you notice it.

What we commit to.

• Eight production squads, full detection surface, your isolated brain.
• Daily Mix Briefing at 06:25 TPE in your jurisdiction time-zone.
• Direct line to Founder via one Slack/Telegram channel and one email thread. No ticketing. No SDR.
• Receipts published with your decisions anonymised but visible.
• Quarterly OS review with full receipts read-out, blindspot acknowledgement, and roadmap input.

Renewal or walk.

At month twelve, you renew on Tier 1 or Tier 2 commercial economics — or you walk. If you walk because the OS did not produce citation-anchored decisions you would not have made otherwise, we owe you a public retraction in the same register as the doctrine page. There is no auto-renew, no balloon clause, no claw-back.

Tier 1 / Tier 2 commercial terms.

Commercial engagements are governed by a master Service Agreement signed before service begins. The master agreement covers the full commercial relationship: scope, pricing, SLA, IP, data residency, breach notification, term, renewal, termination. These public terms summarise the structural points; the master agreement is the binding instrument.

Pricing.

Pricing tiers and bands are described on the Pricing page. Final pricing depends on portfolio shape, squad mix, and jurisdictional posture. Quoted in a scoping memo, fixed in the master agreement.

Service level.

Tier 1 default SLA: 99.5% monthly uptime on the agent fleet, 5-business-day incident response on non-critical issues, 1-hour page on critical (security / privacy) issues. Tier 2 SLA negotiated as part of the master agreement; APAC institutional defaults to 99.9% uptime.

Data residency.

Tier 1 default: shared multi-tenant deployment with per-tenant brain isolation in the customer's preferred region (Singapore, Tokyo, Sydney, Frankfurt, Virginia). Tier 2 default: single-tenant VPC in the customer's chosen jurisdiction.

SOC 2.

SOC 2 Type I attestation targeted at month-five from cohort start; Type II at month-nine. Type I attestation pack available under NDA; Type II report available on completion. Diligence packs (CycloneDX SBOM + OASIS SARIF + Agent Trust Score) are generated continuously and shipped on request under NDA.

Intellectual property.

The IP allocation is straightforward and customer-favorable. Three categories.

Your data stays your data.

Customer-provided data is owned by the customer at all times. We are a data processor, not a data owner. We do not train foundation models on customer data. We do not aggregate one customer's data into another customer's brain. Cross-tenant inference happens only via the deal-precedent librarian, on opt-in, anonymised.

Our software is our software.

The BEAST OS codebase, agent definitions, substrate gates, retrieval engine, brain architecture, and detection products are owned by the operating entity and licensed to the customer for the term of the engagement. Reverse engineering and competitor-style cloning are prohibited.

Citation chains are jointly visible.

Citation chains generated by the OS during your engagement carry references to both the public Tier-1 source (which neither party owns) and the customer-private operational source (which the customer owns). The chain itself is the audit artifact. You receive a full export of all citation chains your engagement generated, in CycloneDX-compatible JSON, on contract end.

Receipts ledger consent.

The public Receipts ledger is the keystone trust artifact for BEAST OS. By accepting these terms (and confirmed in the master engagement contract) you consent to anonymised inclusion of decisions made by the OS during your engagement.

What gets published.

• The decision verdict envelope (admitted, blocked, alert, escalated).
• The citation chain back to public Tier-1 sources (ASHRAE, IPMVP, CORENET X, etc.).
• The jurisdictional metadata (country, sometimes city when not identifying).
• The squad and agent that produced the decision.
• The operational pattern class ("EVM Theater", "RCS trigger", etc.).

What never gets published.

• Asset name or address. Ever.
• Customer organisation name. Ever.
• Specific monetary figures attached to the customer's portfolio, unless explicitly cleared by the customer in the receipt envelope at publication time.
• Names of individuals in the customer's organisation or counterparty organisations.
• Lease, contract, or commercial-terms specifics that could identify the customer or counterparty.

Append-only invariant.

Per Doctrine §II, the ledger is append-only. Once anonymised and published, an entry cannot be retracted by the customer — but it cannot be edited either, including by us. If a published entry contains an unintentional identifier (a misconfigured anonymisation parameter, a pattern that turned out to be more identifying than expected), you can request a correction. The correction lands as a new entry with a back-reference; the original stays. We treat unintentional identification as a privacy incident and trigger §08 of the Privacy page.

Withdrawal of forward-looking consent.

You can withdraw consent for future ledger inclusion at any time via the master engagement contract. Past entries — already anonymised, already published — remain on the ledger because the append-only invariant is what makes the ledger trustworthy in the first place.

Acceptable use.

The standard acceptable-use rules apply. Do not use the service to:

• Violate any law, regulation, or third-party right (including IP, privacy, fair-housing law).
• Exfiltrate or attempt to exfiltrate data belonging to other tenants of the multi-tenant infrastructure.
• Reverse-engineer the service, the substrate gates, the agent definitions, or the brain architecture.
• Attempt prompt injection, indirect injection, or other adversarial-input attacks. (We log attempts under §08 of the Privacy page and route them to security@.)
• Use the service to make decisions in regulated domains (residential leasing under Fair Housing, healthcare PHI under HIPAA, regulated financial advice) without the appropriate licensed professional in the loop. The OS surfaces detections; licensed humans make regulated decisions.
• Resell, sublicense, or commercially redistribute the service to third parties without our prior written consent.
• Use the service to generate, store, or transmit content that is unlawful, harassing, defamatory, or otherwise objectionable.

Violation of acceptable use may result in suspension or termination per §08, additional liability per §09, and / or notification of relevant authorities.

Termination.

Either party can terminate a commercial engagement on the terms documented in the master agreement. The default termination structure is:

• Termination for convenience. Either party with 90 days written notice. Pro-rated refund of any prepaid amounts beyond the termination date.
• Termination for material breach. 30-day written notice with right to cure within the notice period. If unsatisfactorily cured, termination is effective at end of notice.
• Termination for insolvency. Immediate effect on the other party's bankruptcy, insolvency, or assignment for benefit of creditors.
• Beta cohort termination. Either party at any time with reasonable notice. We default to 30 days to allow brain export and transition handoff.

On termination from any cause, you receive your data back in CycloneDX-compatible JSON for operational data, CSV for structured tables, original-format export for documents. We retain a copy only for the legally-required tax / audit retention windows. Citation chains generated during the engagement are exported as part of the data package.

Limitation of liability.

Subject to the master engagement contract, which governs the commercial relationship and may set different (typically more favourable to the customer) terms, the following apply:

• The service is provided "as is" and "as available." We make no implied warranties of merchantability or fitness for a particular purpose beyond what the master agreement explicitly states.
• Total liability is capped at the fees paid by the customer in the 12 months preceding the claim. For Beta cohort members (where fees are zero), the cap is the equivalent of one quarter's Tier 1 fees at the customer's portfolio shape.
• No liability for indirect, consequential, special, or punitive damages, including lost profits, lost data, business interruption, or reputational harm — except to the extent the master agreement or applicable law requires otherwise (notably for gross negligence, wilful misconduct, IP indemnification, or breach of confidentiality).
• Independent professional judgment is required for regulated decisions. The OS surfaces detections; licensed professionals (engineers, architects, lawyers, financial advisors) make decisions inside their scope of license. We do not accept liability for decisions made without the appropriate licensed professional in the loop.

If the cap or exclusions are unenforceable under the law of your jurisdiction, they apply to the maximum extent permitted by that law.

Governing law + disputes.

For commercial engagements, the master agreement specifies governing law and dispute-resolution forum, typically chosen to align with the customer's primary jurisdiction (Singapore for SG-resident customers, Hong Kong for HK customers, etc.). The master agreement controls.

For website usage, Mix Daily subscriptions, and other non-contracted use of the service, these terms are governed by the law of Singapore, without regard to conflict-of-laws principles. Disputes go to the courts of Singapore — except where mandatory consumer-protection law in your jurisdiction provides otherwise.

Nothing in this section limits any statutory consumer-protection rights you may have under the law of your country of residence.

Updates to these terms.

We may update these terms from time to time. The version number and last-updated date appear in the legal byline at the top of this page. Material changes are notified to active customers by email at least 30 days before effective date.

For Mix Daily subscribers and casual website users, continued use after the effective date constitutes acceptance of the updated terms. If you do not accept the updated terms, your remedy is to stop using the service.

For commercial customers, the master agreement controls the change-management process for the contracted service (typically 90 days notice, mutual agreement on material changes).

Contact.

Legal and contractual questions: beast.aicowork@gmail.com.

Privacy and data-rights questions: beast.aicowork@gmail.com.

Security disclosures: beast.aicowork@gmail.com.

Anything else: beast.aicowork@gmail.com or the contact page.

The Founder reads every legal email personally and acknowledges within three operating days. SLA tightens for security and privacy emails per the timelines in §08 of the Privacy page.