Scene Runtime Guide

Complete guide to sce Scene features: Template Engine, Quality Pipeline, Ontology, and Moqui ERP Integration

Version: 1.42.0
Last Updated: 2026-02-11

Overview

The sce Scene Runtime is a suite of features for building, validating, scoring, and analyzing reusable scene template packages. Scene packages describe business capabilities (e.g., ERP inventory management) as structured templates that AI agents can understand and instantiate.

Feature Timeline

Version	Feature	Description
v1.25.0	Scene Template Engine	Variable schema, multi-file rendering, three-layer inheritance
v1.39.0	Moqui ERP Adapter	Connect to Moqui ERP instances, entity CRUD, service invocation
v1.40.0	Moqui Template Extractor	Analyze Moqui resources, generate scene templates
v1.41.0	Quality Pipeline	Lint engine, quality scoring, contribute pipeline
v1.42.0	Ontology Enhancement	Semantic graph, action abstraction, data lineage, agent hints

Scene Template Engine (v1.25.0)

Variable Schema

Define typed variables in scene-package.json:

{
  "variables": {
    "entity_name": {
      "type": "string",
      "required": true,
      "description": "Primary entity name"
    },
    "enable_audit": {
      "type": "boolean",
      "default": false
    },
    "db_type": {
      "type": "enum",
      "values": ["mysql", "postgres", "moqui"],
      "default": "postgres"
    }
  }
}

Supported types: string, number, boolean, enum, array.

Multi-File Rendering

Templates support Handlebars-style syntax:

