3.1 Control Plane vs Agent Execution Plane
3.2 Project Scope Model
3.3 Data Flow: Source -> Release -> Pipeline -> Logs/Artifacts
3.4 Runtime Configuration Layers (global / project / environment)
3.5 Pipeline Execution Semantics
3.6 Release Governance Path
3.7 Rollback Architecture (Policy-driven)
3.8 Security and Trust Boundaries
3.9 State and Persistence Model
3.10 Scalability Model
3.11 Failure Modes and Recovery Patterns
3.12 Why This Architecture Works in Practice
10.5 Templates, Actions, Functions
Orbnetes deployment and release orchestration documentation for operators and platform teams.
Blueprint editor includes helper panels to speed authoring.
Templates
Prebuilt blueprint skeletons for common flows (deploy/build patterns). Use templates as starting point, then customize tags/inputs/steps.
Actions
Reusable insertion snippets for common command patterns. Purpose: reduce repetition and avoid copy/paste drift across blueprints.
Functions
Reference snippets/documented patterns for supported platform features:
- launch inputs,
- environment-aware configuration,
- secrets/variables usage,
- conditions and dependency controls.
Practical recommendation:
- start with template,
- insert action snippets,
- refine with function references,
- validate before first run.