A decision engine is software that takes a named personal choice and returns a structured pass: fields, tensions, and a reading you can accept or reject. It helps when the bottleneck is structure. It fails when the bottleneck is missing facts, acute danger, or a wish to be told you are magical.

A decision engine helps when you can name options and you need a structured pass. It does not help in emergencies, when facts are missing, or when you are using it as a mood machine.

Numira is Croncode’s engine in this category. It uses numerology as the lens. That is a design choice, not a claim of omniscience. Yusufhan Sokur and Goktug Unver would rather you close the app after one honest pass. Listing: Numira on the App Store. Studio: home.

When is the engine the right desk?

Right desk means you already did the adult collection: documents, dates, who pays. The engine then helps you see the shape. If you skip collection, the reading will decorate a vacuum.

This is the same honesty we ask of product teams in data versus stories. Feelings are data. They are not a substitute for the lease clause.

When does the engine become harmful?

• Emergency: leave the phone’s decision toy and use emergency services or a safe person.
• Looping: three reruns with the same facts is entertainment. Stop.
• Authority laundering: “the app said so” to avoid telling a partner.
• Scope creep: using it for every snack and email. That is decision fatigue, not wisdom.

Harm is not mystical. It is delayed action and displaced responsibility. Feature-rich engines invite looping; we resist extra surfaces in feature creep. Quiet tools are safer; see minimalist interfaces.

How do you brief the engine so the pass is usable?

1. Write options as verbs: accept, decline, wait until a date.
2. Add the facts that would change your mind.
3. Add the people who share the outcome.
4. Run once. Copy anything useful to a journal.
5. Take the action or the dated wait the same day if the stakes allow.

If you cannot write verbs, you are not ready for an engine. You are still in a mood. Walk, sleep, or collect the missing paper. A useful test: if a stranger could act on your sentence without calling you, it is specific enough. “Fix my life” fails that test. “Decline the offer by Friday and stay 90 days” passes. AI in our stack is infrastructure for that pass, not a friend; AI as infrastructure.

Write the stop rule before you open the app: one pass, then a journal line, then a conversation if someone shares the cost. If you skip that order, the engine becomes a stall you can blame. The stall still has your name on it.

How does this sit next to other Croncode products?

YourStyle is garments. Luviport is transfers. Spylie is a different investigation job. Do not merge them into one “tell me what to do” blob. A small team ships separate jobs; lean studio structure. More: Journal, Ozgur Ismet Ozkan.

Frequently asked questions

Can a decision engine be wrong?

Yes, in the sense that a reading can miss your values or your facts. You remain the decider. Wrong is also what happens when you type a vague choice.

Should I use it with a therapist or advisor?

You can bring a structured note to a qualified human. Do not replace that human with an app when the issue is clinical or legal.

What if I feel calmer but still do not act?

Calm without a dated action is incomplete. Write the next verb and a time.

Is waiting a valid engine output?

Yes if the wait has a date and a fact that will arrive. Endless wait is a hidden no.

Do I need numerology for a decision engine to count?

No in the abstract. Numira’s engine happens to use numerology. Other engines use other lenses. Judge the job: named choice, one pass, clear limits.