Make writes source-aware

Where a memory came from determines what it may become.

First time here? Paste the Context Pack first so the AI understands your project - open it from the header above.

Prompt Capsule

Instrument the memory write path with source awareness. Every write must carry the provenance of the content it derived from: USER-STATED (the user directly told the agent), OBSERVED (the agent verified via its own tool execution - a test passed, a file exists), UNTRUSTED-DERIVED (extracted from web pages, third-party docs, tool results of external origin), or INFERRED (the model's own reasoning). Policy by source: user-stated and observed may write to the normal store; untrusted-derived and low-confidence inferred route to quarantine (next step); nothing writes to a 'high-trust' tier except user-stated or multiply-observed. Refactor the memory tool so the source tag is required, not optional, and reject writes that cannot name their source.

Paste into EmergentFull Build: complete implementation prompt with explicit requirements

Quick is short. Full Build is recommended for most steps. Strict forces real logic when the AI keeps faking output.

Actual change check

Expected after this step

A source-required write path enforcing policy by provenance.

Should NOT happen

An existing feature broke
A button only logs to console
Data disappears after refresh
Errors fail silently with no visible state

This is what should exist before you continue. If reality does not match, do not move on.

Your notes for this step

Track what changed, failed, or needs follow-up. Notes export with the flow.

Pass the Verify Gate to complete this step

Verify before continuing

Do not move on until every check is true. The complete button stays locked until then.

Source tag mandatory on every writeUntrusted-derived routes to quarantine by policyHigh-trust tier restricted to user-stated/observed

Do not continue if…

! Persisting anything the agent 'learned' without asking where it came from
! Memories with no provenance, so a poisoned fact is indistinguishable from a real one
! Untrusted-sourced claims recalled with full authority
! Never re-checking stored facts, so poison persists indefinitely

If the AI messes this up

Use this when:

- it only made visual forms or placeholder UI
- buttons do nothing or only log to console
- data is not persisted - state disappears on refresh
- something that worked before is now broken

Use this when the AI fakes progress or breaks the feature. It forces a real fix.

Writes arrive without a credible source. The model is guessing sources to satisfy the field - tighten instructions and validation: 'observed' requires citing the tool result that proves it, or it is demoted to inferred.