[chore] add reusable standards layer#112
Merged
salazarsebas merged 1 commit intochore/new-featuresfrom Apr 4, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR completes Phase 4 of the roadmap by introducing a reusable
standardslayer for common contract controls in Cougr.It adds storage-backed, example-independent primitives for:
OwnableOwnable2StepAccessControlPausableExecutionGuardRecoveryGuardBatchExecutorDelayedExecutionPolicyWhy
Cougr already had useful ECS, account, and privacy building blocks, but it did not yet expose a cohesive standards layer for common contract ergonomics and operational controls.
This change closes that gap with explicit, composable primitives that:
SymbolidentifiersImpact
Developers building on Cougr now have a dedicated public standards surface for ownership, access control, pausability, guarded execution, recovery-aware protection, bounded batching, and delayed execution flows.
The documentation and maturity model were also updated so the new layer is described honestly as Beta and aligned with the roadmap and public API story.
Validation
cargo fmt --checkcargo test --test integration_standards -- --nocapturecargo test --test public_api_surface -- --nocapturecargo test --lib --testsCloses #101