blacktrigram

Enforces systematic threat modeling for Black Trigram using STRIDE, MITRE ATT&CK, and attack trees — maintains THREAT_MODEL.md and FUTURE_THREAT_MODEL.md aligned with Hack23 Threat Modeling Policy and Secure Development Policy §3.2

Enforces C4 Architecture Model documentation standards for Black Trigram. Ensures ARCHITECTURE.md, DATA_MODEL.md, FLOWCHART.md, STATEDIAGRAM.md, MINDMAP.md, SWOT.md and their FUTURE_* variants are maintained with strategic, rule-based principles.

Enforces WCAG 2.1 Level AA accessibility for Black Trigram — semantic HTML, ARIA, keyboard navigation, 4.5:1/3:1 contrast, screen reader support, and prefers-reduced-motion for inclusive Korean martial arts gameplay

Enforces AI governance for Black Trigram — transparent and accountable AI-assisted development aligned with Hack23 AI Governance Policy, EU AI Act, NIST AI RMF, and Information Security Policy

Enforces code quality standards for Black Trigram — maintainable, type-safe TypeScript with low complexity, organized imports, explicit error handling, and search-before-create discipline

Enforces data protection at every stage of its lifecycle for Black Trigram — classification, HTTPS/TLS 1.2+, CSP, SRI, minimal retention, aligned with Hack23 Data Classification Policy and GDPR Articles 5, 25, 32

Enforces consistent documentation standards for Black Trigram — JSDoc/TSDoc completeness, architecture currency, bilingual Korean-English content, and security documentation updates

Enforces GDPR, NIS2, and EU Cyber Resilience Act requirements for Black Trigram — data minimization, explicit consent, right-to-erasure, privacy by design, and Hack23 Data Classification Policy alignment

Enforces security incident response procedures for Black Trigram aligned with Hack23 Incident Response Plan — severity classification, SLA-based remediation, secret rotation, lessons learned, and automated detection

Enforces input validation at all system boundaries for Black Trigram — type, length, format, range checks; Zod/type guards; safe output encoding; aligned with OWASP A03:2021 and Hack23 Secure Development Policy §3.3

Enforces Hack23 Open Source Policy for Black Trigram — license compatibility, OSSF Scorecard evidence, SBOM/SLSA provenance, security posture badges, vulnerability disclosure, and community-aligned open source contribution discipline

Enforces systematic risk identification, evaluation, and treatment for Black Trigram — aligned with ISO 31000, ISO 27001 6.1/6.2, NIST CSF ID.RA, and Hack23 Information Security Policy

Enforces secure handling of API keys, tokens, and credentials for Black Trigram — no hardcoded secrets, GitHub Secrets for CI/CD, rotation SLAs, aligned with OWASP A02:2021 and Hack23 Cryptography Policy

Enforces maximum TypeScript type safety for Black Trigram — strict mode, no 'any', readonly by default, exhaustive pattern matching, explicit return types for compile-time error detection

Enforces continuous vulnerability identification, assessment, and remediation for Black Trigram — Dependabot, npm audit, CodeQL, SLA-based patching, OSSF Scorecard ≥8.0, CycloneDX SBOM, aligned with Hack23 Vulnerability Management policy

Enforces GitHub Agentic Workflows (gh-aw) best practices: workflow structure, frontmatter, safe outputs, MCP integration, defense-in-depth security, operational patterns, multi-engine support, and Continuous AI automation.

Enforces comprehensive Secure Development Lifecycle (SDLC) practices for Black Trigram, implementing all phases from requirements to retirement with DevSecOps automation, secure coding standards (OWASP Top 10, CWE Top 25), supply chain security (OSSF/SLSA), and continuous security integration following Hack23 ISMS Secure_Development_Policy.md.

Enforces Hack23 ISMS classification framework for security levels (Confidentiality, Integrity, Availability, Privacy/PII), business impact analysis (Financial, Operational, Reputational, Regulatory), recovery time objectives (RTO/RPO), and project type classifications. Validates proper classification and implements defense-in-depth strategies for Black Trigram following CLASSIFICATION.md methodology.

Validates all code changes against Hack23 ISMS policies, enforces ISO 27001:2022, NIST CSF 2.0, CIS Controls v8.1 alignment, ensures GDPR/NIS2/EU CRA compliance, supply chain security (OSSF Scorecard, SLSA, SBOM), and maintains required architecture documentation for Black Trigram.

Enforces authentic Korean martial arts systems (Hapkido, Taekwondo, Taekyon, Kuk Sool Won, Tang Soo Do, Hwa Rang Do, Gumdo, Ssireum, Subak, Yudo, Gongkwon Yusul) with Eight Trigram stances, 70 vital points, Dark Ops combat applications, special forces integration, cultural respect, anatomical precision, and realistic combat mechanics for Black Trigram.

Enforces unified compliance across ISO 27001:2022, NIST CSF 2.0, and CIS Controls v8.1. Validates framework alignment, control mapping, and evidence documentation for Black Trigram following Hack23 ISMS compliance methodology from Compliance_Checklist.md.

Enforces 3D physics-based combat patterns for Black Trigram including Rapier physics, collision detection, attack/defense mechanics, damage calculations, hitbox accuracy, and realistic Korean martial arts combat in Three.js environments.

Enforces audio best practices for Black Trigram including Howler.js patterns, spatial 3D audio with PositionalAudio, performance optimization, combat audio feedback, Korean-themed soundscapes, and proper audio resource management.

Enforces game development best practices for Black Trigram including game loop patterns, state management, combat system architecture, animation timing, deterministic physics, and 60fps performance targets for Korean martial arts combat gameplay.

Enforces @react-three/fiber and @react-three/drei best practices for Black Trigram, including proper Canvas setup, Korean-themed lighting, resource cleanup patterns, Html overlay vs 3D mesh decision guide, performance optimization (useFrame, useMemo), testing patterns, and common Three.js anti-patterns to avoid.

Enforces comprehensive testing standards for Black Trigram including >90% coverage, unit tests (Vitest), E2E tests (Cypress), Three.js component testing, performance testing (60fps target), and accessibility testing. Ensures test quality and coverage.

Enforces 60fps rendering for Three.js scenes, bundle size optimization (<500KB initial, <2MB total), Lighthouse performance score >90, memory leak prevention, efficient Three.js patterns (instancing, LOD, culling), and performance budget monitoring for Black Trigram.

Enforces Korean cyberpunk aesthetic and cultural authenticity for Black Trigram. Ensures proper Korean color palette usage, bilingual text, authentic martial arts terminology, and Eight Trigram system integration across all UI and game components.

Validates that all code changes follow Hack23 ISMS security architecture principles, ensures SECURITY_ARCHITECTURE.md and FUTURE_SECURITY_ARCHITECTURE.md are maintained, and enforces security-by-design practices across the codebase.