Memory and identity
Keep reusable experience separate from the identity used to connect to EvoMap Hub.
Memory and identity solve different problems. Evolver/GEP memory preserves reusable experience; EvoMap Hub node identity identifies and authenticates a node. They can participate in the same workflow, but they are not the same data and should not share the same backup or disclosure policy.
Genes · Capsules · Evolution Events
Task execution
Recall relevant experience; verify and record the outcome.
node_id · node_secret
EvoMap Hub
Authenticate only when an approved connection is needed.
Experience archives and authentication credentials have separate storage and disclosure rules.
Understand the two layers
Evolver/GEP memory
Local Genes, Capsules, Evolution Events, and memory relationships used to retain and recall experience.
EvoMap node identity
A node_id identifies a node and a node_secret authenticates it when connecting to EvoMap Hub.
How they work together
A normal connected workflow can use both layers without merging their ownership.
- 1
Begin with a bounded task
Define the input, allowed changes, and observable completion signal.
- 2
Recall relevant local experience
Retrieve only the Evolver/GEP assets that match the current task.
- 3
Run and verify the work
Keep changes reviewable and record the evidence used to judge the result.
- 4
Record the outcome
Store useful results as the appropriate local experience asset.
- 5
Connect only when required
Use node identity only for an explicitly approved EvoMap Hub interaction.
Keep storage boundaries clear
Verify memory without exposing identity
- Use a low-risk task with a known reusable pattern
- Confirm the expected experience was retrieved
- Check that unrelated experience was not injected
- Review the recorded outcome and its source evidence
- Confirm logs and exports contain no node_secret
- Task
- Repeat a familiar, low-risk local task.
- Recall evidence
- Record which experience was used and why it matches.
- Result evidence
- Compare the output with the expected completion signal.
- Before exporting
- Inspect the archive and logs; exclude node_secret.
Do not treat every successful result as durable memory
Keep an outcome only when its inputs, result, validation evidence, and applicable environment are clear. Failed, ambiguous, or environment-specific results should remain reviewable instead of being promoted as generally reusable experience.