Governed lifecycle

Progress without false completion.

Soval keeps the path understandable. Katra Forge keeps each transition exact: inquiry is not formation, approval is not execution, and a passing result is not release.

Two colleagues handing over a notebook in a bright workspace
Keep the next step clear.Illustrative AI-generated imagery

The wider Katra process

The hosted workroom currently guides five steps: frame, gather, develop, check, and hand off a review copy. The wider process below describes component responsibilities; formation, repository admission, and downstream execution are not connected to this workroom.

  1. 01
    Express intent

    A human states an idea or desired outcome in natural language. No project is inferred.

    intent
  2. 02
    Capture exact source

    Smusma preserves the deliberate submission, classification, scope, and intended outcome.

    captured
  3. 03
    Resolve before creating

    The system finds a related active inquiry, identifies ambiguity, or offers an explicit unrelated line.

    active inquiry
  4. 04
    Select a baseline

    One primary workstream binds to exact intent. Parallel work requires an explicit fork and reconciliation condition.

    primary / fork
  5. 05
    Develop the inquiry

    Evidence, assumptions, unknowns, requirements, risks, constraints, and material questions become traceable.

    candidate
  6. 06
    Request formation explicitly

    The human selects whether work should become a project or application. Selection still does not form it.

    formation withheld
  7. 07
    Evaluate formation evidence

    Identity, policy, repository, verified result, and lineage must all be valid, current, and attributable.

    prepared
  8. 08
    Build Product Definition

    Sarek coordinates requirements, backlog, Evidence State, and proposed transitions without becoming the decision authority.

    needs decision
  9. 09
    Compile and review

    Deterministic inputs produce candidate PRD bytes, gaps, traceability, and a semantic diff for attributable human disposition.

    human approved — pending admission
  10. 10
    Admit and read back

    Exact repository checks, admission, and independent readback bind the final PRD and implementation handoff.

    verified

Safe failure is part of the product.

WITHHOLD is not a dead end. It identifies the missing prerequisite and preserves a safe next action.

Unauthorized action

An agent asks to inspect or change a scope outside its explicit delegation. Soval withholds before protected state is resolved or disclosed.

request → delegation check → WITHHOLD

Stale state

A baseline, revision, approval, or provider observation has moved. The action stops, identifies drift, and requires refresh or reconciliation.

request → freshness check → refresh

Lost response and retry

An exact retry returns the prior result without creating a duplicate effect. The same command ID with changed meaning fails closed.

retry → semantic match → IDEMPOTENT

What Soval shows at every consequential step

The interface keeps ten facts separate so a fluent conversation cannot visually impersonate a completed transition.

BEFORE

Intent, target, current state

What was requested, the exact object affected, and its verified precondition.

DECISION

Effect, evidence, authority

What would change, what supports it, who may decide, and what remains unknown.

AFTER

Execution, receipt, readback

What actually happened, the returned evidence, and the independently verified result.

Human entry

Start with the outcome.

The person should not need repository syntax, internal identifiers, or command vocabulary. Soval surfaces those mechanics only when they materially affect the action.

Agent entry

Use the same path, with bounded authority.

An agent carries attributable identity and delegated scope. It may analyze, draft, propose, verify, or execute only as separately permitted.

A precise vocabulary for real state

Generic “done” language hides meaningful differences. Soval uses explicit state names and their authority effect.

Candidate

Prepared work with no accepted authority.

Withheld

An effect safely stopped with an addressable reason.

Stale

A required binding no longer matches current state.

Authorized

An attributable decision permits a specific effect.

Executed

The effect was attempted or completed; verification remains separate.

Verified

The actual result was independently read back.

Admitted

The artifact entered the governing repository boundary.

Released

Only used when a separate release decision and proof exist.