Calamophyton Developer Materials Notice

Site and public-materials notice

This site contains materials for enterprise and institutional customers and their technical, security, legal, and procurement teams to evaluate products and integration opportunities. Public materials are not an offer or solicitation to consumers, an offer to enter into a contract, or a guarantee of any particular outcome.

The drafting directions for insurance evidence (Section 16), change protection during a paid term (Section 13), a narrow Feedback license (Section 11), and enumerated post-termination survival (Section 14) received internal business approval on 2 September 2026. They remain separate counsel-review rider drafts and are not an external representation or transaction term unless exact final bilingual bytes are expressly incorporated into a mutually executed Order.

Documentation, reference examples and response readers, specifications, roadmaps, and status indicators are based on information available when prepared and may be changed, corrected, or withdrawn. Except as expressly stated in a separate written agreement, Calamophyton does not warrant the accuracy, completeness, currency, fitness for a particular purpose, or continued availability of public materials.

This site does not provide legal, regulatory, investment, tax, security-certification, or other professional advice, or advice concerning any particular operational outcome. Before any material decision or integration, Customer personnel and independent advisers must review the source materials, applicable law, internal authority, security requirements, and signed agreements themselves.

• Synthetic or explanatory scenarios and fixed test data do not represent an actual customer, third party, operational incident, or grant of authority.
• Links to external sites or third-party materials are provided for convenience and do not mean that Calamophyton controls or warrants their content, security, availability, or terms of use.
• Public materials are protected by copyright and other intellectual-property rights. They may not be reproduced, modified, distributed, or made public except as permitted by applicable law or separate written authorization.

1. Executed-Agreement boundary

“Executed Agreement” means only the mutually executed Order and the exact Master Terms and schedules incorporated by title, version, and SHA-256. This public Notice is not an agreement, click term, license grant, or incorporated document and does not amend or supplement an Executed Agreement. If this Notice conflicts with an Executed Agreement, the Executed Agreement controls.

Binding terms, if any, must be identified in a mutually executed agreement. A separately recorded acceptance event may evidence execution or supplemental assent but does not replace the mutually executed Order required for a paid Private Preview. This public review draft does not itself create an offer, assent event, credential, or access approval.

This predeployment draft concerns Calamophyton developer materials that 칼라모피톤 인더스트리즈 유한책임회사, using the company-designated English contracting name Calamophyton Industries LLC (the “Company” or “Calamophyton”), may actually provide or approve for access by a customer or developer. Comparison of both contracting names and the address against an authoritative corporate record remains an external evidence gate before execution. The applicable product—HARBINGER, PÓLYA, or RAIFFA—must be identified in the relevant order form, product schedule, access approval, or separate written agreement.

A paid Private Preview agreement becomes binding only when both parties execute an Order incorporating the exact identified terms, by signature or through a designated electronic-execution flow that binds both parties and the exact bytes and SHA-256 digests. Customer click acceptance of this public draft alone is not an executed Order. Browsing, downloading, or linking to public documentation does not constitute assent.

An electronic-assent flow must identify every document in the contract bundle, its version and SHA-256 digest, the applicable Order and Product Schedule, the signer and represented legal entity, the important terms shown separately, and the acceptance time. It cannot substitute for a transaction-specific signed Order where the customer scope, fees, taxes, term, or security obligations remain incomplete.

Before using any non-public Developer Materials, the authorized representative must complete the applicable assent process. Contract assent does not itself issue a credential or approve access. Any actual access requires a separate recorded approval and issuance event.

Viewing public documentation alone does not grant any right to access an API, Sandbox, SDK, CLI, or any Product operating environment, organizational authority, or execution authority.

2. Key terms

