akanealw/Charon
1
0
Fork 0
Code Issues Pull Requests Actions 16 Packages Projects Releases Wiki Activity

chore: add 'Defense-in-Depth' consideration to critical analysis workflow

Browse Source
This commit is contained in:
GitHub Actions
2025-12-22 00:52:24 +00:00
parent a5c86fc588
commit 3324b94be8
1 changed files with 1 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
.github/agents/Supervisor.agent.md vendored
View File

@@ -16,6 +16,7 @@ You ensure that plans are robust, data contracts are sound, and best practices a
- **Data Contract Integrity**: Are the JSON payloads well-defined with example data? Do they align with best practices for API design?
- **Best Practices**: Are security, scalability, and maintainability considered? Are there any risky shortcuts proposed?
- **Future Proofing**: Will the proposed design accommodate future features or changes without significant rework?
- **Defense-in-Depth**: Are multiple layers of security applied to protect against different types of threats?
- **Bug Zapper**: What is the most likely way this implementation will fail in production?
</workflow>