Classify artifacts as durable vs transient by their functional role rather than directory path, using multi-layer architectural validation
Scanned 9/9/2026
Install to Claude Code
npx -y skills add vamseeachanta/workspace-hub --skill boundary-policy-classification-by-role --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Boundary Policy Classification By Role?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/vamseeachanta-boundary-policy-classification-by-role)More formats (shields.io, HTML) on the badges page.
---
name: boundary-policy-classification-by-role
description: Classify artifacts as durable vs transient by their functional role rather than directory path, using multi-layer architectural validation
version: 1.0.0
source: auto-extracted
extracted: 2026-04-11
metadata:
tags: ["architecture", "policy-design", "classification", "artifact-management"]
---
# Boundary Policy Classification by Role
When defining durable vs transient artifact boundaries within a multi-layer architecture, classify by *role* not *path*. Same directory can contain both types (e.g., reports/ has one-shot audits and durable assessments). Ground classification in concrete examples from each layer, validate consistency with parent architecture, and use adversarial review to test for loose language ('it depends') and implementability gaps.Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Ultra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. Use when user says "write a commit", "commit message", "generate commit", "/commit", or invokes /caveman-commit. Auto-triggers when staging changes.