Skip to content

transitrix/transitrix

v0.1.0MIT

Scaffold a Transitrix enterprise-architecture-as-text repository and author your first notation file with inline canonical validation. Drops the canonical zoned canon/ + field/ + codex/ layout with an assistant-neutral AGENTS.md guide and a pinned transitrix.yaml manifest, then walks the user through one of the 12 diagram views (BPMN, DGCA / DGA, Goals, Capability map, Process landscape map, Process Blueprint, Action schedule, Nested blocks, Applications, Integration map, Products, Action Card) + PlantUML rendering, one of the 6 report views (Scenarios, Actions tree, Compliance Impact, Coverage Metric, Rules in Force, Glossary), or a document view (MRD, SRS, SDD) or a codex artefact.

Transitrix Reg-Intel

Collect regulatory-source changes in practice — the operational counterpart to the methodology's codex / SEGMENT / AMENDMENT notation work. Reads the centralised watch-list at operations/config/scan-sources.yaml, runs a cheap change-signal gate before any expensive extraction, then on signal-moved runs the SCAN → SEGMENT → CLASSIFY → OUTPUT pass: fetches and snapshots the source, slices it into obligation-bearing SEGMENT field artefacts, classifies each segment as a CONSTRAINT or REQUIREMENT candidate (positive obligation → REQUIREMENT by default), emits an AMENDMENT field artefact when an existing source has drifted, updates the codex scan block, and stages everything in a review digest for human admission. Never writes canon. Never auto-admits. Never silently drops.

Read SKILL.md at the source

Pinned to revision 92e95c363dd1, so it is the text this page describes rather than whatever the author pushed since.

Pre-approved tools experimental

Experimental field. Support varies between clients, so this list is what the author declared, not what your client will enforce.

  • Read
  • Write
  • Edit
  • Bash
  • Glob
  • Grep
  • WebFetch

Files

Every link opens the file at its source, pinned to the revision this page describes.