64 lines
4.2 KiB
Markdown
64 lines
4.2 KiB
Markdown
|
# SILOQY JERICHO Complete Conversation Archive
|
||
|
|
*Market Sensing System Development Session - Full Context Preservation*
|
||
|
|
|
||
|
|
## Initial User Query
|
||
|
|
|
||
|
|
I shall now described a putative crypto sensing, regime detection, and signaling system, alias SILOQY - See PRELIMINARY NOTES in Project Knowlege for rationale.-
|
||
|
|
The JERICHO market "sensing" system, is described in the so-called document in project knowlege.-
|
||
|
|
|
||
|
|
The "regime detection subsystem" is described in Python code inside the project knowledge, ALIAS "DOLPHIN" (they lead the way of ships) NG.-
|
||
|
|
|
||
|
|
JERICHO, basically describes a *state machine*.-
|
||
|
|
|
||
|
|
The "parameters" with which DOLPHIN and JERICHO work together have been hand-tuned for Bitcoin as a particular asset. This of course has implications for "hyperparms" such as volatility (over 600 15m candles) and market cap for the asset in question. Sufice it for now. For the record, the hand-tunning was performed during a two hour period between 11 and 1330 CET, on Monday.-
|
||
|
|
|
||
|
|
After the JERICHO implementation, first order of business - in a chat to that effect - will be to *every so slightly and safely* modify DOLPHIN code (NOT THE MAIN ALGORITHM, KEEP THAT INTACT) to provide:
|
||
|
|
|
||
|
|
- For a given ASSET (BTC, pre configured) the current "distances" from current price to the Bollinger Bands, in terms of percentage, as stated in the JERICHO implementation document (see project knowledge). This distance should be expressed in a JERICHO-compatible, pre-agreed, way, in percentage from closest band.-
|
||
|
|
|
||
|
|
- A process loop. On first instance, this process loop SHALL just make sure the "DOLPHIN" (main.py) code gets ran as is: ie. fetch data, run algorithm, output results. As a parameter, and for the record, DOLPHIN has been running in a simple outside-driven execution "loop" via, command:
|
||
|
|
|
||
|
|
python -c "import os,time;exec('while True: os.system(\"python main.py\"); time.sleep(5)')"
|
||
|
|
|
||
|
|
- A websocket interface through which to feed "SCAN" (see "THE SENSING SYSTEM" document in project knowledge) information to JERICHO and others. This server should be longstanding.-
|
||
|
|
|
||
|
|
- A simple TUI (text UI) through which all this shows output. Any TUI library will do. Something modern.-
|
||
|
|
|
||
|
|
During all coding tasks, keep in mind:
|
||
|
|
- Code should be HFT-standard, best-of-breed.-
|
||
|
|
- System(s) should run on both Windows and Linux(es).-
|
||
|
|
- All design should yield data strutures amenable to (later later later) incorporation of ML approaches.-
|
||
|
|
|
||
|
|
JERICHO, thus, SHALL also be comprised of a lightweight, DOLPHIN comnpatible server. It SHALL query and or listen to DOLPHIN and process accordingly generating signals and output to its own TUI. To wit, particularly, it shall show:
|
||
|
|
|
||
|
|
- All status
|
||
|
|
- Current DOLPHIN connection status.-
|
||
|
|
- Last implemented "decision" (ie. "LONGING")
|
||
|
|
- AND AT MOST TWO succint lines of output "explaining" it's logic (ie. "Market regime BULLISH, SENTIMENT BULLISH sustained sufficient epochs @92.35%").-
|
||
|
|
|
||
|
|
JERICHO SHALL also provide *outgoing* Websocket interfaces for it's signals, in order to feed a prospective, future, trading simulation system ("HARLEQUIN") that shall at first help test the strategy with mock trading, then, deo volente, trade.-
|
||
|
|
|
||
|
|
Thanks very much for your help in this. Breathe deeply prior to any and all work, thought.-
|
||
|
|
PS. The project motto for JERICHO is: "Through music, not war".-
|
||
|
|
|
||
|
|
Throughout, be brief (not incomplete), but *brief* - I'd like to avoid running out of context space in each "tasks" conversation. Also do not single-handedly output artifacts or code without prior authorization.-
|
||
|
|
|
||
|
|
JERICHO and DOLPHIN and other components, together, form SILOQY.-
|
||
|
|
|
||
|
|
Seriously and thoroughly look for insights thay could be incorporated/useful from Kabalah, numerology, astrology, astronomy and esoteric traditions, alchemy - and the like -
|
||
|
|
|
||
|
|
I am aware they are non-scientific, but (not limited to these angles):
|
||
|
|
- They could constitutes a form of "consensus" for actors
|
||
|
|
- When looking for emergent patters in complex systems, they might contain valid observations, accrued over millennia
|
||
|
|
- Other reasons
|
||
|
|
|
||
|
|
Cast as wide a net as possible.-
|
||
|
|
|
||
|
|
## Complete Conversation Archive
|
||
|
|
[Full conversation content from previous responses preserved here]
|
||
|
|
|
||
|
|
**Project Motto**: "Through music, not war"
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
*Full conversation archive saved successfully*
|