When beliefs conflict, Tenure can flag the contradiction, preserve both sides, apply organization standards, and create a reviewable path to resolution.
Contradictions can come from extraction signals, confidence comparisons, compaction scans, or organization standards.
Tenure keeps provenance and lineage so teams can see where conflicting memory came from.
Org standards can act as absolute constraints while user and team preferences remain reviewable.
Most memory systems retrieve whichever item scores highest. Tenure treats conflict as a lifecycle event: detect it, record it, keep the evidence, and resolve it without hiding the transition.
Tenure checks whether two beliefs assert incompatible things about the same subject.
If content differs within the confidence margin, the conflict is flagged instead of overwritten.
Organization standards can mark a belief as conflicting with policy even without another belief.
Contradictions remain pending until resolved, with belief ids, reason, scope, and timestamps.
When a team changes its mind, when a user preference conflicts with a team norm, or when a policy disagrees with a local convention, Tenure makes that visible.
Tenure flags clear conflicts even when the beliefs do not share the same canonical name.
When org standards are supplied, a belief can be flagged against the organization standard itself.
The goal is not to pretend memory is always consistent. The goal is to make inconsistency observable, reviewable, and resolvable.
A resolved contradiction can produce a more precise belief while keeping older assertions available for audit and lineage.
Solo memory can survive with rough edges. Team memory cannot. As soon as multiple developers, repos, tools, and policies contribute context, contradiction handling becomes part of the infrastructure.
Tenure helps teams keep AI memory useful as facts, preferences, standards, and decisions evolve over time.