• “Product” means only HARBINGER, PÓLYA, or RAIFFA as expressly selected in an Executed Agreement.
• “Developer Materials” means any API, Sandbox, SDK, CLI, sample code, specification, documentation, credential, or related tool provided by Calamophyton.
• “Sandbox” means an evaluation or development environment that is logically isolated for each customer organization; it is not a production environment unless separately approved in writing.
• “Customer Data” means data and content that Customer or an authorized Customer user submits to the service or instructs the service to process.
• “Output” means objects, relationships, changes, evidence, gaps, review conditions, eligibility states, blocking reasons, verification records, and related results that a Product displays or generates from authorized inputs and observations.
• “Customer Application” means software or an integration that Customer develops and operates using the Developer Materials.
• “Usage Data” means technical information required to operate the service—such as request time, version, latency, errors, security events, and feature usage—but not the content itself.

3. Current availability and access status

• Public materials: HARBINGER, PÓLYA, and RAIFFA documentation, Markdown source, the OpenAPI specification, and fixed official-data reference examples and response readers are available for review. A separate public demo endpoint serves precomputed responses to GET requests over enumerated fixed synthetic conditions only.
• HARBINGER API: Calamophyton may separately authorize access only for approved customers and approved purposes after Calamophyton has prepared the applicable environment.
• PÓLYA: The public demo endpoint returns review paths precomputed from the HARBINGER example result. It is not a customer decision workbench, recommendation, approval, or operational authority.
• RAIFFA: The public demo endpoint returns precomputed authority requirement checks and blocking reasons for a fixed synthetic request. It is not a real login, organizational authority, execution right, or action in an external system.
• Isolated Sandbox: If made available, approved users, scope, and data-display policies for each customer organization will be stated in a separate agreement.
• SDK and CLI: These may be used only when Calamophyton separately provides the applicable version and purpose or approves them in writing.
• Production environment: Sandbox access does not grant production-environment access, production-data processing, or any service-level commitment.
• Features shown in documentation: Only features actually enabled for Customer are included in the contractual scope. A description or example does not create a future delivery obligation.

4. No license granted by this Notice

This Notice grants no license, right to use non-public Developer Materials, Product access, or authority. Any limited right exists only if and to the extent an Executed Agreement identifies the Product, Developer Materials, approved entity, users, environment, purpose, region, data scope, version, and term.

Calamophyton and the applicable rights holders reserve all rights not expressly granted in an Executed Agreement. A public description, example, response reader, specification, inquiry response, demonstration, checkbox, or click is not a grant.

5. Restrictions for non-public access

This Section describes restrictions that an Executed Agreement or other separately accepted binding access terms must state before Calamophyton issues non-public Developer Materials. Display of this public Notice does not impose those contractual restrictions on a visitor. Public materials remain subject to applicable law, third-party rights, technical access controls, and any terms separately accepted by that visitor.

Under those binding non-public access terms, the restricted conduct includes directly or indirectly attempting, directing, inducing, assisting, permitting, or causing it through a third party, affiliate, agent, contractor, or automated tool. The list is not limited by the name or form of a method and includes circumvention that achieves substantially the same purpose or effect. It does not prohibit conduct that applicable law does not permit the parties to restrict.

• Selling, leasing, redistributing, publishing, pledging, or sublicensing the Developer Materials, or using them for an unapproved third party.
• Using non-public Developer Materials to reverse engineer, decompile, disassemble, or extract models, weights, prompts, architecture, ontologies, or control logic, except for interoperability activity that applicable law does not permit the parties to restrict or a pre-approved internal security assessment.
• Using non-public Developer Materials, Output, or Confidential Information to train, evaluate, or develop a substitute API, SDK, model, or service, or publishing an unapproved external benchmark. This does not prohibit independent development without Calamophyton Confidential Information or lawful use of public information.
• Removing, altering, or circumventing credentials, organizational boundaries, usage limits, audit records, source labels, status indicators, or access controls.
• Conducting vulnerability scanning, penetration testing, load testing, or automated requests that may affect service stability without Calamophyton’s prior written approval.
• Introducing malicious code; engaging in unauthorized collection, unauthorized surveillance, privacy infringement, or system interference; or infringing a third party’s rights.
• Using Output as a basis or material input for a credit, insurance, employment, health-care, safety, law-enforcement, or other automated decision, approval, command, or external execution that materially affects rights, safety, or economic opportunity. This Private Preview prohibition is not lifted by a general written approval; any later limited exception requires an express signed scope, a separate access-issuance event, a verified technical gate, a prior impact assessment, notice of AI use, legally sufficient human oversight and final approval, explanation and challenge procedures, and appropriate records.

