Active specifications
Rune Engine and other developer-facing contracts are exposed primarily through the active public Spec set.
How to read spec status
- Accepted means the project has adopted the document as its current standard.
- Proposed means the document is public for review but should not be read as a blanket product stability promise.
For this first public documentation release, that distinction matters: Story is the current runnable beta. Read the Engine system guides for the cross-cutting mental model, then use these Specs for exact contracts and edge cases.
Standards and architecture
| Spec | Status | Focus |
|---|---|---|
| RUNE-001 | Accepted | Spec structure, source authority, and audit rules |
| RUNE-002 | Proposed | Overall project architecture and managed-to-native render flow |
| RUNE-003 | Proposed | Project, Engine, and Story identity assets and usage rules |
Engine core
| Spec | Status | Focus |
|---|---|---|
| RUNE-300 | Proposed | C ABI, handles, context submission, and thin C# wrappers |
| RUNE-301 | Proposed | Static, animated, derived, and sampled value representation |
| RUNE-302 | Proposed | Analytical animation curves and render-thread evaluation |
| RUNE-303 | Proposed | Mutable node state, immutable snapshots, commit, and submission |
| RUNE-304 | Proposed | Command stream, data arena, paths, fills, strokes, and trim |
| RUNE-305 | Proposed | Full-target traversal, child composition, opacity, and Layer 3D |
| RUNE-306 | Proposed | Current shaping metrics and managed layout responsibilities |
| RUNE-308 | Proposed | Global resources, slot resources, and snapshot lifetime rules |
Story
| Spec | Status | Focus |
|---|---|---|
| RUNE-1000 | Proposed | .story.yaml, .sprite.yaml, and local HLSL type rules |
| RUNE-1001 | Proposed | Action ordering, binding, waits, and execution model |
| RUNE-1002 | Proposed | Layout solving, arrange, and current row/column limits |
| RUNE-1003 | Proposed | morph semantics and identity preservation |
| RUNE-1004 | Proposed | Shared-sprite transition behavior |
| RUNE-1010 | Proposed | Composite sprite reuse and .sprite.yaml construction |
| RUNE-1011 | Proposed | Story render tracks and playback as export video sources |
| RUNE-1012 | Proposed | StoryExportRequest and export orchestration |
| RUNE-1013 | Proposed | AI-native editor model and Story-as-source-of-truth |
| RUNE-1014 | Proposed | Layer sprite tree behavior and root-layer composition |
| RUNE-1015 | Proposed | motion actions along inline static paths |
| RUNE-1016 | Proposed | Path stroke trimming and animation |
| RUNE-1017 | Proposed | Planar Layer 3D transforms for non-root layers |
Media
| Spec | Status | Focus |
|---|---|---|
| RUNE-2000 | Proposed | FFmpeg backend boundaries and migration shims |
| RUNE-2001 | Proposed | Encoder pull model and export orchestration |
| RUNE-2002 | Proposed | Audio export source replacement with track-based orchestration |
| RUNE-2003 | Proposed | FFmpeg audio decoding and encoding surface |
What is intentionally not here
docs/archived/remains historical project material and is excluded from the public site.knowledge/remains internal AI/design source material rather than published site content.