Systems Layer

From intelligent answers to proof-carrying action.

SOVEREIGN is the product layer behind the research program: a local-first digital twin and decision cockpit for users who need AI to finish real work, respect boundaries, preserve evidence, and learn without self-deception.

observe warrant act learn cleanly

Product Map Proof-Carrying Action Evidence Map Private Briefing

Current-state dashboard visual for proof-carrying action systems.

Product Position

One core system, several application fronts.

The core product is not a chatbot and not a single trading or robotics module. It is a proof-carrying cognitive action infrastructure: a system that turns goals, observations, uncertainty, constraints, evidence, failed attempts, and user trust into auditable work orders and bounded actions.

Finance and robotics are separate product fronts because they stress different parts of the same substrate. Finance tests proof, restraint, regret, and execution evidence. Robotics tests embodiment, recovery, perception, and action under physical uncertainty. The personal digital twin is the user-facing cockpit that binds them into a usable service for high-knowledge and high-net-worth users.

Core

Digital Twin Cockpit

A private operating layer for plans, decisions, memory, workflows, evidence gates, task closure, and value ledgers.

Finance

Proof Action Lab

Trading is treated as a cost-bearing testbed for whether an AI system has earned the right to act.

Robotics

Embodied Evidence

Robot learning papers stress perception, recovery, provenance, physical uncertainty, and when not to act.

Public

Research Archive

The website, Zenodo, GitHub, and Hugging Face expose reproducible slices without exposing private systems.

Service Surface

Public-facing services without exposing the private core.

The product language should be concrete: what enters, what comes out, and which claims remain out of scope.

Audit Sprint

Decision Proof Review

Input: workflow notes, logs, or decision traces. Output: claim boundary, proof envelope, no-go/gate report, and repair queue. Boundary: no legal, medical, or financial advice.

Reliability

Agent Gate Review

Input: an agent task flow. Output: ActionWarrant schema, failure-memory map, no-credit repair plan, and counterexample checklist. Boundary: no deployment certification.

Research

Evidence Ladder Review

Input: paper, benchmark, or system claim. Output: evidence tier, artifact gaps, reproducibility path, and reviewer attack list. Boundary: no authorship or acceptance guarantees.

Proof-Carrying Action

The first positive result can be qualified restraint.

The latest finance evidence pack does not claim profit. It shows a stricter result: the system blocks itself when execution proof, denominator evidence, and regret computability are not closed.

AxisCurrent StateMeaningProduct Use

GateNO_GO_PAPER_EXECUTION_BLOCKEDQualified restraintPrevents premature action

Denom.money_denominator_n = 0No money evidence admittedBlocks fake edge claims

WarrantActionWarrant pass = 0No action earned authoritySeparates advice from action

Leaksauthority leak = 0; credit leak = 0Repair work did not become rewardProtects clean learning

QueueVersioned repair queue; 18 receipt gapsThe system knows why it cannot actTurns no-go into work orders

Pilot Path

A useful pilot starts with a boundary, not a sales pitch.

The public site should make it clear how a serious reader can move from interest to a scoped private trial without asking for protected code, customer data, or live execution authority.

Step 1

Private Brief

Input: goal, workflow, constraints, and what must not be exposed. Output: claim boundary, evidence map, and no-go criteria.

Open private briefing

Step 2

Evidence Gate

Input: non-sensitive logs, task traces, or decision samples. Output: ActionWarrant schema, receipt gaps, and no-credit repair queue.

Step 3

Demo Cockpit

Input: a toy or redacted workflow. Output: a runnable warrant/receipt loop that shows when the system acts, waits, or refuses.

Step 4

Scoped Pilot

Input: agreed private environment and success criteria. Output: local-first deployment plan, artifact ledger, and stop rules.

Boundary

Not Offered Publicly

No regulated advice, no deployment certification, no live trading claim, and no disclosure of customer memory or private orchestration.

Public Proof

What Can Be Shared

Sanitized schemas, toy demos, claim boundaries, DOI-backed papers, public counterexamples, and non-sensitive repair patterns.

Operating Loop

Every action needs a proof trail.

The operating chain is:

goal -> observation -> relation field -> thesis -> falsifier -> warrant -> receipt -> regret -> scar -> clean learning

A suggestion without an execution certificate is not an action. A repair queue item is not progress credit. A pretty report is not reward. A no-action decision is still evidence if it has a wait-policy receipt and a counterfactual baseline.

Open-source boundary map for public and private layers.

Release Boundary

Open enough to verify. Private enough to survive.

Public releases should include papers, evidence maps, claim boundaries, schema, small runnable demos, and reproduction notes. Private layers should keep customer workflows, trading runtime details, credentials, unpublished execution traces, and product-specific decision logic out of public repositories.

Public: research pages, DOI links, non-sensitive schemas, toy demos.
Delayed public: submitted artifacts after decision or camera-ready windows.
Private: execution authority, customer memory, proprietary workflows, and live system logs.

Claim Boundary

We are not training AI to sound more confident. We are building systems that know when they are not yet allowed to act.

This boundary is not weakness. It is the difference between a persuasive model and a responsible action system.