Strategy thesis
01Record the conditions that would support or invalidate the idea.
Memory for
trading agents.
Store strategy research, risk preferences and decision history. Retrieve the relevant records when your agent reviews a new market signal.
WORKFLOW EXAMPLETrading agents
Strategy agentReview a market signal
Context starts here
The next response starts with what your agent already knows.
LIGHTHOUSE MEMORY03 RECORDS
Strategy context
Risk preferences
02Keep the user’s exposure limits and approval requirements.
Previous review
03Recall why a similar signal was rejected last session.
Context available to recall
Example inputs and responses showing how memory fits into this workflow.
34,000Builders on Lighthouse
Saved context.
Available to connected applications.
THE PROBLEMWhat gets lost
What gets lost
between sessions.
The strategy gets lost
A restarted agent sees a signal without the assumptions that originally made it relevant.
Constraints get repeated
Risk preferences and review requirements have to be supplied again in every session.
Decisions lose their context
An execution record alone does not explain which research, assumptions or instructions informed it.
WITH LIGHTHOUSEWhat an agent’s brain
What an agent’s brain
can remember.
A trading agent needs more than the latest signal. Save the strategy, constraints and previous reviews so the application can retrieve them before proposing an action.
Retain the strategy
Save the thesis, research and conditions that would invalidate it. Retrieve these records before the agent proposes its next action.
Retrieve relevant records
Search saved observations by meaning, keywords or tags. Your application chooses which results to include in the next request.
Record the decision
Store inputs, reasoning and outcomes as separate records. Content identifiers let reviewers check the saved version.
Keep review steps in the application
Store risk preferences and approval requirements as context. Your application must enforce limits and approve or reject actions.
THE WORKFLOWHow the workflow
How the workflow
uses memory.
Record the research, retrieve the strategy, then review the decision.
- 01
Capture the observation
Write the signal, source reference, timestamp and strategy tags.
- 02
Recall before reviewing
Retrieve related research, constraints and prior decisions for the application to evaluate.
- 03
Record what happened
Persist the chosen action or rejection, its rationale and the eventual outcome.
WHAT LIGHTHOUSE PROVIDES
Memory supports your application’s decision process. A content identifier proves the integrity of a record, not the quality of a trade.
IMPLEMENTATIONSet up the records.
Set up the records.
Connect your application.
Choose what to store, how to retrieve it and which checks your application must perform.
Read the memory docs01
Define a namespace for each strategy or account context.
02
Tag records by instrument, strategy and event type.
03
Keep execution permissions and risk checks in the trading application.
04
Keep source references and timestamps alongside generated summaries.
COMMON QUESTIONSBefore
Before
you build.
Does Lighthouse execute trades?
This use case describes memory infrastructure. Signal generation, risk validation, approvals and order execution belong to the trading application.
Does memory guarantee better returns?
No. Memory can preserve relevant context and make decisions easier to review. It does not establish that a strategy or market observation is correct.
What should the agent remember?
Useful examples include the original thesis, risk preferences, source references, decisions and outcomes. Your application chooses which records to write and recall.
What can a reviewer verify?
A content identifier can help verify that retrieved bytes match the recorded batch. It does not prove the accuracy of the research or the quality of the decision.
