Skip to main content
Egifta Growth

Trust & evidence

Why an evidence state sits next to every finding.

A growth recommendation is only worth as much as what it is based on. Egifta Growth records that, shows it, and lets it decide what the system is allowed to do without asking you.

What is running today

Egifta Growth is in active development. The Proofence Engine integration is defined as an adapter contract with a deterministic mock — no live verification is running, and nothing on this website is produced by one. Verification capability is delivered in a later phase.

Evidence states

Part of the data model, not a presentation choice.

Every finding, recommendation and claim carries one of these. Their colours are reserved for this meaning and are never used for decoration.

  • Evidence status: Observed

    Observed directly

  • Evidence status: Corroborated

    Corroborated by more than one source

  • Evidence status: Inferred

    Inferred from available signals

  • Evidence status: Unverified

    Not yet verified

  • Evidence status: Disputed

    Contradicted by another source

Decisions

What the trust boundary can decide

When Egifta Growth evaluates a claim, a recommendation or a proposed agent action, the result is one of four decisions. Two of them stop the system and hand control back to a person.

  • Approved

    The evidence supports the subject. Work may proceed.

  • Proceed with caution

    Supported, but with a caveat worth reading before acting.

  • Human review required

    A person must decide. The system will not decide on your behalf.

  • Blocked

    The evidence does not support this. It cannot proceed automatically.

Designed boundaries

Boundaries agents do not cross

Agents are planned, not built. These are the rules they are being built to.

  • An action that publishes anything externally requires a recorded human decision.
  • An action that spends money requires a recorded human decision.
  • A claim with no supporting evidence cannot be marked publishable, however well it is written.
  • A claim supported only by model inference is not publishable until something corroborates it.
  • An experiment cannot enter a running state without passing through explicit approval.

Verification

Verification through Proofence Engine

Egifta Growth is designed to reach Proofence Engine for verification through an explicit adapter boundary, so that Egifta Growth remains an independent product. That verification is not live: the adapter today is a deterministic mock and verifies nothing. An enterprise governance integration with AtlasProof is planned and does not exist yet.