Spectron’s memory model is built around eight pillars — not a flat “two layers” split. Two pillars matter most for day-to-day behaviour:
Authoritative — curated artefacts: manuals, policies, product data, structured uploads. Higher default trust.
Experiential — conversation and everything derived from it (reflection, elaboration, consolidation, …), including identity, knowledge, context, instructions, and uncertainties.
Reconciliation merges both streams with the same rules: supersession, uncertainty records, and trust logic apply whether facts arrived from a document or a turn. Physically, both are records in the same unified substrate.
Curated truth is never silently overwritten
Authoritative content does not change because a user said something different. When an experiential assertion conflicts with curated knowledge, Spectron:
Keeps the curated record unchanged.
Stores the user’s belief in experiential memory with provenance intact.
Surfaces the clash — for example via
uncertaintyrecords and conflict indicators in/stateor/profile.
The user’s assertion remains valuable conversational context; it does not become canonical truth. That prevents incorrect chat from silently rewriting product, policy, or compliance data.
Worked example
Your knowledge base states a 30-day return window. A customer says: “Your return policy is 60 days.”
Spectron stores the customer’s belief under their scope in experiential memory and flags the disagreement. The curated policy record is unchanged. When the agent answers, it can acknowledge what the customer said while citing the policy that actually applies.
Attribute resolution order
When both curated and experiential values exist for the same topic:
Authoritative values ground factual answers (price, policy, specification).
Experiential values personalise the interaction; conflicts are visible, not hidden.
Agents should trust curated answers for compliance and use experiential memory for preferences, history, and stated beliefs.
Linking chat to catalogue facts
Experiential mentions can link to authoritative knowledge records (for example resolving “AirPods Pro” in chat to the same product as your catalogue) via resolves_to. See Cross-layer linking.
Practical guidance
Facts with regulatory weight — ground in Authoritative content.
Personalisation — lives in the Experiential pillar.
Contradictions — surface them honestly; never pick silently.
Scope — catalogue updates propagate across the Context; experiential records stay scoped per user, team, or project as you configure.
The full pillar list is in Eight pillars and six categories.