Documentation Index
Fetch the complete documentation index at: https://docs.skrmir.com/llms.txt
Use this file to discover all available pages before exploring further.
Environment Model: Dev/Test/Preview/Prod
Audience
This page is for maintainers and operators who need to design permissions, approvals, release flows, and environment isolation.Goal and Scope
This page explains the semantic differences between the default four environments and why production guardrails differ from the others.Core Concepts
Dev
- optimized for day-to-day development
- prioritizes fast iteration
- some mutations may execute directly under RBAC
Test
- optimized for integration and automation validation
- still prioritizes feedback speed
- usually stricter than Dev, but not necessarily prod-style approval
Preview
- optimized for pre-release validation
- closer to production configuration
- more restrictive than Dev/Test by default
Prod
- handles formal business traffic
- high-risk mutations default to
require_approval - approval, audit, and rollback chains must remain complete
Standard Workflow
Non-prod
AuthN -> AuthZ(allow/deny) -> Execute -> Audit
High-risk prod mutations
AuthN -> AuthZ(require_approval) -> Approval -> ValidateBinding -> Execute -> Audit
Planned CLI Examples (Not Yet Implemented)
The repository does not currently ship these environment-targeting CLI commands. They remain examples of how guardrails differ across environments.Web UI Path
- environment selector
- application detail environment context
- production approval tickets in the approval center
Pitfalls / Risk Notes
- Preview is not just “simplified prod”; it is its own policy layer.
- production rollback should still follow the same guardrail chain by default.