PRODUCT / AI / UX / 2026

Independent prototype

Ally Ai

From scattered intentions to daily action.

REAL INTERFACE / 16 SEP 2026

THE TECHNOLOGY STARTS WITH AN ORDINARY SENTENCE

Illustrative request: “I want to start a project, but I am not sure I can handle the scope.” The same example continues through the analysis and decision map below.

Ally Ai entry screen with voice, text and example prompts
Product screenshotPublic product entry screen. No private dialogue or account data is shown.
Open original
Ally Ai entry
Ally Ai entry screen with voice, text and example prompts

Public product entry screen. No private dialogue or account data is shown.

01

Voice

A raw thought can enter without first becoming a polished prompt.

02

Free text

The interface asks for the situation, not for technical parameters.

03

Low-friction starts

Examples reduce the blank-page barrier without predetermining the answer.

EXPLANATORY RECONSTRUCTION04 / 04

Decision map

Two routes are compared: commit to a large scope immediately, or test one narrow scenario first.

First reversible stepBuild one scenario and record the actual time before committing to the full project.
01

What is known

In this illustrative example, two evenings a week are available for the project.

02

What matters

The current commitments need to remain stable while the idea is tested.

03

What is missing

The time required for a useful first version is still unknown.

04

What to try

Build one narrow scenario, record the actual time and revise the route if it does not fit.

The product screenshot is a real capture. The decision-card panel is an explanatory reconstruction of the implemented data and prompt logic, clearly separated from the live screen.

SYSTEM VIEW

HOW IT WORKS

A person describes a situation in everyday language. The system separates facts from assumptions, connects them to values and criteria, compares options and returns a structured decision map instead of generic advice.

01

Dialogue

Open request and clarifying questions

02

Context analysis

Facts, values and unknowns

03

Decision model

Options, risks and criteria

04

Action map

Conclusion and reversible first step

Simplified system view — the purpose is to explain the logic, not imitate a deployment diagram.

Engineering details and safeguards
ENGINEERING CUTAWAY

FROM WORDS TO A SYSTEM THAT CAN REVISE ITSELF

The core innovation is not the chat window. It is the controlled loop between a live conversation, structured memory, a decision artifact and feedback from reality.

01

Signal

The current message is weighted more strongly than old context. A router selects only the relevant decision, safety or voice capability.

02

Context

Conversation memory, confirmed meanings and evidence are assembled into a compact working context — not an unlimited personal dossier.

03

Decision

The model separates what is known from what is assumed, compares routes and produces a structured decision card instead of generic advice.

04

Reality

The person confirms, edits or rejects the interpretation. New evidence changes the map and makes the next answer more precise.

LIVING MEMORY

An interpretation earns its status

The map keeps the source, confidence and evidence count. Repeated evidence may strengthen an item, but the person’s explicit confirmation remains decisive.

01Observationone source
02Testingcautious hypothesis
03Repeatedindependent evidence
04Confirmedperson decides
CONTROL LAYER

Useful without pretending to know the person better than they do

01

Evidence before confidence

A new observation starts as a hypothesis. Confidence grows only when independent conversations support it.

02

Human retains control

The person can confirm, edit, resolve or reject an item. The system does not silently turn an inference into a fact.

03

Sensitive wording

Sensitive patterns are phrased as possibilities; diagnostic language is filtered from generated map items.

04

Urgent route

Immediate danger, medical urgency and self-harm signals bypass the ordinary answer and receive a dedicated safety response.

IMPLEMENTED FOUNDATION

Node.js / Express service · PostgreSQL state and event history · structured JSON schemas · prompt and safety routing · OpenAI with optional Gemini and Claude modes · browser and unit test contours

This diagram explains the repository architecture; it is not a claim that every experimental module is enabled in production.
A DECISION I MADE

A structured decision map instead of one long recommendation.

Why

Facts, criteria, unknowns and the next step remain visible and can be revised separately.

Trade-off

The conversation needs extra clarification before it can produce a useful map.

MY CONTRIBUTION

Product concept, decision logic, UX and implementation direction.

DELIVERED

Decision map, conversation flow and prototype interface.

APPLICATION

AI assistants, advisory systems and decision-support interfaces.

Have a similar task or an idea to explore?

DISCUSS A TASK →