Prepare a Private Preview inquiry.

What you can run and what requires a customer environment

Start with the public evidence review: its v3 API compares fixed synthetic financial-record-review or supply-chain records. Earlier v2 links remain available. Neither flow connects to the private product Core packages.

For a proposed customer evaluation, review the HARBINGER data model, customer OpenAPI contract, request and error formats, fixed financial reference response, Capture Plane security model, and regional infrastructure candidate. English and Korean documentation and the Developer Materials draft for counsel review are also available.

The public example serves precomputed responses for fixed synthetic incidents; candidate customer infrastructure does not establish an operational customer service. A customer API address, Customer Sandbox, live Capture Worker, customer SSO and MFA, customer key management, durable customer audit store, source approvals, and an SLA remain unavailable until the customer environment is integrated and verified.

• PUBLIC FIXED EXAMPLE · AVAILABLE — stateless synthetic GET execution with HTTP status, request ID, precomputed HARBINGER, PÓLYA, and RAIFFA objects, and a same-input SHA-256 digest
• REFERENCE RESPONSE — a fixed fictional-company example (Example Insurance), not executable implementation code
• PUBLIC EXECUTION FIXTURES — synthetic financial-record-review and industrial supply-chain cases, not a real company, customer material, or source connection
• CUSTOMER INFRASTRUCTURE CANDIDATE · NOT DEPLOYED · UNSIGNED — customer-isolation and READ_ONLY infrastructure definitions
• INQUIRY OPEN · ACCESS NOT ISSUED — review the proposed organization, purpose, material, and scope
• NOT CURRENTLY AVAILABLE — self-service signup, customer operational API, instant Sandbox, or production SLA

The customer fixes the evaluation boundary first

If separately offered under executed terms, the intended model is a paid, fixed-scope pilot for qualified enterprises and institutions and their named users. The Order must choose exact fixed dates or a 56-day period beginning only after every stated start condition is satisfied. It would test whether HARBINGER can preserve an evidence-bearing view inside one bounded business inquiry; it is not an invitation to upload an undefined data estate. The organization should identify:

• Economic buyer and accountable recipient of the evaluation
• One business inquiry, time window, success criteria, and stopping rule
• Permitted and excluded material, third-party rights, and processing purpose
• Named participants, roles, and the organizational result boundary
• A prohibition on treating output as recommendation, approval, command, or automated action

Calamophyton supplies a reviewable evaluation package

• HARBINGER Core contracts for objects, observations, change, evidence, time, and gaps
• A GET-only OpenAPI 3.1 contract with literal authority and error states
• A fixed official-source response example that returns to the origin
• A Capture Plane boundary separating acquisition from interpretation
• Availability labels that distinguish implemented assets from operational commitments
• Documentation and a changelog suitable for product, security, and legal review

A completed evaluation should leave five kinds of evidence

1. 01
   Product fit

   Show what was observed, what remained unknown, and why the boundary held.

2. 02
   Technical fit

   Review identifiers, time, source coordinates, failure states, and the OpenAPI contract against the customer boundary.

3. 03
   Security fit

   Identify the isolation, identity, key, audit, retention, and deletion evidence required before deployment.

4. 04
   Legal fit

   Confirm processing purpose, third-party rights, ownership of customer material and output, and contract priority.

5. 05
   Buying record

   Record validated value, remaining risk, pre-production conditions, and accountable owners in one review artifact.

Separate approved defaults from an actual deployment

Calamophyton identifies the version, current status, and product boundary of the contracts, code, deployment configuration, and documentation it expressly supplies. Actual obligations and warranties are fixed in the signed order and schedules. The customer remains responsible for lawful authority over material, approved users and purposes, customer-controlled devices and networks, and downstream use of results.

The following values are internal design baselines for review, not current processing practices or contractual commitments. Any applicable value must be restated in executed terms and verified in the actual environment.

• The internal design default for a first Sandbox is an in-country cloud region, with cross-border replication denied by default
• An evaluation begins with public material or authorized material backed by confirmed lawful use; private customer material is accepted only after security review, applicable agreements, and an approved transfer path all exist
• Raw source material is not stored by default; an expressly approved exception may retain raw material for no more than 24 hours
• The Order and DPA must explicitly select 30, 90, or 180 days for observations and evidence; blank, conflicting, or unverified controls block customer-data processing
• Operational logs use 30 days; personal-data access audit records use one year, or two years where required by law. Both require an explicit choice in executed terms and evidence of the actual controls
• Primary-store deletion is targeted within five days of an approved deletion request; backups remain no longer than 30 days, deletion proof remains one year, and Legal Hold requires separate approval
• Deletion remains unverified until environment evidence covers active stores, versions, backups, indexes, caches, and work queues
• Availability, support hours, incident notice, recovery targets, subprocessors, and customer-specific security controls are not yet operational commitments

Decisions required before contracts and access

All three published contact addresses completed individual and simultaneous external delivery tests on 1 September 2026. The items below cannot be closed by editing documentation or code. They remain external gates until an actual decision, professional review, or access and domain change has been completed.

• Final legal review before applying the license to an external customer
• Final approval of transaction pricing, tax, quoting rules, term, and the applicable Order Form
• Separate approval before customer operational addresses or access-policy changes
• A deliberate choice among owner-only, approved-buyer, public-noindex, or fully public documentation access

Checks required in a customer environment

These items require an implemented environment and verification evidence. A local infrastructure template candidate, public security model, OpenAPI contract, or synthetic fixture does not close them.

• Customer-specific SSO and MFA
• Key management and durable audit-log storage
• A deployed Capture Worker
• Approved source-operator connections
• An operational API address
• SLA and incident response
• Customer-data deletion verification
• A second non-financial vertical slice

From inquiry to evaluation closure

A first inquiry should contain only the organization, accountable contact, business purpose, expected users, and requested integration scope. Do not send customer source data, credentials, internal addresses, or regulated information before a secure channel and processing terms are agreed.

• Agree success, stop, and exit criteria before the evaluation begins.
• Define expiration, revocation, and evidence-preservation rules before access is issued.
• Verify return, deletion, and legal-hold exceptions against the actual environment at exit.
• No evaluation transitions to production without a separate decision and agreement.

1. 01
   Inquire as an enterprise or institution

   Submit the organization, accountable owner, and one bounded business purpose.

2. 02
   Qualify the organization and material rights

   Review the organization, purpose, lawful authority over material, and accountable owner.

3. 03
   Agree scope, commercial terms, and contract

   If Calamophyton offers an evaluation, bind the inquiry, subjects, sources, users, deliverables, price, and term in the executed documents.

4. 04
   Invite named users

   Open access only after the customer-specific environment has been prepared and verified.

• Draft a HARBINGER Private Preview inquirysupport@calamophyton.com · submit only the organization and proposed evaluation boundary↗