Hidden dependency and assumption detector. Surfaces things the system depends on that aren't explicit — environment variables, implicit service dependencies, timing assumptions, undocumented contracts. The things that break at 2am.
Detect LA drift in geometric algebra code. Scan for scalar-only returns, missing grade-2 components, and notation that hides structure. The code guard for GA discipline.
Grammar layer system health check for v3. Assesses PCFG weight distribution entropy, pre-embedder accuracy status, evolutionary macro library utilization, RTG coverage, and layer dependency integrity. Use weekly during search or after any grammar layer change.
Production hardening checklist derived from the actual stack. HTTP headers, dependency scanning, secret management, input validation, error handling, CSP, CORS. Not a generic OWASP list — reasoned from the specific architecture. Use before deployment, after adding external integrations, or at phase boundaries.
Identifier integrity audit. Checks finding IDs (F-VN-NNN), FTR IDs, and other identifier systems for uniqueness, formatting, sequence gaps, and cross-reference validity. Catches duplicates, orphans, and broken references.
Design-to-code specification. Given a deliverable or FTR, produce a concrete implementation plan with file paths, function signatures, SQL migrations, config constants, and test specifications. The bridge from architecture to code.
Incident response readiness evaluation. Assesses runbook coverage, escalation paths, severity classification, communication templates, rollback procedures, and post-incident review process. Use when transitioning from development to production, at phase boundaries, or after a real incident exposes gaps.
Whole-project awareness. Reads every architectural doc, source file, test, and research synthesis into context using the full 1M token window. Use at session start when broad project understanding is needed, or when context has drifted.
Systematic assumption flipping. For every key decision, invert it and examine what emerges. A creativity and stress-testing tool — not to change direction, but to verify that choices are load-bearing rather than habitual.
Pre-launch production readiness gate. Comprehensive go/no-go checklist covering SLAs, monitoring, backups, load testing, security, accessibility, legal, rollback, and runbook completeness. Runs at any phase boundary — not just final launch. Use when asking "are we ready to ship this phase?".