Solvyn frequently asked questions

Question 1

What exactly is Solvyn?

Accepted Answer

Solvyn is execution-record infrastructure for autonomous systems. It captures a consequential run as it occurs and produces a portable .solv Case that people and machines can understand, inspect, verify, replay, share and retain.

Question 2

What problem does Solvyn solve?

Accepted Answer

It closes the gap between an autonomous system taking action and an organization later needing a durable, defensible record of that specific execution.

Question 3

Does Solvyn capture every action?

Accepted Answer

Solvyn captures consequential decisions and actions inside declared execution boundaries. Each Case states what was captured, what was not and what remains unknown.

Question 4

What happens if something is not captured?

Accepted Answer

It cannot be replayed later. Solvyn makes the capture boundary explicit so reviewers know what is and is not part of the preserved record.

Question 5

What is a .solv Case?

Accepted Answer

A .solv Case is the record of one execution. It combines a readable account, a structured evidence index, protected artifacts or references to them, lineage, integrity values and review or Replay data.

Question 6

Is a Case just a report or summary?

Accepted Answer

No. The readable account is one layer. The Case also carries the evidence structure and the protected artifacts or artifact references needed to inspect and test the account.

Question 7

What does replay mean?

Accepted Answer

Replay means walking the fixed recorded sequence from preserved evidence. It does not mean rerunning the autonomous system and expecting the same outcome.

Question 8

What is Live World?

Accepted Answer

Live World is a continuously running reference deployment of Solvyn’s execution-record infrastructure, not a staged demo. The world is the workload; Solvyn seals each completed tick as a .solv Case, and material developments surface through Moments, continuity, evidence, lineage, integrity and Replay.

Question 9

Why are logs, traces and dashboards not enough?

Accepted Answer

Logs, traces and dashboards are essential operating signals and can preserve rich execution histories, but their primary job is to operate and debug the system inside the platform that collected them. Solvyn turns one consequential execution into a portable Case with a declared boundary, stable identity, evidence structure, lineage and verification semantics that can travel beyond the dashboard.

Question 10

How is Solvyn different from observability?

Accepted Answer

Observability helps teams monitor and investigate a running system. Solvyn preserves one specific execution as a durable record that can be reviewed beyond the original runtime and dashboard.

Question 11

How does Solvyn separate fact from interpretation?

Accepted Answer

Observed actions and state changes remain distinct from inferred intent, scoring, analysis or explanation. The Case makes that boundary visible.

Question 12

Can a Case be verified independently?

Accepted Answer

Yes, subject to the verification material available for that deployment. Solvyn treats verification as separate checks: schema and content integrity, evidence-file consistency, producer authenticity, authoritative-record matching, external receipts, continuity and Replay eligibility. A Case should report which checks passed, were unavailable or were not performed; a digest alone does not authenticate the producer.

Question 13

How does Solvyn protect customer data?

Accepted Answer

Security is defined at the same declared boundary as capture. Production deployments are scoped against the customer’s requirements for encryption in transit and at rest, least-privilege access, auditable identities and permissions, storage and key management, and retention and deletion. Solvyn is designed to work within the controls of the environment in which it runs rather than requiring an unmanaged copy elsewhere. The exact control set and responsibilities are documented before production use.

Question 14

How are privacy, redaction and access handled?

Accepted Answer

The underlying record and the view shared with a particular audience are separate concerns. Access, masking, redaction policy, retention and reviewer permissions govern what an authorized reader can see without silently changing the Case.

Question 15

Who owns and controls a .solv Case?

Accepted Answer

Your Cases and customer-provided data remain yours. You determine where Cases are stored, who may access them, how long they are retained and which views may be shared or redacted. Verification does not require a Case to become public, move into a Solvyn-controlled repository or transfer ownership to Solvyn.

Question 16

Can a sealed Case be changed or corrected?

Accepted Answer

No. A sealed Case is read-only and preserves what was recorded for that execution. Corrections, annotations and later findings receive their own identity and lineage rather than silently altering the original. An unrecomputed change to sealed contents fails content-integrity verification. A re-digested edited copy may become internally content-consistent, but it is a different object and is not thereby producer-authenticated or authoritative-record matched.

Question 17

Does Solvyn create a new source of truth that conflicts with our systems?

Accepted Answer

Solvyn does not replace domain systems of record. It creates the execution record that binds material evidence across them for one run. The Case preserves references and lineage back to the systems that participated.

Question 18

Who needs Solvyn first?

Accepted Answer

