Contact
A human address, for a product with no hosted service.
Kalkas has no released hosted service, so there is no support desk, no ticket queue, and no form here that would post into one. What exists is an address a person reads. This page says what to send, what never to send, and what to expect back.
Writing to the team
One address serves every topic: a question about a run, a security concern, a correction to something on this site, or a note that a claim here cannot be supported. A person reads it, and no queue number is issued.
Security reports are welcome at the same address. The trust page names what counts as one, and what is out of scope while no hosted service exists.
ExpectationNo support commitment is stated
No service is open, so there is no response-time promise, no service level, and nobody on shift. We answer when we can, and when a question is outside what we can answer we say so rather than leaving it open.
Asking about a run
Five things make a decision run answerable.
A run is reproduced from its inputs, so a question about one is easiest to answer when it names them. These five are enough to start; anything beyond them is optional.
The run idThe identifier printed with the receipt, copied exactly as it appears. The domainThe domain module you ran: sport and racing, quant research, financial analysis, or another pack. The scenarioThe scenario you chose, when you chose one at all. The receipt lines that refusedCopied as they were printed. The wording is stable, and it names the boundary better than a summary does. The exact revision you ranThe build or source revision you actually took the product from, not the one you meant to run.
Send the fields you are comfortable sharing and no more. If you would rather not send a whole receipt, the five fields above still let us find the same run or explain why a different one appeared. The receipt reference lists what each field carries.
What never to send
None of this is needed, and none of it should be sent.
The list is short and absolute. Nothing here is required to answer a question about a decision run.
- neverCredentials, keys, tokens, or session cookies — yours or anyone else’s.
- neverPersonal data about yourself or another person.
- neverAnyone else’s strategy, evidence, or run records.
- neverA dataset you do not own or have the right to share.
- neverAnything you are under an obligation to someone else to keep.
Safer pathDescribe the steps instead
If reproducing a problem looks like it needs a credential, a key, or someone else’s data, describe what you did in words and send nothing else. Nothing we ask for will ever require a secret, and a question is never improved by including one.
Who this is for
The people this address exists for.
If you recognise yourself in one of these, write; if you are looking for a hosted product to sign up to, none is open yet, and the quickstart is the way to run the loop today.
Operators running the local entry point against sealed evidence, who want a run explained.
Engineers extending a domain module or a model contract, who need the contract read exactly.
Reviewers who have to reproduce a decision months after it was recorded.
Anyone evaluating the approach who would rather ask a pointed question than guess.
A note that a claim on this site cannot be supported is the most useful message of all: the site states its exposure posture on every page, and it is held to that statement here.
Read the contract before writing, if it helps.
Most questions are answered faster by the kernel contracts, the refusal reference, or the privacy statement than by an email. All three are short.