semantic-matrix-build

Derive eight semantic matrices from canonical A and B matrices into _SEMANTIC.md.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/sgttomas/chirality-piping --skill semantic-matrix-build
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: semantic-matrix-build
Source: https://github.com/sgttomas/chirality-piping/tree/main/skills/semantic-matrix-build
Command: npx skills add https://github.com/sgttomas/chirality-piping --skill semantic-matrix-build

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Derives a deliverable-local semantic lens by applying canonical matrices and generating eight semantic matrices to capture the knowledge structure around a deliverable, enabling consistent reasoning and audit-ready outputs without embedding project specifics.

Core Features & Use Cases

  • Canonical A/B adoption: read-only reference matrices and deterministic derivation to C, F, D, K, G, X, T, E.
  • Deliverable-local outputs: produces a single _SEMANTIC.md per run that encodes the semantic lens and provenance for auditing.
  • Variant-aware operation: supports PROJECT, SOFTWARE, and DOMAIN decomposition variants for different production documents and terminology.

Quick Start

Provide the deliverable folder path and the decomposition_path to generate the deliverable-local semantic lens.

Frequently Asked Questions about semantic-matrix-build

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a semantic lens for a specific deliverable?

To generate a semantic lens, provide the deliverable folder path and decomposition variant. The tool reads context and production documents, applies canonical A and B matrices, and outputs a _SEMANTIC.md file.

What is canonical matrix decomposition for knowledge structure auditing?

Canonical matrix decomposition derives eight semantic matrices from read-only A and B references to capture a deliverable's knowledge structure. This process ensures consistent reasoning and audit-ready outputs without embedding project specifics.

How do I audit a deliverable's semantic structure using decomposition variants?

You audit a deliverable by running the tool with PROJECT, SOFTWARE, or DOMAIN decomposition variants. It processes your production documents and generates an updated _STATUS.md file alongside the semantic lens output.

What inputs do I need to derive semantic matrices for a deliverable?

Deriving semantic matrices requires the deliverable's _CONTEXT.md file and associated production documents. These inputs feed the canonical A/B matrix application to generate the final semantic lens.

Can I process multiple deliverables in a single semantic matrix generation run?

No, the derivation operates on a single deliverable per run. You must provide a specific deliverable folder path and decomposition path to generate each localized _SEMANTIC.md output.

Why use canonical matrices instead of manual semantic mapping?

Canonical matrices provide deterministic derivation to eight semantic matrices, ensuring audit-ready provenance and consistent reasoning. Manual mapping lacks this standardized structural capture across PROJECT, SOFTWARE, and DOMAIN variants.