Wire graduated trust posture fields into newly authored agent rules.
npx skills add https://github.com/FFOO6866/lead2cash --skill 32-trust-posture
Please help me install this Agent Skill. Skill: 32-trust-posture Source: https://github.com/FFOO6866/lead2cash/tree/main/.claude/skills/32-trust-posture Command: npx skills add https://github.com/FFOO6866/lead2cash --skill 32-trust-posture
This Skill prevents newly authored rules from shipping without the required “graduated trust posture” wiring, which can leave enforcement uninstrumented and allow risky actions to proceed without correct detection, grace periods, and downgrade logic.
Add a “## Trust Posture Wiring” section to every new rule proposal produced by /codify, following the format in rule-authoring-checklist.md and including severity, grace period, cumulative threshold, regression-within-grace policy, receipt requirement, and detection mechanism.
High-intent search queries and answers about installing and using this skill.
To enforce a graduated trust posture for agent rules, you must wire severity, grace periods, thresholds, receipt requirements, and detection mechanisms into each rule proposal to ensure safe enforcement and correct downgrade logic.
A pending_verification grace window is a lifecycle period where newly codified agent rules are monitored before promotion, allowing emergency-downgrade triggers and rollback expectations to validate safe enforcement behavior.
You add trust posture wiring by inserting a dedicated section into codify rule proposals, documenting severity, cumulative thresholds, regression-within-grace policy, receipt requirements, and detection mechanisms following the authoring checklist format.
Newly codified rules ship without correct detection and downgrade logic when they lack canonical trust posture wiring, leaving enforcement uninstrumented and allowing risky agent actions to bypass required grace periods.
Trust posture wiring works with redteam auditing and implement workflows by aligning rule metadata with SessionStart behavior and posture-gate logic to interpret and enforce L1 through L5 constraints correctly.
Enforcing agent rules without posture-gate receipts limits instrumentation visibility, preventing the system from tracking pending_verification states, applying emergency downgrades, or validating cumulative threshold regressions during the grace period.
terrene-foundationWire authored rules into L1–L5 trust posture with grace-period lifecycle handling.
Mohammed-AbdelhadyAutomate code review and security scans for Hyperflow workflows.
ssdiwuApply an L1 to L5 evidence-level framework to verification workflows.
Habitat-ThinkingDesign enforcement-ready constraints with rule text, enforcement type, tool mapping, and scope metadata.
