The memory graph

Memory in Vectadyne is a graph of typed nodes joined by typed edges, not a pile of embedded text. Both halves of that carry weight.

Kinds

Every memory has a kind, and the kind determines how it behaves:

Kind	What it is	Notes
fact	Something true about the system	The weakest claim; easily superseded
decision	A choice that was made	Can be superseded by a later decision
lesson	Something learned, usually the hard way	Typically born from an incident
policy	A rule that must be followed	Outranks a lesson or a fact in conflict
skill	A reusable procedure
guide	The standing answer for a topic	Resolved, not stored stale
evidence	A pointer to raw activity	The provenance layer

Kind is not a tag. When a policy and a lesson disagree, the policy wins — because a rule someone committed to outranks a pattern someone noticed.

Status

Status	Meaning
active	Current and returned normally
disputed	Contradicted by something else; returned with that flagged
stale	Aged past its confidence horizon
deprecated	Superseded; not returned as current

Status changes as the corpus grows. A decision does not become wrong because it is old, but it does stop being current once a later one supersedes it — and a good answer distinguishes those.

Edges

Relationships are typed:

Edge	Meaning
supports	Corroborates
contradicts	Directly disagrees
supersedes	Replaces an earlier claim
applies_to	Binds a memory to a scope or entity
caused_by	Traces to origin
inherits_from	Draws from a broader memory

Retrieval returns one hop of edges alongside each hit, so an agent sees not only the memory but what it is connected to — including what contradicts it. Multi-hop traversal does not exist; see What we do not claim.

Conflict is surfaced, not resolved

When two memories disagree, Vectadyne shows you the disagreement rather than silently picking a winner. A disputed hit arrives flagged, with the contradicting edge available.

This is deliberate. A retrieval system that quietly returns one side of a live disagreement is a system that will confidently tell an agent something half your team believes is wrong. Surfacing disputes is less tidy and much more honest — and a warn verdict citing contradicts_decision or disputed_memory is exactly this working.

Sensitivity

Every memory carries a sensitivity: public, internal, restricted, secret. A principal’s clearance determines what it may see, enforced at admission on every read.

Clearance is not advisory. A principal cannot read above its clearance, and a request asking to widen it is refused rather than clamped.

Next

• Retrieval and admission — how a query becomes an answer
• Scopes and inheritance — where a memory applies