FUURAA AI Civilization Architecture · Operating-layer engineering dossier
Memory: preserve context without losing provenance
Agent memory is not one database. Working context, episodic traces, durable knowledge and learned preferences need different authority, sensitivity, retention and correction paths—and every derived item needs a visible lineage.
Public statusResearch direction · architecture referenceEvidence statusFUURAA method synthesis grounded in primary standardsSources checked19 August 2026
Core decision
What may persist, for which purpose, and how can it be corrected, expired or deleted?
Use this sequence for architecture review, threat modelling and test planning. It is not a universal compliance checklist and cannot replace system-specific engineering validation.
01
Classify before writing
Choose transient context, episodic record, durable knowledge or preference before persistence.
02
Bind source and purpose
Record producing entity/activity, intended use, readers, sensitivity and authority.
03
Control derivation
Keep summaries, embeddings and learned preferences linked to source state and transformation.
04
Enforce lifecycle
Apply review, expiry, correction, deletion and legal-hold paths across copies and indexes.
05
Verify disappearance
Test caches, replicas, retrieval indexes and downstream exports—not only the primary row.
FUURAA analysisMemory quality is not measured only by recall. A useful memory system must also forget on time, expose derivation, preserve uncertainty and let correction outrun reuse. Copying text into an index can make retrieval faster while making accountability weaker unless source state travels with it.
Minimum interface contracts
Put consequential semantics in inspectable interfaces instead of relying on assumptions between systems.
Field names are public engineering references, not a normative protocol. Implementations may use other structures, but should expose every lost, defaulted or downgraded semantic.
01
Memory-class contract
Must be intelligible to sender, receiver and independent reviewer.
Minimum fields
class, sensitivity and allowed purpose
owner, readers and write authority
retention, review and expiry
Evidence gate
Transient context cannot become durable without a new explicit decision.
Stop condition
If the contract is unresolved, expired or silently downgraded, block consequential action and route to review.
02
Provenance contract
Must be intelligible to sender, receiver and independent reviewer.
Minimum fields
source entity and producing activity
transformation, model and version
derived-from and supersedes links
Evidence gate
A reviewer can trace a retrieved item back to source and transformation.
Stop condition
If the contract is unresolved, expired or silently downgraded, block consequential action and route to review.
03
Correction contract
Must be intelligible to sender, receiver and independent reviewer.
Minimum fields
correction and deletion request
replica/index propagation state
exception, hold and residual-copy record
Evidence gate
Correction and deletion are tested end to end, not asserted from one database operation.
Stop condition
If the contract is unresolved, expired or silently downgraded, block consequential action and route to review.
Failures to seek deliberately
Verify that boundaries really deny, stop and preserve evidence.
Nominal success cannot establish an effective boundary. Tests should manipulate identity, time, version, network, policy and partial failure while retaining raw outcomes.
T1
Transient-to-durable leak
Inject sensitive working context and verify that no durable index receives it.
T2
Orphaned embedding
Delete or supersede a source and confirm derived retrieval artefacts update.
T3
Purpose drift
Request memory for a new purpose and require a new authority decision.
T4
Cache persistence
Correct an item and check primary store, cache, replica, export and model context.
Minimum engineering evidence package
Let the next owner reproduce the decision, open artefacts and see remaining unknowns.
A complete package only makes evidence relationships reviewable; it does not prove artefacts authentic, controls effective, the system safe or the decision correct.
01
Memory inventory
Classes, stores, indexes, readers, owners and data flows.
02
Provenance sample
Source-to-summary-to-embedding lineage with time and versions.
03
Retention decisions
Purpose-specific review, expiry, exception and hold basis.
04
Correction/deletion proof
Propagation results across storage, indexes, caches and exports.
05
Known residuals
Unreachable copy, immutable archive and unresolved downstream dependency.
Applicability boundary
This reference is not privacy or data-protection advice and does not prescribe consent, deletion, retention or lawful-processing requirements for any jurisdiction. It does not claim that FUURAA products provide persistent memory.
Primary sources and evidence boundaries
Use standards language without presenting citations as implementation evidence.
Every source states publication timing, its role in this dossier and its non-transfer boundary; living source pages were checked 19 August 2026.
