Skip to main content
# =============================================================
# 1. MANIFEST (Protocol Identity Card)
# Rights Confirmation, Version Management, and Global Unique Identification
# =============================================================
manifest:
  urn: "urn:runly:ecommerce:amazon:selection-expert:v1.0.0"
  title: "ACME Amazon Selection Expert"
  description: "Standard SOP for deep product selection decision-making based on AI-driven business scenarios."
  version: "1.0.0"
  status: "stable"
  creator:
    me_id: "me_arch_dow_001"
    name: "Solo Arch Lab"
    pub_key: "ed25519:0x8e5c...a12b"
  created_at: "2026-02-07T10:00:00Z"
  updated_at: "2026-02-07T22:00:00Z"
  min_runtime: "v1.0"

​
1. Parameter Fields

ParameterRequiredTypeDescription
urnYesStringUniform Resource Name. Standard format: urn:runly:[domain]:[category]:[asset_name]:[version].
titleYesStringProtocol Name. Used for display in user interfaces (e.g., Runly Me).
descriptionNoStringDetailed Description. Explains the specific business logic and expected outcomes of the SOP.
versionYesStringSemantic Versioning (SemVer). E.g., 1.0.2. Follows Major.Minor.Patch.
statusNoEnumAsset Status. Standard values: draft, stable, deprecated.
creatorYesObjectCreator Information. The legal basis for rights confirmation and revenue sharing.
created_atNoISO8601Creation Time. Format: YYYY-MM-DDTHH:MM:SSZ.
updated_atYesISO8601Last Update Time. Must be updated every time the protocol is re-signed and published.
min_runtimeYesStringMinimum Runtime Version. Declares the minimum Executor version required (e.g., v1.0).

​
2. Creator

The Creator field is the core anchor for the protocol to achieve the “Capitalization of Expert Experience.”
  • me_id: The expert’s globally unique identity ID (Runly Me ID).
  • name: The display name of the creator or organization.
  • pub_key: Public Key for Digital Signature Verification.
    • Specification: Must be a public key based on the Ed25519 algorithm.
    • Function: The execution engine extracts this key to verify the signature in the Security field at the end of the file. If the public key does not match the signature, the asset will be locked.

​
3. URN Naming Convention Example

To ensure asset interoperability within the ecosystem, the URN must follow a hierarchical structure: urn:runly:ecommerce:amazon:selection-expert:v1
  • runly: Protocol scheme.
  • ecommerce: Major business category.
  • amazon: Specific vertical field.
  • selection-expert: Logical name of the asset.
  • v1: Major version identifier.