6. Customer Applications and user responsibilities

Customer is responsible for its Customer Applications, user administration, configurations, inputs, use of Output, and the resulting consequences. Customer must comply with applicable law, third-party agreements, internal authority structures, and the documentation provided by Calamophyton.

• Obtain lawful authority to collect, use, and provide Customer Data and to connect each integration target, together with all required consents and notices.
• Manage approved users and purposes, and apply least privilege, multi-factor authentication, and Customer’s organizational security policies.
• Be responsible for the quality and lawfulness of Customer Applications, end-user notices, support, and incident response.
• Independently review the sources, observation time, uncertainty, gaps, counter-signals, and status included in Output.
• Maintain backups, record retention, human approval, and additional controls required by law or Customer policy.

7. Credentials and security

Credentials may be used only for the customer, user, application, and environment for which they were issued. Customer must not store credentials in a public repository, client-side code, shared document, or unauthorized device, or share them with a third party.

Customer must notify Calamophyton immediately upon learning of lost credentials, unauthorized access, a suspected compromise, or use beyond the approved scope, and must cooperate in reasonable investigation, containment, and recovery measures. Use made with Customer’s credentials will be treated as Customer’s use to the extent it was within Customer’s reasonable control.

Non-public Developer Materials, credentials, Sandbox content, and information that should reasonably be understood to be confidential must be protected under the applicable nondisclosure agreement or customer agreement. System records are rebuttable evidence considered with other evidence only to the extent their authenticity, integrity, and generation path are established. They are not conclusive, do not increase Customer’s statutory burden of proof, and yield to the agreed document order of precedence.

Unless an executed agreement states otherwise, mutual confidentiality survives for five years after termination, while source code, model structure, security design, and trade secrets remain protected while they qualify as trade secrets. Public information, lawful prior possession, independent development without use of Confidential Information, and lawful third-party receipt are excluded. External use of either party’s name, logo, result, screen, case study, or test result requires case-specific mutual written approval.

8. Customer Data and service data

Customer and its licensors retain their rights in Customer Data. This Notice authorizes no collection, receipt, processing, retention, de-identification, aggregation, or use of Customer Data, Output, or Usage Data. Any processing authority must be stated for documented purposes in an Executed Agreement and, where applicable, a signed data processing addendum.

Customer Data or Output may not be used for model training or product improvement unless a mutually executed Order and, where personal data applies, a signed data processing addendum expressly identify the exact data, purpose, model and customer scope, safeguards, retention, and deletion. An email, support ticket, checkbox, general consent, or this Notice is insufficient.

Actual processing of personal data requires a signed data processing addendum and a verified Security Schedule. The current drafting baseline starts initial notice upon awareness of facts reasonably indicating a Customer Data Security Incident, without waiting for final confirmation; only an Executed Agreement creates that obligation.

This Notice grants no right to use aggregated, de-identified, or technical Usage Data. Any such right must identify its data fields, purpose, safeguards, reidentification prohibition, retention, and deletion in an Executed Agreement.

9. Source materials and third-party rights

Materials accessed under an Executed Agreement through an API or Sandbox may be subject to intellectual-property rights, privacy rights, confidentiality obligations, and use restrictions belonging to Customer, a source provider, or another third party. Neither this Notice nor an Executed Agreement gives Customer ownership of those materials or a right to use them beyond their original permitted scope unless expressly stated.

Customer must query, transmit, or combine user or third-party materials only where it has express authority and all required consents. Unless Calamophyton separately warrants otherwise in writing, Calamophyton does not warrant the authenticity, completeness, currency, or continued availability of third-party materials.

