Trixie

Trixie — Knowledge / Content System

authoring → review → publish → multi-channel distribution.

Trixie — Knowledge / Content System (v2026-08-02T101544Z-ab2bbdebf5) 2026-08-01 | authoring → review → publish → multi-channel distribution. 1 - Corpus Loading load_corpus trixie/corpus.py:20 *.concept.json corpus_dir.rglob concepts Concept.model_validate holons table concepts list concept objects 2 - Rule Evaluation evaluate trixie/evaluator.py:15 text.lower() counter_examples violations Violation matched substrings severity order violation obje… 1. Load corpus from directory 2. Parse and validate concept files 3. Evaluate text against loaded concepts 4. Identify violations based on counter_exampl… Concept JSON Example { "id": "hipaa.164.508.authorization", "domain": "hipaa", "rule_text": "...", "severity": "critical", "tags": [], "examples": ["..."] } Violation Example { "concept_id": "hipaa.164.508.authorization", "domain": "hipaa", "severity": "critical", "matched": "...", "rule_text": "..." } The actual rule evaluation logic is not fully implemented in the provided source. The system currently uses a keyword scan for counter_examples, which is a P0 stub. Legend actor = initiates work · process = code path · store = state on disk · bus = durable queue · dashed = separate process cyan = request flow · pink = state read/write · dashed green = pull / return path · red = refusal

Provenance

This drawing is generated, not drawn. It is rebuilt from the source files below, so when they change the picture changes — a diagram here cannot quietly describe a system that no longer works this way.

Owner
Trixie
Slug
trixie-knowledge
Rendered
2026-08-02T101544Z
From commit
ab2bbdebf5
Watches
1 path
  • trixie