SagaWizard™: Functional Analysis

What SagaWizard Actually is…

SagaWizard interface is a visual transaction builder for SagaChain. It is not a demo page, placeholder, or documentation stub. Instead, it functions as:

A drag-and-drop transaction builder UI that allows users to compose, inspect, and submit real SagaChain transactions without writing raw SagaPython™ code.

This makes it a first-class execution interface, not a tutorial surface.

---

Core Capabilities of the SagaWizard

SagaWizard enables users to visually assemble fully valid SagaChain transactions by chaining together structured actions.

A. Account Creation & Access

• Create new SagaChain accounts
• Select and operate on existing accounts
• Iterate across accounts as first-class execution targets

Accounts are not wallets in the traditional sense; they are persistent on-chain objects.

B. Industry Class Tree Access

SagaWizard exposes all deployed industry class trees, including (but not limited to):

• Deployed
• Finance
• Automotive supply chain base
• Implemented
• Real Estate
• Music
• Pharma
• Supply Chain
• Government / Regulatory

Each tree represents a globally shared class hierarchy, not per-app contracts. Users can:

• Browse class trees visually
• Select specific classes
• Inspect available methods and fields
• Instantiate new objects from those classes

C. Object Instantiation & Lifecycle Control

Through SagaWizard, users can:

• Instantiate objects from SagaPython™ classes
• Bind objects to accounts
• Invoke methods on existing objects
• Modify persistent object state
• Iterate across collections of objects or accounts

All of this happens inside a single composed transaction.

• No redeployments.
• No contract recompilation.
• No app-specific state silos.

D. Transaction Composition (Drag & Drop)

SagaWizard allows users to:

• Chain execution steps visually
• Control execution order
• Reuse objects created earlier in the transaction
• Pass outputs from one step into the next
• Inspect the resulting transaction graph before submission

This is closer to workflow composition than “calling a smart contract.”

---

Submission Path: SagaWizard → SagaScan

Once a transaction is composed and submitted from /SagaWizard:

• The transaction is executed on SagaChain™
• Execution artifacts (objects, state changes, LOIDs) are committed
• The transaction becomes visible in SagaScan

---

Role of sagascan.prasaga.com

sagascan.prasaga.com is not the builder, it is the inspection and observability layer.

It is where users can:

• View transactions created in the SagaWizard
• Track execution status
• Inspect transaction details
• Observe object creation and mutation
• Follow account-level activity over time

In other words:

• SagaWizard creates transactions.
• SagaScan shows you what those transactions did.

This clean separation mirrors professional systems design:

Authoring surface vs Audit surface

Execution UI vs Ledger visibility

---

Why This Is Architecturally Important

SagaWizard represents a fundamental departure from traditional blockchain UX:

Traditional Blockchains	SagaChain™ SagaWizard
Write code	Compose visually
Deploy contracts	Use shared class trees
App-specific state	Global persistent objects
Wallet-centric	Account-centric
Contract calls	Object lifecycle operations

This makes SagaWizard suitable for:

• Enterprise users
• Regulators
• Standards bodies
• Non-developer domain experts
• Cross-industry interoperability pilots

---

Conceptual Summary

The SagaScan™ SagaWizard is best understood as:

A visual compiler for SagaChain transactions

It allows users to:

• Assemble executable logic
• Operate on global industry models
• Instantiate and manage persistent objects
• Submit real transactions
• Audit results through SagaScan™

All without writing a single line of raw blockchain code.

---

One-Sentence Definition

The SagaScan™ SagaWizard is a drag-and-drop transaction builder UI that lets users create accounts, access global industry class trees, instantiate and operate on persistent objects, and submit executable SagaChain transactions that can then be tracked and audited in SagaScan.

---

Important Reminders

This remains a non-production development environment: no real cryptocurrency, unsigned messages, periodic resets, and potential for silent failures (e.g., script crashes). It’s ideal for prototyping, learning the meta-class object model, and providing feedback to PraSaga.

For deeper guidance, check the linked resources directly on the page:

• Demo videos playlist (covers client usage, object instantiation, etc.)
• Sample scripts repo

If you’re actively developing or demoing, this wizard UI is a game-changer for quickly iterating on SagaChain concepts – much more visual and approachable than pure CLI work. Let me know if you’d like tips on specific script examples or common patterns!