10. Nature of Output and independent review

Output is review material that structures authorized materials and the inputs available when generated. A HARBINGER change candidate is not a determination of fact or a prediction; PÓLYA options and conditions are not a recommendation or final decision; and a RAIFFA eligibility check does not grant Customer organizational authority or issue an execution command.

Output may change when new materials appear, corrections or withdrawals occur, time passes, authority changes, or conflicting evidence emerges. Before any material decision or action, Customer must independently verify source materials, time, lineage, counter-signals, and gaps, and must have an authorized person make the final decision.

Customer must not remove source, time, uncertainty, or state indicators—including UNKNOWN or BLOCKED—in a way that presents Output as a confirmed fact or as approval by Calamophyton.

11. Intellectual property and use of results

Calamophyton and its licensors retain all rights in HARBINGER, PÓLYA, RAIFFA, the Developer Materials, models, ontologies, algorithms, interfaces, templates, documentation, generalized improvements, and all related intellectual-property rights. Customer retains its rights in Customer Data and in Customer Applications that Customer independently creates.

Only an Executed Agreement may grant Customer a right to use, reproduce, or analyze Output generated for Customer. Any such right remains subject to source-material restrictions and does not transfer any right in a Product’s underlying technology, third-party materials, or another customer’s information.

This draft grants no license to use Customer feedback beyond rights established by applicable law or a separately approved and mutually executed rider. Any Feedback term requires a separate internal APPROVED decision, counsel-cleared final bilingual clause bytes, exact decision and clause digests, conspicuous presentation, and incorporation into the executed Order. It may not be inferred from product use, support conversations, suggestions, silence, or the appearance of a proposal on this site.

12. Third-party services, artificial-intelligence tools, and open source

Third-party services, data, applications, artificial intelligence, or large language models that Customer selects or enables are subject to the applicable provider’s separate terms. Calamophyton is not responsible for the conduct, data, or continued availability of a third-party service selected by Customer.

An open-source component included in the Developer Materials is governed, for that component, by its applicable open-source license. A subprocessor selected directly by Calamophyton to provide the service will be managed under the applicable data processing addendum and security obligations.

A link from this site to an external website or third-party material is a reference provided for convenience. Except to the extent Calamophyton directly provides or warrants the relevant material in writing, Calamophyton is not responsible for the accuracy, lawfulness, security, availability, or changes of external content, and Customer must review the third party’s terms separately.

13. Private Preview, changes, and discontinuation

Private Preview is a pre-release stage for evaluation and limited integration. Features, data structures, performance, versions, URLs, and compatibility may change, and no general-availability commitment concerning availability, support, or compatibility applies unless stated in a separate SLA or order form.

This public Notice creates no paid-term feature-preservation, change-notice, migration, compatibility, workaround, substitution, termination, or refund commitment beyond a mutually executed Order and mandatory law. The internally approved drafting direction requires counsel-cleared final bilingual rider bytes, exact Order-specific decision and clause digests, conspicuous presentation, and express incorporation into the executed Order. It may not be inferred from a roadmap, documentation, prior behavior, internal approval, or the appearance of a rider draft on this site.

A party delayed by an event beyond its reasonable control must promptly describe the cause, expected impact, mitigation, and recovery plan and must reduce the impact. Accrued payment, confidentiality, Customer Data protection, Security Incident notice, and mitigation obligations are not excused. If the effect continues for more than 30 days, the other party may terminate the affected scope and settle unused prepaid fees for that scope.

14. Suspension and termination

Calamophyton may immediately suspend the minimum necessary scope to address unlawful conduct, unauthorized access, a credible security risk, or harm to a third party. The ordinary cure period is five business days for non-payment and ten business days for another curable material breach. An incurable breach, insolvency, business cessation, or legal prohibition may result in immediate termination. Where possible, Calamophyton will first apply a narrower measure and will restore access without undue delay after the risk is resolved.

