Deterministic methods.
Inspectable evidence.
EcoKure Pty Ltd is an Australian early-stage technology company building a deterministic architecture for qualified computational reuse, independent verification and evidence-bound execution. Published checks, research directions and proposed integrations each carry their own evidence and maturity boundary.
EcoKure / Deterministic architecture
Build the method. Make it inspectable.
Explore the connection between computational reuse research, published checks and evidence-bound authority.
Select an illustrated object to inspect its role.
01 / 03
Retain capability with its conditions.
EcoKure researches qualifying computational structure for reuse with recorded assumptions and verification obligations.
Research / patent-pending architectureFive Australian provisional applications are listed as Filed. Published titles describe applications, not granted claims.
The details a procurement team asks for
| Item | Detail |
|---|---|
| Legal entity | EcoKure Pty Ltd, an Australian proprietary company |
| ACN | 699 693 779 |
| ABN | 98 699 693 779 |
| Registered | 30 June 2026, Queensland, Australia |
| Governing law | Queensland, Australia |
| Stage | Pre-revenue. Founder-led. No outside capital taken to date. |
| Headcount | One. Stated because a vendor-risk assessment will ask, and because it changes what we should be trusted with. |
| Certifications | None held. Controls are built to be auditable, which is a different and weaker claim. |
| Intellectual property | Five Australian provisional applications listed as Filed, spanning published titles on computational methods, verification, dependency-aware change, evidence validity and authority-bound persistence. Inspect the public filing records. |
The finding that made this a company
The first working piece was a deterministic mathematics checker. The question behind it was narrow: could an exact symbolic method answer a question faster and more reliably than asking a language model to reason its way to an answer a calculator already knows.
It could. But testing it against the best available models exposed something larger than the thing being looked for. Frontier models are far more fragile under adversarial and edge-case conditions than their averages suggest, and the failures are not the kind a confidence score catches.
That is the origin of the whole architecture. Not an argument that models are bad, and not an attempt to build a better one. An argument that where the consequence of a wrong answer is regulatory, financial or physical, the answer should be checked by something that cannot be persuaded, and the check should leave a record another person can review.
The same instinct runs through the rest of it. We withdrew three published benchmark results after finding they did not hold, including the most impressive one. That record is on the evidence page rather than deleted, because a company selling verification cannot be selective about verifying itself.
Four commitments, each with a cost we have actually paid
Downgrade the claim to the provable version
Where we are unsure whether a claim is safe, it goes to the weaker wording. This has cost us every headline number we once had.
Publish failures alongside the results
Retractions stay online beneath the original posts. Pilot reports include what did not work and the cases the system declined to decide.
Make it checkable without us
Public repositories, a published audit protocol, and evidence packs a third party can verify without our source code or our cooperation.
Hold missing evidence for review
An unavailable check is recorded as unavailable, never as a pass. It is the least convenient design choice available and it is the whole point.
The questions you were going to ask anyway
| Question | Answer |
|---|---|
| How many customers do you have? | None. Pre-revenue. No pilot has yet run through to a production licence. |
| How big is the team? | One person, with external technical review. If your risk process has a minimum vendor size, we will not clear it yet. |
| What happens if you stop? | A fair question at this stage. Source escrow and the fact that the gates are public repositories are both part of the answer, and it should be discussed before a pilot, not after. |
| What do the filings describe? | Five Australian provisional applications have published titles spanning computational methods, verification, dependency-aware change, evidence validity and authority-bound persistence. Their public status is Filed; the titles are not granted claims. Open the filing records and review date. |
| Is this AI? | No. The checkers are deterministic rulebooks. EcoKure sits after a model, not inside one, and it works the same regardless of which model produced the output. |
| Why should we take a meeting? | Only if a change in rules or evidence has already cost you work. If it has not, we are not useful to you yet and would rather say so. |
Start with one workflow
Thirty minutes, one workflow, and an honest answer about whether this is worth either party's time.