Edited
The changed text is extracted again and the newer revision replaces the older one. A revision whose text did not change makes no model call.
Knowledge that keeps up with its sources.
Records change after they are imported. Muninark follows those changes, stops serving what the source no longer holds and keeps expert-approved knowledge apart from what the engine extracted.
When the source changes
Edits become new revisions.
Tickets and documents carry a revision. When one changes, Muninark applies the newer revision and never lets an older copy overwrite it.
Withdrawn
A comment or attachment removed at the source closes its record. The history still counts it, but answers no longer quote it. Superseded text stops being served before the index catches up.
Derived facts
A business rule or decision taken from text that has since changed is flagged for reevaluation. An approved one goes back to an expert and stays approved until the expert acts.
Expert approval
From extracted to approved.
The engine extracts business rules and decisions from your records. Experts review them in their own portal and approve, correct or reject each one.
- Pending · Extracted and cited, not yet reviewed by an expert.
- Approved · Confirmed by an expert. A query can ask for approved records only, for the rule and decision types the deployment protects.
- Rejected · Withdrawn from answers. Search stops using it at once; graph-based tools follow after the next index pass.
- Feedback · Ratings on answers can adjust how sources rank later, counting only people entitled to read the source. Enabled per deployment.
Visible to operators
Know when the index falls behind.
A drift check compares the latest source revisions with what the graph and the index have applied. Its figures feed the health snapshot, an alert and a panel in the operator console. When an operator discards a record on purpose, the check records that decision instead of reporting drift.
Settled during deployment
What still needs an agreed procedure.
These mechanisms run in the engine. How they behave on your records is part of the pilot evaluation.
- Deleting a whole ticket or document at the source.
- Moving a record from one access scope to another.
- Which rule and decision types count as protected. Until the deployment lists them, an approved-only query filters nothing.
- Retention across source data, derived records, indexes, logs and backups.
Walk through a change with us.
Pick a ticket or document your team edits often, and we will show what happens to the knowledge built from it.