Customer convenience termination and settlement for a paid Order are stated in the signed Order. The drafting baseline is 14 days’ written notice, settlement of completed work, performed mobilization work, and Customer-approved non-cancellable charges, and refund of the remaining unperformed prepaid amount. This public draft creates no ordinary-business discontinuation notice, replacement, termination, or refund right; any such right must appear in the exact mutually executed Order or a separately approved rider.

This public Notice creates no general post-termination survival schedule beyond a duration expressly fixed elsewhere in executed terms—such as a confidentiality period—or mandatory law. The internally approved enumerated-survival drafting direction requires counsel-cleared final bilingual rider bytes, exact Order-specific decision and clause digests, conspicuous presentation, and express incorporation into the executed Order. Survival may not be inferred from a clause’s subject, a claim arising before termination, internal approval, or the appearance of a rider draft on this site.

15. Limited warranty and disclaimers

Calamophyton will use professional and reasonable care to make paid Deliverables materially conform to the Order. Public materials and out-of-scope functionality are provided “as is” and “as available” to the extent permitted by law. Calamophyton does not warrant uninterrupted or error-free operation, detection of every change, data accuracy, completeness or currency, prediction, investment, legal or regulatory judgment, future compatibility, ROI, savings, or business outcome. The contractual remedy is re-performance or correction, a reasonable workaround or substitute, and then termination of the unrestored affected scope with a refund of unused prepaid fees.

This section does not exclude liability arising from Calamophyton’s willful misconduct or gross negligence, or rights and liabilities that applicable law does not permit the parties to exclude.

16. Limitation of liability

A claimant must prove the specific contractual duty, breach, direct causation, and actual documented loss. Conduct by Customer or a third party, causes in external systems or sources, and failure reasonably to mitigate loss will be reflected in liability and damages.

To the extent permitted by law, neither party is liable for indirect, special, incidental, consequential, or punitive damages; lost profits or expected savings; or loss of revenue, opportunity, goodwill, or data value. Reasonable direct restoration, reprocessing, and required-notification costs and a covered third-party claim are not excluded merely because they are characterized as consequential and remain subject to the applicable cap.

The single aggregate cap for general liability under a paid Order is one times the total fees paid or payable under the affected Order, excluding VAT and pre-approved third-party pass-through charges. One higher cap of two times that base is the maximum aggregate cap for covered claims within the affected Order, including (a) a Calamophyton-controlled confidentiality breach, Customer Data security breach, or third-party intellectual-property infringement by Calamophyton’s unmodified core software and (b) Customer’s covered Section 17 obligations to the extent caused by Customer’s breach, unlawful provision, unauthorized source, or unlawful or out-of-scope use. It is not a separate pool for each category or party, includes the one-times cap, and does not stack on top of it.

Under the contract draft, claims are classified as one Related Claim Event only when they arise from the same specific act or omission, or a continuous, repeated, or interrelated series with the same root cause, Customer, Product, environment, and substantially the same loss. Similar legal theories, subject matter, or time proximity alone do not create one event. Regardless of the number of claims, claimants, theories, remedies, or Related Claim Events, the highest applicable cap is one non-replenishing aggregate cap across the affected Order; the one-times and two-times caps do not stack. Double recovery is prohibited. Only an Executed Agreement makes these rules effective.

This public Notice makes no representation that Calamophyton carries a particular insurance policy and creates no duty to maintain insurance or furnish evidence. The internally approved evidence-boundary drafting direction still requires verification against the actual policy, counsel-cleared final bilingual rider bytes, exact Order-specific decision and clause digests, conspicuous presentation, and express incorporation into the executed Order. Insurance never guarantees performance or indemnity, creates a separate recovery pool, or expands or replenishes a contractual liability cap unless mandatory law requires otherwise.

17. Third-party claims and mutual defense and indemnity

