CALAMOPHYTON / DEVELOPER

Find the missing evidence.Know what to check next.

Check whether the supplied records support a claim. See why a comparison is blocked and which material is needed.

Run either public example without signing in. Fixed synthetic records only; no customer uploads or actual approvals.

Discuss your workflowRun the API
01 / FINANCIAL RECORD REVIEW

Does the appendix support the memo?

Supplied: a memo stating a revenue share and a document index. The appendix cited by the memo is missing.

Original-packet result

The share comparison is withheld without the appendix. Select supporting records to see what changes.

Run financial record review
02 / INDUSTRIAL SUPPLY CHAIN

Will stock last until the later delivery?

Supplied: lead time changed from 14 to 31 days, conflicting arrival dates, and no opening-stock record.

Original-packet result

Conflicting dates and missing stock block the calculation. A shortfall can remain after the evidence is supplied.

Run supply-chain warning
GET / PUBLIC DEMO

Run the same review through the API.

Compare the original financial example without an API key. This command calls the currently published site.

Public API requestshell
curl --fail-with-body 'https://developer.calamophyton.com/api/demo/v3/golden-thread?domain=finance-dd&grant=none&packet=initial&path=request-evidence&release=2026-09-05.1'

Read sources, findings and review paths in record, and the digest in receipt. Requirements are simulated; no approval is issued.

Fixed synthetic records only; no customer input or private product Core calls. A matching hash does not establish truth or authority.

Data use conditions — Using customer data or outputs for training or product improvement requires executed documents specifying the data, purpose and other conditions. This notice grants no permission and does not constitute consent.

PRIVATE PREVIEW / INQUIRY OPEN

Want to review your own records?

Inquiries are open. Customer environments and access are not issued immediately.

  1. Describe the review task.

    Include the organization, contact, question, users and integration scope. Do not send customer records or credentials in the first inquiry.

  2. Review scope and requirements.

    If an evaluation is separately offered, agree permitted material, success criteria, price, term and contract.

  3. Access follows environment verification.

    Named users receive access only after the customer environment and controls are prepared and verified. An inquiry is not a delivery date or service commitment.

The email link in the inquiry guide opens your mail app. Review and send the message yourself. Share customer records only after agreeing the transfer method and processing conditions.

Customer data use conditions
Prepare an inquiry and review the conditions ↗
02DECISION STRUCTUREPUBLIC FLOW · PRECOMPUTED
PÓLYA

Compare options with their assumptions, constraints, dissent, and conditions for further review.

THREE PRODUCTS / ONE CONNECTED RECORD

One case. Three distinct responsibilities.

HARBINGER finds the change or missing evidence. PÓLYA uses those findings to structure review paths. RAIFFA checks the requirements for the selected path. The public example simulates those requirements; it does not approve an action.

View the product connection diagram
CALAMOPHYTON / SYSTEMHow the three products connect
HARBINGERPÓLYARAIFFAEOS Finds and verifiesevidenceWeaves verified evidenceinto one situation pictureSupports the decision.Keeps the approval recordOperating and deployment platform beneath the three · deploy · update · environment security boundaries
From evidence to a human decision, on EOSView product connections

Before you begin

What can I run here?

Run financial record review and supply-chain reviews using public synthetic records. Choose another record set to load its precomputed gaps, review options, and simulated requirement checks.

Can I use my company’s data?

The public site does not accept customer data or uploads. Contact support to discuss your workflow and the scope of a separate environment.

Does a completed review mean approval?

No. The public review checks predefined simulated requirements. It does not grant organizational approval or authority, or execute external actions.

Is this limited to finance and supply chains?

These are the two examples currently available publicly. Other applications require a separate review of the data and review criteria they need.

How much time will this save?

The results show the comparisons performed and the checks still needed. Actual time savings have not yet been measured.