Skip to main content

​
1. Vision: The “Container” for Business Logic

In the AI era, business logic is becoming fragmented and uncontrollable. Runly Protocol aims to define an industrial-grade encapsulation standard for logic. Just as Docker encapsulates runtime environments, Runly encapsulates execution paths. Through RSS (Runly SOP Standard), developers can upgrade non-standard “Prompt Interactions” into Digital Logic Assets featuring MeID Identity Provenance, Heterogeneous Resource Contracts, Human-in-the-Loop (HITL) capability, and Automated Royalty Settlement.

​
2. Core Architecture (The 7-Domain Model)

A .runly asset file consists of seven core domains, ensuring security and determinism throughout the logic lifecycle. 2.1. Manifest
  • Provenance & Uniqueness: Identifies the asset via a globally unique URN and binds it to the creator’s MeID (via Runly Me).
  • Versioning: Follows SemVer 2.0.0 to ensure stability for downstream integrations.
2.2. Knowledge
  • RAG Standardization: Defines access specifications for Semantic Retrieval (RAG) or Vector Databases.
2.3. Skills
  • Tool Decoupling: Statically defines external actions (REST APIs, local scripts) with strong-typed I/O Schema validation.
2.4. Dictionary
  • Strong-Typed Admission: Intercepts anomalies before data enters AI nodes using types like string, json, and file.
  • Artifact Definition: Defines final deliverables such as HTML reports or JSON data packets.
2.5. Topology
  • Execution Semantics: Orchestrates the flow of AI_TASK, LOGIC_GATE, and HITL (Human Approval).
  • State Machine Suspension: Natively supports pausing workflows at critical points, waiting for experts via Runly Me.
2.6. Commerce
  • Automated Settlement: Built-in pricing models and Royalty Share ratios for real-time settlement.
2.7. Security
  • Tamper-Proofing: Integrates Ed25519 digital signatures; any micro-tampering will cause verification to fail.

​
3. Why Choose Runly Protocol?

FeatureTraditional AI DevelopmentRunly Protocol (RSS)
Logic StabilityHighly prompt-dependent; prone to hallucinations.Enforced by Logical Gates and Strong-Typed Schemas.
Integration CostMassive boilerplate for model/API adaptation.Standardized SDK; Plug-and-Play assets.
Human ValidationManual development of approval backends.Native HITL suspension and breakpoints.
MonetizationDifficult to price “code fragments.”Built-in Royalty logic; Pay-per-invocation.

​
4. Developer Integration Guide (Step-by-Step)

Step 1: Init Use CLI to create a template following the 7-domain standard. 
runly-cli init expert_logic
Step 2: Orchestrate Declare skill references and task flows in the .runly file. 
skills:
  - id: "market_api"
    config: { endpoint: "https://api.data.com" }

topology:
  nodes:
    - id: "analyze"
      type: "AI_TASK"
      on_success: "expert_gate"
    - id: "expert_gate"
      type: "HITL"
Step 3: Build Sign the asset using the expert’s private key. 
runly-cli build expert_logic.runly
# Output solidified asset: dist.runly
Step 4: Deploy Push to the Hub or invoke via SDK. 
runly-cli publish dist.runly

​
5. Communication Protocol: RSS Message (Packet Standard)

​
5.1. Request Packet

{
  "header": {
    "protocol_version": "v1.1",
    "trace_id": "req-8899-001",
    "timestamp": 1738746029
  },
  "asset": {
    "urn": "urn:runly:ecommerce:analyzer:v1",
    "signature": "ed25519:sig_data..."
  },
  "payload": {
    "current_node": "expert_gate",
    "state_data": { 
        "action": "RESUME", 
        "input_override": { "decision": "APPROVED" } 
    }, 
    "global_inputs": { "target_asin": "B08N5KXXXX" } 
  }
}

​
5.2. Response Packet

{
  "header": { "trace_id": "req-8899-001" },
  "status": {
    "code": 202,
    "state": "SUSPENDED",
    "node_id": "expert_gate",
    "message": "Awaiting expert authorization."
  },
  "result": {
    "artifacts": { "report_url": "https://cdn.runly.net/a/x8y2.html" }
  }
}

​
6. Developer Ecosystem & Support

  • Runly Hub: Online visual protocol editor and asset repository for version management.
  • Runly Executor: Lightweight, high-performance logic engine for cloud and edge deployment.
  • Runly Me: Expert digital identity terminal for receiving HITL notifications and making signing decisions.

​
7. Glossary

TermDescriptionBusiness Value
MeIDDigital ID for ExpertsEnsures assets are accurately attributed to the creator.
HITL”Human-in-the-Loop”Prevents AI drift in high-value decisions with expert backing.
Artifact”Digital Product”The final deliverable (PDF, HTML, or JSON) for the client.
Royalty”Logic Royalties”Protects creators with automated, real-time revenue sharing.
Snapshot”Execution Snapshot”Saves state during suspension for seamless cross-device resumes.