{{variable}} — Variable substitution
{{#if condition}}...{{/if}} — Conditional blocks
{{#each items}}...{{/each}} — Loop blocks

Three-Layer Inheritance

L1-Capability (base)     → e.g., scene-crud-base
  └─ L2-Domain (domain)  → e.g., scene-erp-inventory
       └─ L3-Instance    → e.g., scene-erp-inventory-order

Each layer can extend the parent's variable schema and template files. The template-resolve command shows the merged result.

CLI Commands

# Validate variable schema
sce scene template-validate --package <path>
sce scene template-validate --package ./my-package --json

# Resolve inheritance chain
sce scene template-resolve --package <name>
sce scene template-resolve --package scene-erp-inventory --json

# Render templates with variable values
sce scene template-render --package <name> --values <json-or-path> --out <dir>
sce scene template-render --package scene-erp --values '{"entity_name":"Order"}' --out ./output --json

Moqui ERP Integration (v1.39.0 ~ v1.40.0)

Architecture

MoquiClient (HTTP + JWT auth)
    └─ MoquiAdapter (binding handler for spec.erp.* / moqui.* refs)
         └─ MoquiExtractor (analyze resources → generate templates)

MoquiClient

HTTP client with JWT authentication lifecycle:

Login / refresh / re-login / logout
Automatic token refresh on expiry
Configurable retry logic

MoquiAdapter

Binding handler that resolves spec.erp.* and moqui.* references:

Entity CRUD operations
Service invocation
Screen discovery

MoquiExtractor (v1.40.0)

Analyzes Moqui ERP resources and generates reusable scene templates:

Entity grouping by Header/Item suffix patterns (e.g., OrderHeader + OrderItem → composite)
Pattern-based manifest generation with governance contracts
Dry-run mode for preview

CLI Commands

# Test connectivity
sce scene connect --config <path>
sce scene connect --config ./moqui-config.json --json

# Discover entities, services, screens
sce scene discover --config <path>
sce scene discover --config ./moqui-config.json --type entities --json

# Extract scene templates
sce scene extract --config <path> --out <dir>
sce scene extract --config ./moqui-config.json --type entities --pattern crud --out ./templates --json
sce scene extract --config ./moqui-config.json --dry-run --json

Configuration File

{
  "baseUrl": "https://moqui.example.com",
  "username": "admin",
  "password": "secret",
  "tenant": "DEFAULT"
}

Quality Pipeline (v1.41.0 ~ v1.42.0)

Lint Engine

10-category quality checks:

#	Category	Description
1	Manifest Completeness	Required fields in scene-package.json and scene.yaml
2	Binding Refs	Valid ref prefixes and format
3	Governance Contract	Risk levels, approval rules, audit requirements
4	Consistency	Cross-file consistency between package and manifest
5	Variables	Variable schema validity and usage
6	Documentation	README, descriptions, examples
7	Naming Conventions	kebab-case names, semver versions
8	Action Abstraction	Intent, preconditions, postconditions per binding (v1.42.0)
9	Data Lineage	Source → transform → sink tracking (v1.42.0)
10	Agent Hints	Agent-ready metadata completeness (v1.42.0)

Quality Score

4 base dimensions + 1 bonus dimension:

Dimension	Weight	Description
Contract Validity	30	scene-package.json and scene.yaml structure
Lint Pass Rate	30	Percentage of lint checks passed
Documentation Quality	20	README, descriptions, examples
Governance Completeness	20	Risk levels, approval, audit
Agent Readiness (bonus)	+10 max	Action abstraction + data lineage + agent hints

Total possible score: 110 (100 base + 10 bonus).

Contribute Pipeline

One-stop workflow: validate → lint → score → preview → publish.

# Full pipeline
sce scene contribute --package <path>

# With registry target
sce scene contribute --package ./my-package --registry ./registry --json

# Dry-run (preview only)
sce scene contribute --package ./my-package --dry-run

# Skip lint step
sce scene contribute --package ./my-package --skip-lint --json

CLI Commands

# Lint
sce scene lint --package <path>
sce scene lint --package ./my-package --json
sce scene lint --package ./my-package --strict

# Score
sce scene score --package <path>
sce scene score --package ./my-package --json
sce scene score --package ./my-package --strict

Ontology Enhancement (v1.42.0)

OntologyGraph

A semantic relationship graph built from scene manifest bindings:

Node: binding ref (e.g., "entity:Order", "service:createOrder")
Edge: relationship (depends_on, composes, extends, produces)

Relationship Types

Type	Meaning	Example
`depends_on`	Requires another node	service:createOrder → entity:Order
`composes`	Contains/aggregates	entity:OrderHeader → entity:OrderItem
`extends`	Inherits from	entity:PurchaseOrder → entity:Order
`produces`	Outputs/creates	service:processOrder → entity:Invoice

Action Abstraction

Each binding can declare:

intent — What the action does
preconditions — What must be true before execution
postconditions — What will be true after execution

This enables AI agents to reason about operations before executing them.

Data Lineage

Track data flow through the system:

source → transform → sink

Defined in governance_contract.data_lineage:

{
  "data_lineage": [
    {
      "source": "entity:OrderHeader",
      "transform": "service:calculateTotal",
      "sink": "entity:OrderSummary"
    }
  ]
}

Impact & Path Queries

Use ontology as an operational graph, not just static visualization:

impact: reverse-traverse matching relations to estimate blast radius from one changed ref
path: find the shortest relation path between two refs for dependency explainability

Agent Hints

The agent_hints field provides metadata for autonomous AI operation:

{
  "agent_hints": {
    "summary": "CRUD operations for Order entity",
    "complexity": "medium",
    "estimated_duration": "5min",
    "required_permissions": ["entity:Order:read", "entity:Order:write"],
    "recommended_sequence": ["createOrder", "addItems", "calculateTotal"]
  }
}

Agent Readiness Score

Quality scoring bonus dimension (max +10 points) based on:

Action abstraction completeness
Data lineage coverage
Agent hints presence and quality

CLI Commands

# Show ontology graph
sce scene ontology show --package <path>
sce scene ontology show --package ./my-package --json

# Query dependency chain
sce scene ontology deps --package <path> --ref <node-ref>
sce scene ontology deps --package ./my-package --ref entity:Order --json

# Query reverse impact radius
sce scene ontology impact --package <path> --ref <node-ref>
sce scene ontology impact --package ./my-package --ref service:createOrder --relation depends_on,composes --max-depth 2 --json

# Query shortest relation path between two refs
sce scene ontology path --package <path> --from <source-ref> --to <target-ref>
sce scene ontology path --package ./my-package --from service:createOrder --to entity:Order --undirected --json

# Validate graph (dangling edges, cycles)
sce scene ontology validate --package <path>
sce scene ontology validate --package ./my-package --json

# Show action abstraction
sce scene ontology actions --package <path>
sce scene ontology actions --package ./my-package --ref service:createOrder --json

# Show data lineage
sce scene ontology lineage --package <path>
sce scene ontology lineage --package ./my-package --ref entity:Order --json

# Show agent hints
sce scene ontology agent-info --package <path>
sce scene ontology agent-info --package ./my-package --json

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Scene Runtime Guide

Overview

Feature Timeline

Scene Template Engine (v1.25.0)

Variable Schema

Multi-File Rendering

Three-Layer Inheritance

CLI Commands

Moqui ERP Integration (v1.39.0 ~ v1.40.0)

Architecture

MoquiClient

MoquiAdapter

MoquiExtractor (v1.40.0)

CLI Commands

Configuration File

Quality Pipeline (v1.41.0 ~ v1.42.0)

Lint Engine

Quality Score

Contribute Pipeline

CLI Commands

Ontology Enhancement (v1.42.0)

OntologyGraph

Relationship Types

Action Abstraction

Data Lineage

Impact & Path Queries

Agent Hints

Agent Readiness Score

CLI Commands

See Also

FilesExpand file tree

scene-runtime-guide.md

Latest commit

History

scene-runtime-guide.md

File metadata and controls

Scene Runtime Guide

Overview

Feature Timeline

Scene Template Engine (v1.25.0)

Variable Schema

Multi-File Rendering

Three-Layer Inheritance

CLI Commands

Moqui ERP Integration (v1.39.0 ~ v1.40.0)

Architecture

MoquiClient

MoquiAdapter

MoquiExtractor (v1.40.0)

CLI Commands

Configuration File

Quality Pipeline (v1.41.0 ~ v1.42.0)

Lint Engine

Quality Score

Contribute Pipeline

CLI Commands

Ontology Enhancement (v1.42.0)

OntologyGraph

Relationship Types

Action Abstraction

Data Lineage

Impact & Path Queries

Agent Hints

Agent Readiness Score

CLI Commands

See Also