The contract draft limits Customer defense and indemnity to an actual third-party claim caused by Customer’s breach of an Executed Agreement, unlawful provision of Customer Data or specifications, unauthorized source use, or unlawful or out-of-scope use, and carves out Calamophyton-controlled causes. It separately covers specified infringement claims against Calamophyton’s paid, unmodified core software. Only an Executed Agreement makes those duties effective.

Calamophyton’s obligation does not apply to the extent the claim would not have arisen without a Customer modification or combination, Customer-directed specification, external product, Customer Data, a claim inherent in open source, or continued use after a stop notice.

The contract draft provides that the duty to defend begins when a covered claim is made and notified, and indemnity applies to a final judgment or approved settlement. Procurement of rights, modification or replacement, and termination with refund are exclusive only as to continued availability or use; they do not displace covered defense or indemnity duties. Only an Executed Agreement makes these rules effective.

18. Export controls and legal compliance

Customer must comply with the export-control, economic-sanctions, privacy, intellectual-property, and other laws of any applicable jurisdiction governing access to, transfer, export, re-export, end users, and end uses of the Developer Materials. Customer must not provide or use the Developer Materials in a prohibited territory, for a prohibited person, or for a prohibited purpose.

19. Contract notices and changes

Until an Executed Agreement expressly designates a notice method and address, [email protected] is an inquiry channel only and is not an agreed contractual notice address. This Notice creates no rule for contractual receipt or effect. Only the Executed Agreement determines the required channels, receipt evidence, and effective time.

Online terms and public notices do not amend an Executed Agreement. A changed term requires a successor Executed Agreement that binds the predecessor and successor contract envelopes, acceptance receipts, document and clause manifests, and a complete supersession record. An incomplete chain has no superseding effect.

20. Order of precedence

Only an Executed Agreement establishes document precedence. The current contract-drafting hierarchy is a successor Order with a complete supersession chain; precise Order special terms; the DPA and Security Schedule within their stated subjects; the applicable Product Schedule; the exact Master Terms edition; and separately executed supplemental terms identified by title, version, and SHA-256. This Notice and other public documentation are nonbinding and do not enter that hierarchy.

This Notice cannot become an incorporated click term merely by display, browsing, download, checkbox, or click. An internal draft or unidentified document has no contractual precedence, and no document implicitly expands a Product authority boundary.

Additional or conflicting terms in a Customer purchase order, portal, or other standard document do not apply unless Calamophyton expressly signs them.

21. Governing law, jurisdiction, and general terms

Governing law and forum are set out in the executed Order. Urgent interim relief may be sought in a court with jurisdiction, and final enforceability remains subject to applicable law and counsel review.

Waiver, severability, and assignment rules must appear in an Executed Agreement. This Notice creates none of those contractual effects.

An Executed Agreement constitutes the parties’ entire agreement for its transaction and supersedes prior proposals, representations, negotiations, and drafts concerning that transaction. A mutually executed successor agreement is formed at final verified party execution, but it does not replace its identified predecessor as the controlling agreement until a separate trusted supersession certificate binds and records the complete predecessor and successor evidence. Replacement is prospective from that trusted record time and cannot be backdated. Sales materials, demonstrations, proposals, oral statements, email, and this Notice do not create a warranty or amendment.

The executed Order must select exactly one language-control state. `DOMESTIC_KOREA_KO_CONTROL` and `INTERNATIONAL_KO_CONTROL` make the signed Korean edition controlling; only `INTERNATIONAL_EN_CONTROL_EXPRESS` makes the signed English edition controlling. No language can become controlling through a website default, translation, course of dealing, or inference.

22. Company information and contact

• Korean contracting name supplied for this draft: 칼라모피톤 인더스트리즈 유한책임회사
• Company-designated English contracting name: Calamophyton Industries LLC (comparison against an authoritative corporate record remains an external gate before execution)
• Legal and contractual inquiries: [email protected] (external delivery tested on 1 September 2026; contractual notice only when an executed agreement expressly designates it)
• Status: predeployment counsel-review candidate; not effective
• Candidate version: 1.0