Menu
Traces where an answer came from, showing the source connector and link plus the exact passages that support it. Use when an answer must be audited, defended or fact-checked.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Answers a question from the company brain with cited sources and an honest list of what is not documented yet. Use when someone asks a factual question about the company, its systems, people, decisions or incidents.
Records a decision and its rationale back into the company brain after it is made, with sources, and detects supersede and contradiction effects. Use immediately after an architectural or process decision is reached.
Triages what needs human attention now: stale durable knowledge, unresolved incidents and aging gaps, ranked by severity and age. Use at the start of a work session or on-call shift.
Finds who owns or is responsible for a service, decision or area by traversing the typed knowledge graph and entity index. Use when someone needs to know who to talk to about X.
Helps a newcomer learn an unfamiliar area of the company or codebase by mapping its key entities, owners and decisions from the brain. Use in the first days on a new team, service or domain.
Reviews the company as a system and flags operational risks: unowned services, single-person bus-factor, bottlenecks, broken handoffs and redundant tools, each citing the real nodes behind it. Use for a health check or before reorganizing.
| name | trace-provenance |
| description | Traces where an answer came from, showing the source connector and link plus the exact passages that support it. Use when an answer must be audited, defended or fact-checked. |
| version | 0.1.0 |
| triggers | ["where did this come from","show the source","audit this answer","which passage"] |
| tools | ["Vitrus:provenance","Vitrus:chunks","Vitrus:supporting_chunks"] |
Every answer should be defensible down to the passage.
Vitrus:provenance with a slug → which connector fetched it, the back-link, and when it was captured.Vitrus:supporting_chunks with a slug + the question → the exact passages that support the answer, scored.Vitrus:chunks with a slug → the full ordered chunks for a deeper audit."The model said so" is never the source. Cite the connector, the link, and the passage.