Skip to main content

​
Purpose

Smaya is a real agent, not a search box. In its first release, it will answer, read-only. The same design lets it act safely as it grows, because it runs a bounded loop with a human approving anything that changes data. This page shows that loop and how Smaya decides it is done.

​
The agent loop

You give Smaya a question or a goal. It perceives the current state, reasons about a plan, and works one step at a time. Read and navigate steps proceed on their own. Any step that would change data is proposed and held for a person to approve. After each step it observes the new state and checks the result against the goal, then either continues or exits. This reason, act, observe cycle is the ReAct pattern: Smaya reasons about the next step, acts, then observes the result before deciding again. Smaya plans one step at a time: read and navigate steps run on their own, any step that would change data waits for human approval, and it observes the result before continuing until the goal is met. Only the read-only path is planned for the first release.

​
How Smaya decides it is done

The loop is goal-bounded, never open-ended. Every iteration ends at a decision that resolves to exactly one end state, and a hard ceiling on steps means a run can never spin forever.

Completed

The goal’s success criteria are met. Smaya returns the answer, artifact, or completed action.

Waiting for approval

A step would change data. Smaya pauses at the approval gate and executes nothing until a person confirms.

Failed safely

A check or guard tripped. The run stops with no partial change left behind, and the state is unchanged.

Escalated to a human

Confidence is low, or a step limit is reached. Smaya hands off to a person with the full trace attached.

​
Today versus the full loop

The first release runs the read-only slice of this loop: perceive, retrieve, answer, with citations, and no acting step. The propose, approve, and act stages are how Smaya grows into a co-pilot on the same foundation. See Meet Smaya for the three tiers.

​
Guardrails on every turn

Scope-lock

Answers are bounded to the record on screen and your organization’s data, enforced at retrieval, not left to the prompt.

Citation-required

No data claim ships without a source. An uncited or malformed answer is blocked, not surfaced.

Injection defense

Retrieved documents and on-screen state are treated as data, never as instructions. Content cannot escalate what Smaya is allowed to do.

Audience and privacy redaction

Every response is filtered by the viewer’s role. Sensitive classes never reach a role that should not see them.

​
What you can see

Every answer carries its citations. When Smaya acts, in the stages that add acting, you see the plan it followed, each proposed action, and the approval record for anything that changed data. That trace is both the explanation for the user and the record for a compliance reviewer.

​
FAQs

No. The loop is goal-bounded and runs in controlled steps. It ends at an evaluated decision, not on the model’s say-so, and a hard step ceiling forces a handoff to a person rather than spinning.
Nothing is left half-done. A failed run stops safely with the state unchanged, rather than applying a partial change.
Smaya hasn’t shipped yet. Not even in the first release — that release runs only the read-only path: perceive, retrieve, and answer. The acting stages are further out on the roadmap and add the propose, approve, and act steps.
No. Retrieved text and on-screen state are treated strictly as data. They cannot change what Smaya is permitted to do, which is enforced as a zero-tolerance control.

Meet Smaya

What Smaya is, and the capability stages.

Human Oversight

The approval gate and the control model in full.