Meeting suggestion
A proposed claim does not authorise an implementation change.
ENTERPRISE MEMORY / A QUESTION OF REUSE
Move from a meeting suggestion to an approved decision, then see what changes when evidence conflicts or access is revoked.
Correct.
Current.
Permitted.
Scripted demonstration using synthetic data. No live customer records, memory service or security enforcement is connected.
Approval is a teaching state you select. It is never generated by a model. Dates belong to this synthetic scenario.
Follow people and agents as they read, contribute and review. Every record has an owner, a type and a history. Every connection has a meaning.
Human contribution: adds a named Technology handoff before access is enabled.
Aisha CONTRIBUTES_TO Joiner readinessVersioned records connected by explicit business relationships. Ownership, source evidence and current permissions travel with the knowledge.
New contributions preserve history. A proposed revision does not grant approval.
Typed relationships and source context reviewed.
These are business facts with defined types, not just visual links.
Entities have stable identities and types. Relationships specify which types may connect. Versions preserve how those facts change.
Human → CONTRIBUTES_TO → Process. A contribution creates a version; it does not grant approval.
Drag nodes to stretch their connections; release to let them settle. Drag the canvas to pan. Use + / −, Ctrl + wheel or pinch to zoom. Keyboard: Tab to a node, Enter to inspect, arrow keys to pan, 0 to reset. Synthetic organisation and scripted activity; no live services or customer records.
A participant suggests SSO-only access for the North customer.
No approved configuration change. Ask the owner to validate the source.
A suggestion has not been accepted as an implementation instruction.
A PROPOSED DESIGN
Confidence is not authority. A model may propose a claim; its confidence does not grant permission or make the claim true.
Retain the original record and its permissions.
Extract a possible fact. Model extraction can be wrong.
Check evidence, entity matches and conflicting claims.
A trusted owner approves the scope and permitted audience.
Check current permissions and valid dates for this task.
Record what happened and any correction required.
Revisit the memory when sources, permissions or outcomes change.
Derived memory needs source lineage, scope, owner, valid dates, recorded dates, approval status and audience. A note-link graph and a temporal knowledge graph serve different purposes.
Revocation, erasure and source updates must invalidate relevant derived records, caches and summaries. This is a design requirement, not something this demo or any product supplies automatically.
READ THE DECISIONS
A proposed claim does not authorise an implementation change.
The scoped owner may use the current approved instruction and cite its evidence.
Reconcile apparently authoritative records before making a recommendation.
Keep the history for explanation. Retrieve the replacement under current permissions.
Withhold the source and derived answer. Previously cached context must also be invalidated.
Quarantine content that tries to approve itself. Source text cannot grant authority.
In every state, an actor outside the source’s scope receives neither its content nor a derived answer.
THE THINKING BEHIND THE DEMONSTRATION
Read the research, the proposed architecture and the questions worth testing in your own organisation.