Use when changing IAM, consent scopes, actor model, verification policy, or marketplace access contracts inside the security-audit owner family.
Recursos
2Instal·la
npx skillscat add hushh-labs/hushh-research/iam-consent-governance Instal·la des del registre de SkillsCat.
SKILL.md
Hussh IAM Consent Governance Skill
Purpose and Trigger
- Primary scope:
iam-consent-governance - Trigger on IAM, consent scopes, actor model, verification policy, or marketplace access contract changes.
- Avoid overlap with
security-auditandquality-contracts.
Coverage and Ownership
- Role:
spoke - Owner family:
security-audit
Owned repo surfaces:
docs/reference/iamconsent-protocol/api/routes/iam.pyconsent-protocol/api/routes/consent.pyhushh-webapp/lib/consenthushh-webapp/components/consent
Non-owned surfaces:
security-auditbackenddocs-governance
Do Use
- Consent-scope, actor-model, and verification-gate changes.
- IAM runtime surface and marketplace access contract work.
- IAM docs and code alignment across frontend and backend.
- Opaque object-share references that must remain separate from
attr.*scopes.
Do Not Use
- Broad security intake where the correct spoke is still unclear.
- Vault and PKM storage or encryption-boundary work.
- Generic backend runtime or deploy work.
Read First
docs/reference/iam/README.mddocs/reference/iam/architecture.mddocs/reference/iam/consent-scope-catalog.mddocs/reference/iam/agent-delegation-boundary.mddocs/reference/iam/validation-checklist.md.codex/skills/iam-consent-governance/references/anti-rationalization.md
Workflow
- Confirm whether the change is about actor model, scope catalog, verification gate, or runtime surface.
- Keep IAM docs, code, and validation checklists aligned in the same change.
- Treat vault and PKM boundary questions as
security-auditwork when they become primary. - Reject every Source Library
attr.*form; a local share row is mapping state, not access or revocation authority.
Handoff Rules
- If the request is still broad or ambiguous, route it back to
security-audit. - If the task becomes vault or PKM storage-boundary work, use
security-audit. - If the task becomes general backend runtime work, route it to
backend.
Required Checks
cd consent-protocol && python3 -m pytest tests/test_granular_scopes.py -q
cd consent-protocol && python3 -m pytest tests/test_ria_iam_routes.py -q
cd consent-protocol && python3 -m pytest tests/test_source_library_scope_policy.py -q