Organizations running autonomous systems that can affect customers, money, data, infrastructure, safety, regulated processes or material business decisions.

Question 19

Who buys Solvyn and who uses it?

Accepted Answer

Typical buyers include technology, product, operations, risk, security, legal, compliance and executive leaders. Users and reviewers can include engineers, auditors, customers, regulators, insurers, investors, partners and acquirers.

Question 20

Does Solvyn require a platform replacement?

Accepted Answer

No. Solvyn is designed to sit alongside existing models, agent frameworks, workflow engines, clouds, tools, data systems, observability and governance platforms.

Question 21

Where does Solvyn integrate?

Accepted Answer

A deployment begins at the execution boundaries that matter, such as agent actions, tool calls, state transitions, approvals, model or prompt identity, data access, outputs and cross-system handoffs.

Question 22

Where does Solvyn run?

Accepted Answer

Solvyn is designed to deploy at the execution boundary in a customer-controlled cloud, private environment or on premises. The exact capture topology, storage, key management and verifier trust anchors are defined for each deployment. The current public reference deployment runs in Solvyn’s environment.

Question 23

What does a first pilot look like?

Accepted Answer

Start with one consequential workflow or execution class. Define what must be captured, which reviewers matter, what the Case must prove and how it connects to the existing stack.

Question 24

How is Solvyn priced?

Accepted Answer

Pricing is scoped to the execution-record deployment rather than seats or raw log volume. Scope depends on the systems and execution boundaries involved, the Cases the deployment must produce and retain, and the assurance requirements around them. Early engagements are scoped directly with the founding team.

Question 25

Is Solvyn only for AI agents?

Accepted Answer

AI agents are the immediate entry point because autonomy is expanding quickly. The record model can also apply to robotics, industrial autonomy, infrastructure, financial systems, defense and other systems whose actions need to be provable.

Question 26

Why is this a new infrastructure category rather than an observability feature?

Accepted Answer

The durable object is the category boundary. Solvyn gives one execution a portable identity and evidence structure designed to move across operators, reviewers, organizations and time. That job extends beyond monitoring a running system.

Question 27

Why does Solvyn become a platform rather than a feature?

Accepted Answer

The Case can become a durable interface among builders, operators, assurance teams, customers, regulators, insurers, partners and future owners. Blueprint, Reframe, governance, continuity and redeployment build on the same evidence foundation.

Question 28

What creates defensibility?

Accepted Answer

Defensibility can compound through the Case standard, capture and sealing architecture, verification and replay semantics, integrations, cross-domain evidence models, operating history and the workflows that form around a portable execution record.

Question 29

Why would an enterprise adopt this before a regulation requires it?

Accepted Answer

The immediate value is operational and commercial: faster incident review, stronger customer assurance, more confident pilots, clearer change decisions, better diligence and fewer high-stakes questions that begin with a manual evidence hunt.

Question 30

Why is Live World strategically important?

Accepted Answer

Live World makes the thesis inspectable. It is a continuously running reference deployment of Solvyn’s execution-record infrastructure, showing sealed Cases, continuity, evidence, integrity and Replay from a real workload rather than asking the market to accept a slide-deck promise.

The system of record for what autonomous systems actually do.

Nathan Bernard

Leonardo Oliveira

Victor Lara

An autonomous treasury system stopped a $25M transfer after two apparent executive approvals failed independent verification.

Today, one consequential run can be richly observable and still lack a durable review record that travels beyond the originating platform.

Piece together the story after the outcome.

The record already exists because the execution happened.

Watch one execution become a Case.

One Case. Every audience sees the same run clearly.

What exactly executed, with which versions, inputs, tools, state and dependencies?

Don’t take portability on faith. Open the Case.

Six events. One ordered answer.

What the Case establishes, derives and leaves unknown.

Test the objection, not just the happy path.

A versioned execution object, not a metaphor.

Solvyn does not replace the systems you already use. It preserves one consequential execution across them as a portable Case.

Logs, traces and observability

The public proof environment.

From live activity to a durable record

Live World shows one environment. Solvyn is built for yours.

Autonomous action is scaling faster than the evidence systems around it.

expect meaningful AI-agent use by 2027

lack full confidence they could pass an independent AI governance audit within 90 days

name security and risk as the top barrier to fully scaling agentic AI

One condition is enough to warrant a Case.

Authority changes

Material impact

Independent proof

Durable continuity

Preserve what happened. Use it to make the next run better.

Clear answers for technical, business, assurance and strategic review.

Bring us the run your organization cannot afford to misunderstand.