CAPH TECH
Official@caphtech · Japan
Offers rigorous Evidence-Loop Development frameworks for technical governance, requirement traceability, and systematic failure-mode observation in complex software engineering environments.
Agent Skills by CAPH TECH
Showing 53 vetted skills indexed across 1 GitHub repositories.
CAPHTECHuncertainty-to-law
Convert validated hypotheses into enforceable laws with structured Law Card drafts.
CAPHTECHeld
Enforce an Evidence-Loop Development workflow with Sense/Model/Predict/Change/Ground/Record phases.
CAPHTECHeld-sense-scope
Define context inheritance boundaries between nested parent and child processes.
CAPHTECHeld-ground-check
Verify Law and Term grounding against S0–S3 verification and observability criteria.
CAPHTECHspec-observation
Identify specification ambiguities and formalize acceptance criteria in Given/When/Then format.
CAPHTECHlde-model-law-card
Create Law Cards documenting business conditions in a standard format.
CAPHTECHeld-model-link-map
Manage Law-to-Term cross-reference links and detect orphaned artifacts.
CAPHTECHeld-ground-evaluate
Evaluate generated code outputs for Law compliance and quality.
CAPHTECHeld-sense-activation
Construct an optimized active_context YAML with goal, constraints, references, and expected_output.
CAPHTECHeld-ground-pr-review
Automate PR reviews with Compile-Execute-Capture flow and LDE compliance checks.
CAPHTECHeld-record-compact
Compress long-running session histories into compact, searchable notes with decision traces.
CAPHTECHlde-model-term-card
Create standardized Term Cards for LDE domain vocabulary.
CAPHTECHknowledge-validator
Validate knowledge integrity across documents using pce-memory and shirushi.
CAPHTECHeld-model-law-discovery
Discover vocabulary terms and law constraints from codebases and requirements.
CAPHTECHeld-record-memory-collector
Collect and verify project information from codebases using multi-model validation.
CAPHTECHobservation-minimum-set
Define a minimal set of diagnostic and verification practices covering six failure modes.
CAPHTECHconcurrency-observation
Detect data races, deadlocks, and timing-dependent bugs in concurrent programs.
CAPHTECHoperability-observation
Implement structured logging, health checks, metrics, and configuration validation.
CAPHTECHsecurity-observation
Identify security defects in generated code to prevent data leakage and injection attacks.
CAPHTECHtechnical-book-writer
Standardize technical book writing with chapter templates and code validation scripts.
CAPHTECHapp-idea-workshop
Guide ideation through structured interviews and generate product documentation.
CAPHTECHboundary-observation
Test boundary conditions across input space to reveal edge-case defects.
CAPHTECHdependency-observation
Detect dependency misalignment between lockfiles and installed dependencies.
CAPHTECHrefactoring-executor
Execute prioritized refactoring steps with test-first verification in TypeScript projects.
Frequently Asked Questions About CAPH TECH
FAQPage SchemaWhat specific engineering tasks are enabled by these methodologies?▼
These methodologies enable structured project decomposition, automated pull request reviews, and rigorous validation of code against business invariants. They facilitate the creation of Evidence Packs, Law Cards, and Term Cards to ensure consistency across documentation, requirements, and implementation artifacts.
Which personas benefit most from these technical practices?▼
Senior software engineers, technical architects, and compliance officers benefit from these practices. They are designed for teams managing high-complexity codebases who require strict traceability, formal acceptance criteria, and systematic observation of failure modes to maintain system integrity.
What are the primary prerequisites for implementing these practices?▼
Implementation requires a commitment to the Evidence-Loop Development discipline, which involves defining clear context boundaries and maintaining structured project memory. Users must adopt the provided YAML and Markdown schemas for Law Cards, Term Cards, and active context definitions to ensure compatibility.