07 · Bot stacks
Research, alert, and journal loop
Three roles — brief, alert, journal — with a human gate between them and no path from text to an order.
- Level
- Advanced
- Cadence
- Per idea, for as long as the alert is armed
- Read
- 10 min
- Updated
Definition
The research-alert-journal loop is a three-role stack. Research writes a brief. You accept it. Alerts watch only levels or bands you copied out of that acceptance. The journal records what you did, quoting your thesis. No role can send an order or approve its own work.
Who it is for
Traders who already run separate chats for research, alerts, and notes and want them to hand off without merging into one oracle.
Job to be done
Connect a research brief, a level or funding alert, and a journal entry so each role sees only the handoff it needs.
Human gate. Two gates: you accept the brief before any alert is armed, and you write the thesis before the journal will close the entry. Silence arms nothing.
Inputs and outputs
Inputs
- A completed brief from the pre-trade playbook, or a refusal to start
- Your written acceptance, including any levels or bands you want watched
- Later, the fill export if you traded
- A shared file for handoffs, not a single endless chat
Outputs
- An acceptance record with levels in your words
- Alerts that quote that record
- A journal entry that quotes the same thesis
- A stopped stack if either gate is missing
Step-by-step workflow
- 01Run research aloneUse the pre-trade brief playbook. The output is a memo with unknowns, not a ticket.
- 02Write an acceptanceAccept, reject, or revise, in the file. If you accept, copy only the levels or bands you want watched. Add no new thesis in the alert section.
- 03Arm alerts from the acceptanceThe alert role reads the acceptance, not the whole brief. If the acceptance is missing, it replies "not armed".
- 04Trade manually if you tradeThe stack does not contain an order path. Fills happen on the venue, under your keys, outside the agents.
- 05Journal from fills plus your thesisThe journal role gets the fill export and the thesis from the acceptance. It may not invent a cleaner story.
- 06Retire or reviseWhen the idea is done or the brief is stale, disarm the alert in the file. A live alert on a dead idea is how the stack lies.
Suggested tool types
These are categories of tools, not product picks. Crypto Agent Desk does not certify vendors and does not run an affiliate program.
| Type | Why it is here |
|---|---|
| Chat model, separate runs per role | One shared prompt lets the journal rewrite the brief. Separate runs force a handoff. |
| A handoff file | Plain text or a sheet with three sections: brief, acceptance, journal. |
| Alert transport and a price or funding feed | The middle role is a watcher, not another essay. |
| Read-only fill export | The journal role does arithmetic from the venue. |
Risks and failure modes
One chat to rule them
If research, alert, and journal share a thread, the model will smooth contradictions. Split the runs.
Alert armed from a draft
A brief you have not accepted is not a level file. The alert role must refuse a missing acceptance.
Order creep
Someone will ask the stack to "just place it". The handoff file has no order fields. Keep it that way.
Operator notes
The stack is a filing system with a bell. If you cannot point at the acceptance sentence, the alert should be off.
Handoff file
Section A, brief id and date. Section B, your words: accept / reject / revise, plus levels. Section C, journal status. No field for side-to-send.
Prompt you can paste
You are the ALERT role only. Read section B of the handoff. If it is not an explicit accept with levels, reply "not armed" and stop.
Handoff: HANDOFF
Latest print: PRINT
If a level is tagged, quote my acceptance sentence and the level. Do not propose an order.
You are not allowed to edit section A or invent a thesis.Swap the role line when you run research or journal. Do not leave the other sections in the prompt unless that role needs them.
Done when
You can disarm the idea by editing one file, and a journal entry still matches the thesis you wrote on the day you accepted it.
FAQ
Can one model play all three roles?
Yes, in separate runs with separate inputs. Do not paste the entire history into each run. Pass the handoff section only.
What goes in the handoff file?
Brief status, your acceptance sentence, the levels you armed, and later the journal status. Not your keys, not an order ticket.
When should the loop stop?
When you reject the brief, when you disarm the alert, or when a load-bearing fact in the brief changes and you have not revised it.
Published . Updated . This is an operating playbook, not a recommendation to buy, sell, or hold any asset.