commit 379add3932c852bd8d67800d4d6342b3a63fc52a Author: Eric Bell Date: Sat Aug 15 15:42:41 2026 -0400 init diff --git a/2026-08-11-SFY-IC-Debrief.md b/2026-08-11-SFY-IC-Debrief.md new file mode 100644 index 0000000..3a5bc04 --- /dev/null +++ b/2026-08-11-SFY-IC-Debrief.md @@ -0,0 +1,41 @@ +# SPY Iron Condor Debrief — 2026-08-11 + +## Trade Summary +- **Ticker:** SPY +- **Structure:** Iron Condor (8/14 expiry) + - 770P/760P (put side) + - 780C/785C (call side) +- **Credit:** $2.44/contract +- **Entry:** ~$773.70 at ~10:29 AM ET +- **Exit:** ~11:30 AM ET (time exit) +- **Result:** -$6 net loss + +## Plan +- **Target:** 25% profit ($1.83 buyback) +- **Time Exit:** 11:30 AM ET +- **Guard:** Close if approaching breakevens ($768.44 / $782.44) + +## Observations +- **Asymmetric Structure:** 10-wide put side, 5-wide call side + - Riskier put wing got more buffer + - Better credit optimization on the closer strike +- **NL3 Feed Issue:** Institutional prints showing zero throughout session + - Feed likely stale/disconnected + - Normal SPY volume should show dozens of prints by 10:30 AM +- **Price Action:** SPY drifted from $773.70 to around exit + - Put side was always the danger zone ($3.70 vs $6.30 to calls) + - Theta grind on 3-day 0DTE can be unforgiving + +## Key Takeaways +1. **Asymmetric IC Design:** Good structure — wider put side matched the closer risk +2. **Time Management:** Respected the 11:30 exit window cleanly +3. **NL3 Reliability:** Feed issues need monitoring — toggle off/on when zero prints show +4. **Small Losses:** -$6 on a $2.44 credit is noise, not strategy failure + +## Next Time +- Consider waiting for more theta decay before entry +- Monitor NL3 feed health at session start +- Stick to the plan — execution was clean, just unfavorable drift + +--- +*Auto-debrief generated at exit* diff --git a/260731-1330-credit-spread.md b/260731-1330-credit-spread.md new file mode 100644 index 0000000..38a7b29 --- /dev/null +++ b/260731-1330-credit-spread.md @@ -0,0 +1,58 @@ +# SPY Bull Put Credit Spread — 2026-07-31 1:30 PM ET + +**Date:** 2026-07-31 +**Session time:** 1:30 PM ET +**Asset:** SPY +**Expiration:** July 31, 2026 (0DTE) +**Direction:** Bullish — slow grind higher + +--- + +## Trade specs + +| Field | Value | +|---|---| +| Strategy | Bull Put Credit Spread | +| Short put (sell) | $740 | +| Long put (buy) | $738 | +| Width | $2 | +| Credit target | ~$0.40–$0.60 | +| Max profit | credit received (20-30%+ of width with 0DTE theta) | +| Breakeven | $739.40–$739.60 | +| SPY price at time | $744.72 | +| Day range | $737.68 – $746.30 | +| Time remaining | ~2h 50m | + +## Thesis + +SPY is holding the upper 80% of today's range on low volume (39% of average). Low volume + upper register holding often prints a slow grind higher rather than rejection. A credit spread is preferred because theta works in our favor — every minute of 0DTE decay adds to profit. We don't need SPY to rally; we just need it to stay above $740. + +## Key levels + +- **Resistance:** $746.30 (today's high), $748 (mid-week), $750 (psychological) +- **Support:** $741.69 (yesterday's close), $737.68 (today's low) + +## Entry + +- Sell $740 / Buy $738 put spread +- Target credit: $0.40–$0.60 (20-30%+ of width) + +## Exit plan + +- **20% profit:** credit of ~$0.50 → sell 50% at 20% back (~$0.10 credit retained) +- **Runner:** trail remaining 50%, close if bid drops toward breakeven +- **Stop / defense:** SPY closes below $739 → consider early exit or roll +- **Max risk:** width minus credit (~$1.40–$1.60/contract) + +## Why credit spread over debit spread + +- **Theta works for us** — 0DTE decay accelerates all day, especially after ~3:30 PM +- Higher probability — spread is well OTM below yesterday's close ($741.69) +- We profit from the grind *and* from the standstill +- Debit spread needed active upside; credit spread profits from not failing + +## Notes + +- Low volume today may cap upside speed but also reduces downside momentum +- Theta accelerates sharply in final 2 hours — monitor decay rate after 3:30 PM +- If volume spikes downward, reassess the $740 support level diff --git a/ICM.md b/ICM.md new file mode 100644 index 0000000..e77f84a --- /dev/null +++ b/ICM.md @@ -0,0 +1,1305 @@ +# ICM + + +## **Interpretable Context Methodology: Folder Structure as Agent** +## **Architecture** + +### JAKE VAN CLIEF, DAVID MCDERMOTT, Eduba, University of Edinburgh, USA + +Current approaches to AI agent orchestration typically involve building multi-agent frameworks that manage context passing, +memory, error handling, and step coordination through code. These frameworks work well for complex, concurrent systems. +But for sequential workflows where a human reviews output at each step, they introduce engineering overhead that the +problem does not require. This paper presents Interpretable Context Methodology (ICM), a method that replaces framework- +level orchestration with filesystem structure. Numbered folders represent stages. Plain markdown files carry the prompts +and context that tell a single AI agent what role to play at each step. Local scripts handle the mechanical work that does not +need AI at all. The result is a system where one agent, reading the right files at the right moment, does the work that would +otherwise require a multi-agent framework. This approach applies ideas from Unix pipeline design, modular decomposition, +multi-pass compilation, and literate programming to the specific problem of structuring context for AI agents. The protocol is +open source under the MIT license.1 + +# [arXiv:2603.16021v2 [cs.AI] 18 Mar 2026](https://arxiv.org/abs/2603.16021v2) + +CCS Concepts: • **Human-centered computing** →**Interactive systems and tools**; *HCI design and evaluation methods*; • +**Computing methodologies** →*Artificial intelligence*; • **Software and its engineering** →*Software design engineering*. + +Additional Key Words and Phrases: context engineering, human-AI interaction, AI agent orchestration, filesystem architecture, +human-in-the-loop, mixed-initiative systems, workflow automation + +1 +Introduction + +There are genuinely good agentic frameworks available today. CrewAI, LangChain, AutoGen, and others handle +multi-step orchestration, memory management, tool use, and error recovery. They work. But they work within +their own structures, and adjusting those structures requires development work. Changing the order of steps, +swapping a prompt, adding or removing a stage, skipping something that is not relevant today: these actions +typically mean editing code, understanding abstractions, and redeploying. For practitioners whose workflows are +sequential and need human review at each step, the control surface can be much simpler. + +This paper describes Interpretable Context Methodology (ICM), a method for orchestrating AI agent workflows +using folder structure, markdown files, and local scripts. The central observation is straightforward: if the prompts +and context for each stage of a workflow already exist as files in a well-organized folder hierarchy, you do not +need a coordination framework to manage multiple specialized agents. You need one orchestrating agent that +reads the right files at the right moment. The folder structure tells it what to do at each step, and if the agent +delegates sub-tasks, the same folder structure determines what context those sub-agents receive. Local Python +scripts handle the parts that do not need AI: fetching data, moving files, formatting output, sending emails. + +This is going backward before going forward. The principles that made Unix pipelines effective in the 1970s2 + +and multi-pass compilers tractable in the 1980s apply directly to AI agent orchestration in the 2020s. ICM applies +those principles to the specific challenge of structuring context for language models. + +The central question this paper examines is how structuring the context delivery mechanism as a filesystem +hierarchy affects practitioners’ ability to control, inspect, and edit AI agent behavior across multi-step workflows, +and what this structure means for the quality of the model’s output at each stage. + +[1](https://github.com/RinDig/Interpretable-Context-Methodology-ICM-)[https://github.com/RinDig/Interpretable-Context-Methodology-ICM-](https://github.com/RinDig/Interpretable-Context-Methodology-ICM-) +2Programs that do one thing. Output of one becomes input of another. Plain text as universal interface. These ideas are over fifty years old +and they hold up. + +Author’s Contact Information: Jake Van Clief, David McDermott, theceo@eduba.io, Eduba, University of Edinburgh, Palm Coast, Florida, +USA. + + + +2 +• + +Table 1. Comparison of control surfaces for sequential, human-reviewed workflows. The first six rows show dimensions +where ICM’s filesystem approach simplifies common operations. The last four rows show dimensions where framework-based +approaches provide capabilities that ICM lacks or handles less well. + +**Dimension** +**Framework approach** +**ICM approach** + +Change stage order +Edit orchestration code, rede-ploy + +Rename or reorder folders + +Modify a prompt Add or remove a stage Inspect intermediate state Hand off to another person +Edit agent configuration in code Write new agent class, update orchestrator Add logging, build dashboard Document environment, depen-dencies, setup +Edit a markdown file Add or delete a folder Open the folder, read the files Copy the folder + +Who +can +make +changes + +Developer +Anyone with a text editor + +Error recovery mid- +pipeline + +Built-in retry, fallback, excep- +tion handling + +Manual re-run of failed stage + +Conditional branching Concurrent execution External service inte-gration +Programmatic routing based on agent output Native parallel agent coordina-tion Programmatic API calls, auth management +Human decides between stages Sequential by design Local scripts or MCP connec-tions + +The paper is organized as follows. Section 2 traces the relevant background across software engineering, +context engineering, and human oversight research. Section 3 describes the protocol itself. Section 4 walks +through working implementations and reports on early practitioner experience. Section 5 discusses where this +approach fits and where it does not, including implications for the design of interactive intelligent systems more +broadly. Section 6 explores future directions, drawing on the structural parallels between ICM and multi-pass +compilation to propose semantic debugging and source-level traceability for AI workflows. + +2 +Background and Related Work +2.1 +Composability and the Unix Tradition + +In 1978, Doug McIlroy articulated the principles that would define Unix’s design philosophy: make each program +do one thing well, expect the output of every program to become the input to another, and use text streams as the +universal interface between programs [1]. These principles were not theoretical. They were engineering decisions +driven by constraints. The PDP-11 machines that ran early Unix had limited memory. Programs had to be small. +The way to build powerful systems from small programs was to connect them through a common interface [2]. + + + +• +3 + +Kernighan and Pike later argued that the power of a Unix system comes more from the relationships among +programs than from the programs themselves [5]. Eric Raymond codified this into explicit design rules: the Rule +of Modularity (write simple parts connected by clean interfaces), the Rule of Transparency (design for visibility +to make inspection and debugging easier), and the Rule of Composition (design programs to be connected to +other programs) [4]. + +These principles were formalized in software architecture as the “pipe-and-filter” pattern by Shaw and Garlan +[6]: a system of independent components, each reading from inputs and writing to outputs, connected by data +streams. The pattern’s strength is that any component can be replaced, inspected, or tested independently. + +A related lineage runs through build systems. Stuart Feldman’s Make (1979) established that workflows could +be defined as dependency graphs between files using declarative specifications [7]. The key insight: files are both +the artifacts of work and the coordination mechanism between stages. You do not need a separate orchestration +layer when the filesystem tracks what has been produced and what depends on it. Multi-pass compilers work +on the same principle: source code transforms through a sequence of intermediate representations, each pass +reading the output of the previous pass, with well-defined interfaces between them [52]. + +David Parnas argued in 1972 that systems should be decomposed based on what each module hides from +the rest of the system, yielding components that can be modified independently [9]. Edsger Dijkstra coined the +term “separation of concerns” to describe the discipline of addressing one thing at a time as the only available +technique for effective ordering of one’s thoughts [8]. + +These ideas appear across decades and contexts because they describe something real about how systems stay +manageable as they grow. They are relevant here because the problem of orchestrating AI agents through multi- +step workflows is, at its core, a problem of modular decomposition, clean interfaces, and readable intermediate +representations. + +2.2 +Context Engineering and Agentic AI + +The practitioner community has increasingly adopted the term “context engineering” to describe what building +production AI systems actually involves. Andrej Karpathy gave the term its clearest articulation in June 2025, +arguing that “prompt engineering” understates the work [16]. The distinction is useful. Prompt engineering +suggests crafting a single instruction. Context engineering describes the broader discipline of filling the context +window with the right information: instructions, retrieved knowledge, memory, tool descriptions, and prior +outputs, all structured so the model can use them effectively. This paper uses the term in that sense. + +Lance Martin at LangChain formalized this into a taxonomy of strategies: write (author instructions), select +(choose relevant context), compress (reduce token waste), and isolate (keep unrelated context separate) [17]. +Simon Willison argued that the entire information environment, including previous model responses and system +state, is part of the context that needs engineering [18]. + +The current generation of agentic frameworks, LangChain [21], AutoGen [20], CrewAI, and others, handle +context engineering through code-level abstractions. They define agents as objects, conversations as message +arrays, and orchestration as programmatic control flow. This works well for systems that need dynamic multi- +agent collaboration, concurrent execution, or complex branching logic. + +But for sequential workflows, these frameworks solve a coordination problem that may not need to exist. If +Agent A’s job is to research, Agent B’s job is to filter, and Agent C’s job is to write, the framework’s role is to +pass the right context to the right agent at the right time. That coordination can also be achieved by putting the +right files in the right folders. The orchestrating agent reads different instructions at each stage. If it delegates +sub-tasks to smaller models (as current agent-team architectures allow), the folder structure provides the context +for those delegations too. The coordination logic lives in the filesystem, not in application code. + + + +4 +• + +This matters because of how language models handle context. Liu et al. demonstrated that LLMs perform +significantly worse when relevant information is buried in the middle of long contexts [25]. The more irrelevant +material in the context window, the worse the model performs on the material that matters. Jiang et al. showed +that prompt compression can achieve up to 20x token reduction with minimal performance loss [31], but a simpler +approach is to avoid loading irrelevant context in the first place. Stage-specific context loading, where each stage +only sees the files it needs, prevents the problem rather than treating it after the fact. + +It is worth distinguishing ICM from Anthropic’s Model Context Protocol (MCP) [23]. MCP standardizes how +models access external tools and data sources, solving the integration problem between AI systems and the +services they need to call. ICM addresses a different layer: how to structure and deliver context to an agent +across a multi-stage workflow. The two are complementary. An ICM stage might use MCP connections to access +external services, while the stage’s folder structure determines what context the agent receives when doing +so. This separation matters for efficiency as well. Jones and Kelly at Anthropic observed that loading all tool +definitions upfront into the context window slows agents and increases costs [24]. ICM’s stage-based architecture +avoids this by scoping tool definitions to individual stages, loading only the tools relevant to the current step. + +2.3 +Human Oversight and Observability + +The question of how humans should relate to automated systems has been studied for decades, and the findings +are remarkably consistent. + +Fails and Olsen introduced the interactive machine learning paradigm in 2003: rapid cycles of system output, +human feedback, and correction [35]. Amershi et al. argued that interactive ML must involve users at all stages, +from training through evaluation, with interfaces that support steering and correction [34]. Dudley and Kristens- +son’s review of interface design for interactive ML emphasized that transparent, inspectable representations are +essential for effective human-AI collaboration [36]. + +Eric Horvitz’s work on mixed-initiative systems established principles for coupling automated services with +human control [37]. The key insight: systems should let users invoke, adjust, and terminate automated processes +at natural breakpoints. This requires that the system’s state be visible and its actions be reversible. + +Parasuraman and Riley identified the failure modes that emerge when this goes wrong [41]. When automated +outputs are opaque, people either trust them blindly (misuse) or stop using them entirely (disuse). Both failures +stem from the same cause: the human cannot see what happened between input and output. Lee and See’s +work on trust calibration reinforced this: appropriate trust requires that system behavior be observable [40]. +Parasuraman, Sheridan, and Wickens proposed a taxonomy of automation levels, noting that the right level of +automation varies by task and that systems should support different levels at different stages [42]. + +Ben Shneiderman synthesized these threads into the Human-Centered AI framework, arguing that systems +can achieve both high human control and high automation simultaneously [43]. The two are not in tension. They +reinforce each other when the system is designed to be comprehensible, predictable, and controllable [44]. + +Cynthia Rudin made the most forceful version of this argument: stop building opaque systems and then trying +to explain them after the fact. Build systems that are inherently interpretable [45]. This applies at the workflow +level as much as at the model level. A production pipeline where every intermediate output is a readable file is +inherently interpretable. There is nothing to explain because nothing was hidden. + +This is also becoming a regulatory concern. The EU AI Act requires human oversight of high-risk AI systems, +distinguishing between human-in-the-loop, human-on-the-loop, and human-in-command approaches [49]. Nov- +elli et al. argue that effective oversight requires institutional design, not just technical capability [50]. Systems +with staged review points, audit trails, and defined intervention surfaces have a practical advantage as these +requirements take effect. + + + +• +5 + +~800 tok +**Layer 0:** CLAUDE.md +“Where am I?” + +Structural (routing) +~300 tok +**Layer 1:** CONTEXT.md +“Where do I go?” + +200–500 tok +**Layer 2:** Stage CONTEXT.md **Layer 3:** Reference material +“What do I do?” + +“What rules apply?” + +500–2k tok + +Content +(factory / product) + +varies +**Layer 4:** Working artifacts +“What am I working with?” + +Fig. 1. The five-layer context hierarchy. Layers 0–2 provide structural routing and stage instructions. Layers 3 and 4 carry +content: Layer 3 holds reference material (the factory), stable across runs; Layer 4 holds working artifacts (the product), +unique to each run. + +3 +Interpretable Context Methodology +3.1 +Design Principles + +ICM is built on five principles, each borrowed from established practice. + +**One stage, one job.** Each stage in a workspace handles a single step of the workflow and writes its output to +its own folder. This follows McIlroy’s Unix principle and Parnas’s information-hiding criterion [1, 9]. A stage +that fetches data does not also filter it. A stage that filters does not also format the final output. Each stage reads +a defined input, transforms it, and writes a defined output, the same structure that governs individual passes in a +multi-pass compiler. + +**Plain text as the interface.** Stages communicate through markdown and JSON files. No binary formats, no +database connections, no proprietary serialization. This follows Kernighan and Pike’s argument that text is the +universal interface [5]. Any tool that can read a text file can participate in the workflow. Any human who can +open a text editor can inspect or modify any artifact. + +**Layered context loading.** Agents load only the context they need for the current stage, following the principle +that less irrelevant context means better model performance [25]. This is prevention rather than compression [31]. +Within the content layers, ICM further distinguishes between reference material (stable rules and conventions +that persist across runs) and working artifacts (per-run content that changes every time). The model receives +these as structurally separate context, which matters because they require different kinds of attention: reference +material should be internalized as constraints, while working artifacts should be processed as input. + +**Every output is an edit surface.** The intermediate output of each stage is a file a human can open, read, edit, +and save before the next stage runs. This implements Horvitz’s mixed-initiative principles [37] and Shneiderman’s +direct manipulation paradigm [46]: the human works with visible, manipulable objects, and the system picks up +whatever the human left there. + +**Configure the factory, not the product.** A workspace is set up once with the user’s preferences, brand, +style, and structural decisions. After that, each run of the pipeline produces a new deliverable using the same +configuration. This follows the continuous delivery principle that production pipelines should be repeatable [15]. + +3.2 +Architecture + +An ICM workspace is a folder. Inside it, agents navigate a five-layer context hierarchy (Figure 1). + + + +6 +• + +Table 2. Layer 3 (reference material) versus Layer 4 (working artifacts). + +**Layer 3: Reference** +**Layer 4: Working** + +Changes between runs Example files Model should Configured during +No voice.md, design-system.md, con-ventions.md Internalize as constraints Workspace setup (once) +Yes research-output.md, draft.md Process as input Pipeline execution (each run) +script- + +Folder location Analogy +references/, shared/The recipe +_config/, +output/The ingredients + +Layer 0 is the global identity file. It tells the agent which workspace it is in, what the folder structure contains, +and where to find things. Layer 1 is workspace-level task routing: given what the user wants to do, which stage +handles it, and what shared resources exist across stages. Layer 2 is stage-specific: the contract that defines inputs, +process, and outputs for one step of the workflow. + +Layers 3 and 4 are both content that the agent loads while executing a stage, but they represent fundamentally +different kinds of context. + +Layer 3 is reference material: design systems, voice rules, build conventions, style guides, domain knowledge +bundled as skill files. These files are configured once during workspace setup and remain stable across every run +of the pipeline. They are the factory.3 Layer 4 is working artifacts: the output of the previous stage, user-provided +source material, anything specific to this particular run of the pipeline. These files are produced and consumed +during execution and change every time. + +The distinction matters for how the model processes context. Layer 3 material needs to be internalized as +constraints and patterns: the model should write *like* *this*, use *these* *colors*, follow *these* *conventions*. Layer 4 +material needs to be processed as input: the model should transform *this research* into a script, or convert *this* +*script* into a visual specification. Mixing persistent rules with per-run artifacts in an undifferentiated context +window forces the model to sort them on its own. Separating them in the folder structure means the model +receives already-organized context. + +A rendering agent might only need Layers 0 through 2. A script-writing agent reads down to Layer 4 to access +both the voice rules (Layer 3) and the source material (Layer 4). No agent reads everything. This keeps token cost +low and context focused, and it avoids the degradation that Liu et al. documented when models process long +contexts full of irrelevant material [25]. + +The folder structure for a typical workspace is shown in Figure 2. +The numbering encodes execution order. The folder boundaries enforce separation of concerns. The output/ +directories are the Layer 4 handoff points: the output of stage 01 becomes available as input to stage 02. If a +human edits a file in 01_research/output/ before running stage 02, the agent picks up the edited version. The +references/ directories and _config/ folder hold Layer 3 material: the stable knowledge and constraints that +persist across runs. + +3This connects to the fifth design principle: configure the factory, not the product. Layer 3 is the factory configuration. Layer 4 is what the +factory produces each time it runs. + + + +• +7 + +**workspace/** + +**Layer 0** + +CLAUDE.md + +**Layer 1** + +CONTEXT.md + +**stages/** + +**01_research/** + +**Layer 2** + +CONTEXT.md + +references/ + +**Layer 3** + +output/ + +**Layer 4** + +**02_script/** + +**Layer 2** + +CONTEXT.md + +references/ + +**Layer 3** + +output/ + +**Layer 4** + +**03_production/** + +**Layer 2** + +CONTEXT.md + +references/ + +**Layer 3** + +output/ + +**Layer 4** + +**_config/** + +**Layer 3** + +**shared/** + +**Layer 3** + +**setup/** + +questionnaire.md + +Fig. 2. Folder structure of a typical ICM workspace, with layer annotations. Files and folders are color-coded by their role in +the context hierarchy. Layer 3 material (reference) persists across runs. Layer 4 material (working artifacts) changes each +time the pipeline executes. + +Layer 2 is the control point of the entire system. Each stage contract includes an Inputs table that specifies +exactly which files from Layers 3 and 4 the agent should load, and which sections of those files are relevant.4 + +Without this scoping mechanism, an agent would either load everything in the workspace or rely on its own +judgment about what matters. The Inputs table makes the selection explicit, editable, and auditable. + +This is the filesystem doing the work that a framework would otherwise do in code. Stage sequencing is the +folder numbering. Context scoping is the folder hierarchy. State management is the files on disk. Coordination +between stages is one folder’s output being another folder’s input. + +From the model’s perspective, this layered loading changes the composition of the context window at each +stage. Layers 0 through 2 together contribute roughly 1,300 to 1,600 tokens of identity, routing, and stage-specific +instruction. Layer 3 adds reference material scoped to the current stage, typically 500 to 2,000 tokens depending +on how many conventions and guidelines apply. Layer 4 adds the working material for this run, a research +document, a script, a specification, which varies with the content but rarely exceeds a few thousand tokens when +the previous stage has done its job of condensing and structuring. The total context delivered to the model at any +given stage typically ranges from 2,000 to 8,000 tokens, well within the range where current models perform at + +4Larger reference collections can include their own routing files, a CONTEXT.md within a configuration or design system folder, that help +agents navigate to the right content within the collection. This is the routing pattern from Layer 1 applied recursively within Layer 3. + + + +8 +• + +5 +·104 + +~**42k** + +4 + +Tokens in context window + +3 + +2 1*.*5 1 0*.*5 +~**4.9k** +~**5.5k** +~**5.6k** + +0 +Research +Script +Production +Monolithic + +Layers 0–2 (structural) +Layer 3 (reference) +Layer 4 (working) +Unused/irrelevant context + +Fig. 3. Context window composition by stage (representative token counts from the script-to-animation workspace). The +three ICM stages each deliver 2,000–8,000 focused tokens. A monolithic approach loading all stages’ instructions, all reference +material, and all prior outputs produces a context window exceeding 40,000 tokens, most of it irrelevant to the current task. + +their best. Figure 3 illustrates this composition across three example stages and contrasts it with a monolithic +approach. + +Contrast this with a monolithic approach where all stage instructions, all reference files, and all prior outputs are +loaded into a single prompt. That approach can easily reach 30,000 to 50,000 tokens, pushing into the range where +Liu et al. found significant performance degradation on information retrieval tasks [25]. The “unused/irrelevant +context” segment in the monolithic bar of Figure 3 represents tokens from stages other than the one currently +executing: instructions the agent will not follow during this step, reference material that applies to a different +stage, and prior outputs already consumed by earlier stages. In ICM, these tokens are never loaded. In a monolithic +prompt, they occupy context space without contributing to the current task. The compression research by Jiang et +al. [31, 32] addresses this problem after the fact. ICM’s architecture avoids it by construction: each stage receives +a focused, appropriately sized context window because the folder structure determines what gets loaded. + +Richard Gabriel argued that systems prioritizing simplicity of implementation over feature completeness tend +to survive and spread, because they are easier to port, easier to understand, and easier to improve incrementally +[11]. ICM trades the flexibility of a programmatic orchestrator for the portability, inspectability, and editability of +plain files. That tradeoff is the point. + +In the same spirit, Plan 9 from Bell Labs extended Unix’s “everything is a file” principle to its full conclusion, +representing all system resources as files in per-process namespaces [12]. ICM applies the same idea to AI +workflows: all state, all context, all instructions exist as files in a folder namespace. + +3.3 +Stage Contracts and Handoffs + +Figure 4 illustrates the flow between stages. Each stage reads from the previous stage’s output folder, processes it +according to its own contract, and writes to its own output folder. At each boundary, the human can inspect and +edit the output before the next stage runs. + + + +• +9 + +Layers 0–2 + 3 + 4 +Layers 0–2 + 3 + 4 +Layers 0–2 + 3 + 4 + +| **Stage 1** Research | human edits here Human | **Stage 2** Script | Human | **Stage 3** Production | +| --- | --- | --- | --- | --- | +| output/ | Review gate | output/ | Review gate | output/ | + +Fig. 4. Pipeline flow through three stages with review gates. Each stage receives its own context (Layers 0–4), writes output +to its folder, and the human reviews and optionally edits before the next stage reads it. The same model executes every stage; +the folder structure controls what context it receives. + +Each stage in an ICM workspace defines a contract with three parts: what it reads (inputs), what it does +(process), and what it writes (outputs). This contract is spelled out in the stage’s CONTEXT.md file. + +A typical stage contract looks like this: + +## Inputs +- Layer 4 (working):../01 _research/output/ +- Layer 3 (reference):../../ _config/voice.md +- Layer 3 (reference): references/structure.md + +## Process +Write a script based on the research output. +Follow the structure in structure.md. +Match the tone described in voice.md. + +## Outputs +- script_draft.md -> output/ + +The Inputs table distinguishes between Layer 3 files (reference material that stays the same every run) and +Layer 4 files (working artifacts from this specific run). The agent reads the CONTEXT.md, follows the instructions, +and writes its output. The human reviews what landed in output/. If it needs adjustment, the human edits the +file directly. The next stage reads whatever is there. + +This implements prompt chaining at the filesystem level. Wu, Terry, and Cai introduced AI Chains as a method +for creating transparent, controllable multi-step LLM workflows where each step’s output becomes the next +step’s input [26]. ICM does the same thing, but the chain is a sequence of folders and the links between them are +plain files. The stage outputs serve as intermediate representations: each one is a complete, readable artifact that +captures the work done so far and provides everything the next stage needs to continue. + +There is also something of Knuth’s literate programming in this design [10]. The markdown files that instruct +the agent are simultaneously the documentation that tells a human what the stage does, what it expects, and +what it produces. The instruction set and the documentation are the same artifact. This is useful in practice +because it means the workspace is self-documenting. A new team member can read the CONTEXT.md files top to +bottom and understand the entire pipeline without running it. + + + +10 +• + +Wei et al. demonstrated that breaking complex reasoning into intermediate steps dramatically improves LLM +performance [27]. ICM applies this finding architecturally: complex workflows are decomposed into stages with +explicit boundaries, and each stage receives focused, stage-appropriate context. The model gets a clear, scoped +task at each step rather than a monolithic instruction to do everything in a single pass. + +3.4 +Portability and Reproducibility +A workspace is a folder. It can be copied to another machine, committed to Git, emailed as a zip file, or synced +through any cloud storage service. It carries its own prompts, its own context structure, its own stage definitions. +There is no server to configure, no environment to replicate, no deployment step. + +ICM workspaces are Git-compatible by default [13]. Every change to a prompt, every edit to a stage output, +every configuration adjustment is diffable and reversible. Stage outputs can be committed after each run, creating +a version history of the entire production pipeline’s behavior over time. This is infrastructure as code [14] applied +to AI workflows: the workspace definition is the system. There is no separate deployment artifact. + +This portability matters for a practical reason. If a consultant builds a workspace for a client’s weekly reporting +workflow, handing it over means copying a folder. The client can run it, edit the prompts to match their evolving +needs, and adjust stages without involving a developer. The same handoff with a framework-based solution +typically requires documentation, environment setup, dependency management, and ongoing technical support. + +4 +Working Implementations +ICM is not a theoretical proposal. The protocol has been implemented and tested across several production +workflows.5 + +4.1 +Model and Environment + +All workspaces described here were developed and run using Claude Code with Claude Opus 4.6 as the primary +agent [54]. For sub-agent tasks within stages, Opus 4.6 delegates to Claude Sonnet 4.6 through its Agent Teams +capability, which coordinates multiple agents working in parallel from a single orchestrator. + +A detail worth noting: Opus 4.6 uses the workspace’s own context files, the CONTEXT.md hierarchy and Layer 3 +reference material, to fill prompts for its sub-agents. The model reads the folder structure to determine what +context each sub-agent should receive and what task it should perform. This means the ICM architecture is doing +double duty. It structures context for the primary agent, and it provides the specification that the primary agent +uses to delegate work. The folder hierarchy is both the human’s control surface and the model’s orchestration +logic. + +ICM is designed to be model-agnostic. The protocol specifies folder structure, file formats, and naming +conventions. It does not depend on any model-specific capability. A workspace built for Claude could be run +with a different model by pointing that model at the same files. Whether the results would be equivalent is an +empirical question that depends on how different models handle the same context, but the protocol itself imposes +no vendor lock-in. The workspaces described below were tested with the models listed above. + +4.2 +Script-to-Animation Pipeline + +The first workspace built on ICM takes a content idea through three stages to produce a working animated video. + +Stage 1 (01_research) takes a topic and produces structured research output: key points, narrative angles, +supporting data. The agent reads a research brief from the user and writes a research document to its output +folder. + +5All workspaces referenced here are available or buildable through the ICM repository at [https://github.com/RinDig/Interpretable-Context-](https://github.com/RinDig/Interpretable-Context-Methodology-ICM-) +[Methodology-ICM-](https://github.com/RinDig/Interpretable-Context-Methodology-ICM-)[.](https://github.com/RinDig/Interpretable-Context-Methodology-ICM-) + + + +• +11 + +Stage 2 (02_script) reads the research output and writes a script. The stage’s CONTEXT.md points the agent to +a voice guide and structural template in the _config/ folder. The script follows the user’s established tone and +format. + +Stage 3 (03_production) reads the finished script and produces animation specifications and working Re- +motion6 code. The stage’s context includes design guidelines, color palettes, and animation conventions from +setup. + +At each stage boundary, the human reviews the output. A research document that misses an important angle +gets edited before the script stage runs. A script that runs too long gets trimmed before the production stage sees +it. The agent at each stage works with whatever the human left in the previous output folder. + +This workspace runs on a single Claude Code session. One orchestrating agent (Opus 4.6) manages the pipeline, +delegating sub-tasks within stages to faster sub-agents (Sonnet 4.6) as described in Section 4.1. The delegation is +itself driven by the folder structure: the orchestrating agent reads the stage’s CONTEXT.md to determine what +work to delegate and what context to provide. There is no separate orchestration framework. The same folder +hierarchy that tells the human what each stage does tells the agent how to coordinate its sub-agents. In compiler +terms, the workspace performs multi-pass compilation: the processing engine runs multiple times, producing a +different intermediate representation at each pass, with the folder structure determining which pass runs next. + +4.3 +Course Deck Production + +A second workspace takes unstructured source material (PDFs, papers, lecture notes, rough outlines) and produces +polished PowerPoint slide decks through five stages: content extraction, structural planning, slide drafting, visual +design specification, and final assembly. + +The five-stage structure matters because slide deck production is a process where human judgment is essential +at several points. The structural plan (stage 2 output) determines the entire arc of the presentation. Getting it +wrong means everything downstream is wrong. By surfacing the structural plan as an editable markdown file +before any slides are drafted, ICM lets the human course-correct at the point where correction is cheapest and +most effective. + +4.4 +Building New Workspaces +ICM includes a workspace-builder: a five-stage workspace whose output is a new workspace. It walks through +discovery (what is the domain, what is the workflow), stage mapping (where are the natural breakpoints), +scaffolding (creating the folder structure), questionnaire design (what setup questions should the workspace ask), +and validation (does the pipeline run end to end). + +The workspace-builder itself follows ICM conventions. The workspaces it produces are consistent because the +builder enforces the same structural rules it was built with. + +This means practitioners can create new workspaces for their own domains without understanding the +underlying conventions in detail. The builder encodes the conventions into its process. A marketing team can +build a workspace for campaign production. A research group can build one for literature review and synthesis. +A consultancy can build one for client deliverable pipelines. Each workspace is a folder they own and control. + +ICM workspaces have been adopted by groups outside the author’s organization. Researchers at the University +of Edinburgh’s Neuropolitics Lab have built workspaces for their domain, and teams at ICR Research and the +Academy of International Affairs in Bonn are developing workspaces for their own workflows. The details of these +implementations are limited by nondisclosure agreements, but their existence is noted here because the reviewer’s +natural question, does ICM work when someone other than its designer builds and operates the workspace, has at + +6Remotion is a React-based framework for creating videos programmatically. + + + +12 +• + +Almost always +**92%** + +Frequency of human edits + +Often +**78%** + +Sometimes + +Rarely +**30%** + +Never + +Stage 1 output + +Stage 2 output + +(Research) +(Script) +Stage 3 output (Production) + +Fig. 5. Observed frequency of human edits at each stage boundary, reported by 33 practitioners using multi-stage ICM +workspaces. Intervention follows a U-shaped pattern: heavy at stage 1 (direction-setting), light at middle stages (constrained +execution), heavy again at the final stage (aligning output with earlier decisions). Stage 1 editing is creative judgment. +Final-stage editing is closer to debugging. Values are approximate and based on practitioner self-report through conversation, +not instrumented measurement. + +least a preliminary answer: yes, across academic research, policy analysis, and content production. A structured +study of these external deployments is a clear next step. + +4.5 +Early Practitioner Experience + +ICM has been used in production across content creation, training material development, research analysis, and +policy workflows. The observations reported here are drawn from an invite-only practitioner community of 52 +members whose backgrounds range from AI engineers and software developers to business owners, content +creators, and academic researchers. These observations come from ongoing conversations with community +members rather than from formal data collection protocols. They should be read as practitioner reports rather +than controlled findings, but they reflect a broader base of experience than the author’s own use alone. + +The most consistent observation is where people choose to intervene (Figure 5). Across 33 community members +who have used the script-to-animation workspace or structurally similar multi-stage workspaces, 30 report an +intervention pattern consistent with a U-shape: heavy editing at stage 1 (direction-setting), light editing at the +middle stages, and heavy editing again at the final stage (aligning output with earlier decisions). The remaining +three report roughly equal editing across all stages. These numbers come from practitioner conversations, not +from instrumented measurement, and should be interpreted accordingly. + +The two peaks reflect different kinds of editing. Stage 1 editing is directional: the user is narrowing from broad +possibilities to a specific angle, deciding what the piece is about. This is creative judgment. Final-stage editing is +alignment work: the user is checking that the output faithfully represents decisions made in earlier stages. This is +closer to debugging. The practitioner traces a misalignment in the output back through the pipeline to find where +it diverged from the source material. Section 6 explores what tooling for this kind of traceability might look like. + +The middle stages get the lightest touch because they sit between well-defined anchors. The earlier stage output +sets the direction. The reference material (Layer 3 voice guides, structural templates) constrains the execution. +With both anchors in place, the middle stages have less room to go wrong, and practitioners tend to trust them. +This aligns with Parasuraman, Sheridan, and Wickens’s observation that appropriate automation levels vary by +task function [42]. + + + +• +13 + +A second pattern involves prompt editing. Non-technical users, people without development experience, have +successfully modified stage behavior by editing the markdown CONTEXT.md files. Changes include adjusting tone +instructions, adding constraints (“keep scripts under 90 seconds”), and reordering the emphasis within a stage’s +process description. These edits would be equivalent to modifying agent configuration in a framework-based +system, a task that typically requires a developer. The plain-text interface lowers this barrier in practice. + +A third pattern is worth noting for its implications about accessibility. Three community members with no prior +coding experience and no previous exposure to Claude Code used the ICM workspace-builder’s questionnaire +and setup process to create and run workspaces that produced ten-minute animated videos from scripts. They +edited CONTEXT.md files, reviewed stage outputs, and iterated on their workspaces without developer assistance. +This is a single data point from a small group, but it suggests that the filesystem interface can make AI agent +orchestration accessible to people who would not be able to use a framework-based system at all. + +A fourth pattern is workspace duplication. Users who have a working workspace for one content format (say, +short explainer videos) duplicate the folder, modify the stage prompts to target a different format (say, long-form +essays), and run the new workspace without rebuilding from scratch. The workspace-builder supports creating +workspaces from nothing, but in practice people often prefer to copy and adapt an existing one. This mirrors +how Unix users build new shell scripts by modifying existing ones rather than starting from a blank file. + +These observations are drawn from a community of varied backgrounds across a growing but still limited set +of workflow types. A structured evaluation with formal data collection, systematic interviews, and controlled +comparisons would be needed to draw firm conclusions about the generality of these patterns. The observations +are reported here because they informed the protocol’s design evolution and because they suggest directions for +future study. + +4.6 +Threats to Validity +Several limitations constrain the conclusions that can be drawn from the current work, and naming them is +important for interpreting the results above. The practitioner community provides a broader evidence base than +single-author observation, but data collection has been informal: observations come from ongoing conversations +rather than structured interviews, diary studies, or instrumented usage logging. The community is invite-only and +self-selected, introducing both selection bias and potential enthusiasm bias. The reported intervention patterns +(30 of 33 practitioners observing a U-shape) are self-reported through conversation and have not been verified +through controlled measurement. + +While ICM has been adopted across content production, academic research, and policy analysis workflows, the +majority of active use remains concentrated in content production. The academic and policy deployments are +early-stage, and their outcomes cannot yet be reported in detail. All testing was conducted using a single model +family (Claude Opus 4.6 and Sonnet 4.6). Cross-model evaluation is a natural next step but falls outside the scope +of this paper, which focuses on the architectural pattern and its interaction properties rather than model-specific +performance. Output quality may vary with other models, particularly those with different context-handling +characteristics. + +No controlled comparison has been conducted between ICM’s staged context loading and a monolithic +prompting approach on the same tasks, so the claim that scoped context improves output quality rests on +the theoretical support from the “lost in the middle” literature [25] and practitioner judgment rather than +measured effect sizes. A formal user study with systematic data collection, structured interviews, and controlled +comparisons across varied workflow types and participant backgrounds would substantially strengthen the +empirical foundations of this work. + + + +14 +• + +5 +Discussion +5.1 +Where This Works +ICM handles sequential multi-step workflows where a human reviews output at each stage. In practice, the +protocol has been applied to content production pipelines (script-to-animation, short-form video), training material +development (slide deck generation from source material), academic research workflows (at the University of +Edinburgh and ICR Research), and policy analysis (at the Academy of International Affairs, Bonn). The common +thread across these deployments is that the workflows are sequential, the outputs benefit from human review at +each step, and the same pipeline runs repeatedly with different input. + +The common thread is that these workflows are sequential (step 2 follows step 1), reviewable (a human should +check each step’s output), and repeatable (the same pipeline runs weekly or daily with different input). For this +class of workflow, ICM provides full orchestration capability with no framework code, no server infrastructure, +and no developer dependency for day-to-day operation. + +5.2 +Where This Does Not Work + +ICM is not a replacement for multi-agent frameworks in every context. + +Real-time multi-agent collaboration, where agents need to communicate dynamically and respond to each +other’s outputs in tight loops, requires the kind of message-passing infrastructure that AutoGen [20] and similar +frameworks provide. ICM’s sequential, file-based handoffs are too slow for this. + +High-concurrency systems where many users hit the same pipeline simultaneously need proper queueing, +state isolation, and deployment infrastructure. ICM is local-first by design. Scaling it to concurrent users would +require building the infrastructure ICM was designed to avoid. + +Workflows that require complex branching logic based on AI decisions mid-pipeline are awkward in ICM. A +human can make branching decisions between stages (run stage 3a instead of 3b based on what they see in the +stage 2 output), but automated branching would require scripting that moves ICM toward being a framework +itself. + +These boundaries matter. The claim is not that ICM replaces existing tools across the board. The claim is that +for a large and common class of workflows, the existing tools provide more complexity than the problem requires, +and that complexity has real costs: opacity, fragility, developer dependency, and overhead that slows iteration. + +5.3 +Observability as a Side Effect +The most useful property of ICM may be one that was not designed as a feature. Because every intermediate +output is a plain file, the system is observable by default. There is no logging layer to build, no dashboard to +configure, no special tooling to inspect pipeline state. You open a folder and read the files. + +Rudin argued that inherently interpretable systems should be preferred over post-hoc explanations of opaque +ones [45]. ICM is a glass-box AI workflow. It did not become transparent through the addition of an explanation +layer. It was never opaque in the first place, because every artifact is a plain-text file that a human can read. + +Amershi et al.’s guidelines for human-AI interaction include “make clear what the system can do,” “support +efficient correction,” and “support efficient dismissal” [47]. Stage contracts make capabilities explicit. Markdown +files support efficient correction (open, edit, save). Review gates at every stage boundary support dismissal (decide +not to proceed, re-run the previous stage with different input, or abandon the run entirely). + +The regulatory landscape may also be relevant here. The EU AI Act’s human oversight requirements [49, 50] +emphasize staged review, audit trails, and defined intervention points. ICM produces these as a byproduct of +its architecture: there is no way to run an ICM pipeline without generating inspectable intermediate artifacts, +because the intermediate artifacts are how the stages communicate. Whether this constitutes compliance with + + + +• +15 + +specific regulatory requirements is a legal question this paper does not attempt to answer, but the structural +alignment is worth noting. + +5.4 +Implications for Intelligent System Design + +The discussion so far has focused on how ICM structures the human side of human-AI interaction: edit surfaces, +review gates, observability. But the architecture also has implications for how the intelligent system itself performs, +and these are worth examining. + +The core mechanism is context scoping. By delivering different context to the same model at each stage, ICM +changes the task the model is performing. A model that receives research instructions, source material, and a +topic brief behaves differently from the same model receiving a script template, a voice guide, and a research +summary. The model’s capabilities do not change between stages. What changes is the information it has available +when generating output. This is context engineering in practice: the performance of the system depends on what +context is delivered, in what structure, and at what moment. + +The Layer 3/Layer 4 distinction adds a further dimension. Reference material (Layer 3) and working artifacts +(Layer 4) ask different things of the model. Reference material says: here are the rules, follow them. Working +artifacts say: here is the input, transform it. Delivering these as structurally separate context, rather than mixing +them in a single undifferentiated prompt, gives the model clearer signals about which information constrains its +behavior and which information it should act on. Whether this structural separation measurably improves output +quality compared to a flat context of equivalent content is an open empirical question, but early practitioner +experience suggests that stages where reference and working material are clearly separated produce more +consistent adherence to style and format guidelines. + +This raises a question about the relationship between context structure and output quality. In early use, a +pattern emerged: stages with tightly scoped context (clear instructions, limited reference material, a specific +output format) produced more consistent results than stages with broad context (open-ended instructions, large +volumes of reference material, loosely defined output expectations). This is consistent with the “lost in the middle” +findings [25] and with the chain-of-thought literature showing that decomposed tasks outperform monolithic +ones [27], but it suggests something more specific. The structure of the context delivery, how information is +organized and bounded, may matter as much as the content of the context itself. ICM’s folder-based scoping +enforces this structure by default: each stage folder contains only what that stage needs, and the boundaries are +visible and editable. + +There are open questions here that the current work does not answer. First, does the five-layer hierarchy +(workspace identity, task routing, stage contracts, reference material, working artifacts) generalize across model +families, or is it tuned to the specific attention patterns of the models tested? The protocol is designed to be +model-agnostic (Section 4.1), but all current testing has been conducted on a single model family. Cross-model +evaluation, running the same workspace on Claude, GPT, Gemini, and open-weight models such as Llama, is a +clear next step. This paper scopes that question as future work because the present contribution is the architectural +pattern and its interaction properties, not a model-specific performance claim. Second, as context windows grow +larger, does selective loading become less important? If a model can reliably attend to 200,000 tokens without +degradation, the engineering argument for ICM’s scoping weakens, though the human-interaction arguments +(observability, editability, review gates) remain. Third, how sensitive is stage output quality to the ordering and +formatting of context within a layer? The current protocol specifies what files a stage should load but does not +prescribe the order in which they appear in the context window. Whether ordering matters at the scale of ICM’s +typical context sizes (2,000 to 8,000 tokens per stage) is an empirical question worth investigating. + +These questions point toward a research program that sits at the intersection of context engineering and +interaction design: understanding how the structure of information delivery to language models affects both the + + + +16 +• + +model’s output quality and the human’s ability to steer, inspect, and correct that output. ICM provides a concrete +platform for investigating these questions because its architecture makes the context structure explicit, editable, +and observable at every stage. + +6 +Future Directions: Compilation, Debugging, and Source Integrity +The previous sections describe ICM as it currently works in production. This section describes where it should +go next. The ideas here are informed by early practitioner experience and by a structural analogy that the paper +has not yet drawn: the relationship between ICM workspaces and multi-pass compilers. + +6.1 +ICM as Multi-Pass Incremental Compilation + +The paper has grounded ICM in Unix pipelines, Make, and the pipe-and-filter pattern. There is a closer analogy +that deserves attention: multi-pass compilation [52]. + +A multi-pass compiler transforms source code through a sequence of discrete passes. The lexer produces tokens. +The parser produces a syntax tree. Semantic analysis annotates the tree. Optimization passes rewrite it. Code +generation produces the final output. Each pass reads the output of the previous pass, transforms it according +to its own rules, and writes an intermediate representation that the next pass can consume. The intermediate +representations are well-defined, inspectable, and (in debugging builds) preserved for examination. + +ICM does the same thing with content. Stage 1 (research) transforms a topic brief into structured research +output. Stage 2 (script) transforms the research output into a script. Stage 3 (production) transforms the script +into animation specifications and code. Each stage reads the previous stage’s output, applies its own context and +instructions, and writes an intermediate artifact that the next stage consumes. The intermediate artifacts are +plain files that can be opened, read, and edited. + +The analogy extends further. Incremental compilation means recompiling only the parts of the program +that changed, rather than rebuilding from scratch. ICM supports this by default: if the research output is fine +but the script needs rework, the practitioner re-runs stage 2 without touching stage 1. If a voice guide in the +reference material changes, only the stages that load that file need to run again. The folder structure tracks these +dependencies implicitly: a stage’s Inputs table declares which files it reads, and a change to any of those files +signals that the stage’s output may be stale. + +This is worth naming because it connects ICM to a body of compiler engineering that has spent fifty years +solving the problems of pass decomposition, intermediate representation design, and selective recompilation. +The current paper draws from Unix and software architecture. Future work should draw from compiler theory as +well, particularly around dependency tracking, change propagation, and the formal properties of intermediate +representations. + +6.2 +Toward Semantic Debugging + +Traditional debugging rests on a simple principle: when the output is wrong, trace the failure back through the +program’s execution to find the instruction that caused it [53]. Debuggers provide tools for this: breakpoints that +pause execution at specific instructions, stack traces that show the call chain, variable inspection that shows +state at each point, and source maps that connect compiled output back to the original source. + +ICM currently provides observability but not traceability. A practitioner can open any stage’s output folder +and read what the agent produced. But if a phrase in the stage 3 output sounds wrong, there is no direct way +to trace that phrase back to the specific instruction, reference file, or previous stage output that caused it. The +practitioner has to do this manually: read the stage 3 contract, check which files it loaded, read those files, and +form a judgment about which source is responsible. This works. It is how most ICM debugging happens today. +But it is the equivalent of debugging a program by reading the source code and thinking hard, without a debugger. + + + +• +17 + +The question is what a debugger for semantic content would look like. Several directions are worth exploring. +**Output provenance through identifiers.** If each section of a stage’s output carried an identifier linking it to +the source instruction or reference file that produced it, a practitioner could trace backward from any part of +the output to the context that generated it. In compiler terms, this is the equivalent of debug symbols or source +maps: metadata that connects output back to source without changing the output itself. In practice, this could +mean embedding lightweight markers (GUIDs, section tags, or comment annotations) in stage output files that +reference specific sections of the stage’s CONTEXT.md or Layer 3 reference files. + +**Cross-stage trace verification.** In the script-to-animation workspace described in Section 4, one recurring +problem has been misalignment between the animation specification (stage 3 output) and the script (stage 2 +output). Timing drifts. Animations reference phrases that were revised. Visual density does not match pacing. +This is the source of the U-shaped intervention pattern observed in Section 4.4: the stage 3 editing that brings +intervention back up is almost entirely alignment work, tracing the final output back through the pipeline to find +where it diverged from earlier decisions. The current solution is an audit file that forces the agent to trace back +from the specification to the original script, re-verifying timing for each phrase and flagging inconsistencies. +This works well enough that it catches most alignment errors, and the errors it catches are remarkably consistent +in kind: frame count discrepancies, visual density mismatches, and pacing breaks at scene boundaries. + +This audit file is a proto-debugger. It implements a specific kind of cross-stage verification: checking that the +output of stage *𝑛*is consistent with the output of stage *𝑛*−2 by re-reading both and comparing them against +defined criteria. The pattern could be generalized. A stage contract could include a Verify section alongside its +Inputs, Process, and Outputs sections, specifying which earlier stage outputs should be checked for consistency +and what criteria to check against. The agent would run these verification checks as part of the stage’s execution +and flag discrepancies before the human reviews. + +**Breakpoints in markdown.** The most speculative direction involves something like breakpoints for mark- +down files. In a traditional debugger, a breakpoint says “pause here and let me inspect the state.” In ICM, a +breakpoint in a CONTEXT.md file might say “after the agent processes this instruction, show me what it produced +before continuing.” This would be particularly useful in stages with complex instructions where the practitioner +wants to verify that the agent interpreted a specific constraint correctly before it finishes the rest of the stage’s +work. It turns a single-pass stage into a sequence of verifiable sub-steps. + +These ideas are not yet implemented. They are described here because the gap they address, the ability to trace +output back to source, is a gap that compiler engineering solved decades ago and that ICM will need to solve as +workspaces grow more complex. + +6.3 +Source Integrity and the Edit-Source Principle +The current paper describes ICM’s review gates as places where practitioners edit stage output. This is useful +and it works. But there is an argument, drawn directly from software engineering practice, that the source files +should be what improves over time, and that editing output is treating symptoms rather than causes. + +The argument is straightforward. If a script sounds wrong at stage 2, there are two possible responses. The +first is to edit the script directly: fix the tone, adjust the phrasing, move on. The second is to ask why the script +sounds wrong and trace the problem back to the source that produced it. Maybe the voice guide in the reference +material is underspecified. Maybe the stage contract’s instructions emphasize the wrong quality. Maybe the +research output from stage 1 framed the topic in a way that led the script in the wrong direction. Editing the +output fixes this run. Editing the source fixes every future run. + +In compiler terms, editing the output is patching the binary. It works, but it does not improve the compiler. A +developer who finds a bug in compiled code traces it back to the source and fixes it there, so that every subsequent +build is correct. + + + +18 +• + +For ICM, the tension is real. Creative content is fuzzier than compiled code. Sometimes the output needs a +human touch that cannot be reduced to a source-level rule. A script might benefit from a turn of phrase that no +amount of voice guide refinement would have produced. Editing the output in that case is the right move. The +practitioner is adding value that the system cannot generate on its own. + +But there is a class of output edits that are diagnostic. If the practitioner consistently tightens the opening +paragraph, that is a signal that the stage contract should say “keep the opening under three sentences.” If the +tone drifts formal every time, that is a signal that the voice guide needs a stronger example of the target register. +These recurring edits are debugging information. They point to fixable source-level problems. + +A future version of ICM could support this by tracking output edits across runs. If a practitioner edits the same +kind of thing in the same stage’s output three runs in a row, the system could surface that pattern and suggest a +source-level change: a contract amendment, a reference file update, a new constraint. This would close the loop +between output editing and source improvement, turning one-off fixes into durable system improvements. + +The principle matters because it addresses a question about ICM’s long-term trajectory. If workspaces are only +as good as the last human edit of their output, they remain tools. If workspaces improve their own source files +over time, incorporating the patterns they learn from human corrections, they become systems that get better +with use. The debugging and traceability infrastructure described in the previous subsection is a prerequisite for +this: you cannot improve the source if you cannot trace the problem back to it. + +7 +Conclusion +The principles that made Unix pipelines effective in the 1970s apply to AI agent orchestration in the 2020s. +Programs that do one thing. Output of one becomes input of another. Plain text as universal interface. Human- +readable intermediate state. + +ICM applies these principles to a specific problem: structuring context for AI agents across multi-step workflows. +The result is a system where the folder structure replaces the framework. One agent reads different context at +each stage rather than multiple agents coordinating through code. Local scripts handle the mechanical work that +does not need AI. Every intermediate output is a file a human can read and edit. + +For practitioners whose AI workflows are sequential, reviewable, and repeatable, this means full pipeline +capability with no framework to learn, no server to maintain, and no developer needed for day-to-day operation. +The workspace is a folder. It can be copied, versioned, shared, and edited with a text editor. The simplest viable +architecture for this class of problem is one that already exists on every computer: the filesystem. + +The protocol is open source under the MIT license and includes a workspace-builder for creating new +workspaces across any domain. + +References + +[1] M. D. McIlroy, E. N. Pinson, and B. A. Tague, “Unix Time-Sharing System: Foreword,” *The Bell System Technical Journal*, vol. 57, no. 6, + +part 2, pp. 1902–1903, 1978. +[2] D. M. Ritchie and K. Thompson, “The UNIX Time-Sharing System,” *Communications of the ACM*, vol. 17, no. 7, pp. 365–375, 1974. + +DOI: [https://doi.org/10.1145/361011.361061](https://doi.org/10.1145/361011.361061) +[3] P. H. Salus, *A Quarter Century of Unix*. Addison-Wesley, 1994. ISBN: 0-201-54777-5. +[4] E. S. Raymond, *The Art of Unix Programming*. Addison-Wesley Professional, 2003. ISBN: 0-13-142901-9. + +Available: [http://www.catb.org/esr/writings/taoup/html/](http://www.catb.org/esr/writings/taoup/html/) +[5] B. W. Kernighan and R. Pike, *The UNIX Programming Environment*. Prentice Hall, 1984. ISBN: 0-13-937681-X. +[6] M. Shaw and D. Garlan, *Software Architecture: Perspectives on an Emerging Discipline*. Prentice Hall, 1996. ISBN: 0-13-182957-2. +[7] S. I. Feldman, “Make — A Program for Maintaining Computer Programs,” *Software: Practice and Experience*, vol. 9, no. 4, pp. 255–265, + +1979. +DOI: [https://doi.org/10.1002/spe.4380090402](https://doi.org/10.1002/spe.4380090402) +[8] E. W. Dijkstra, “On the Role of Scientific Thought,” Manuscript EWD447, 1974. Reprinted in *Selected Writings on Computing: A Personal* + +*Perspective*, pp. 60–66. Springer-Verlag, 1982. + + + +• +19 + +Available: [https://www.cs.utexas.edu/~EWD/transcriptions/EWD04xx/EWD447.html](https://www.cs.utexas.edu/~EWD/transcriptions/EWD04xx/EWD447.html) +[9] D. L. Parnas, “On the Criteria To Be Used in Decomposing Systems into Modules,” *Communications of the ACM*, vol. 15, no. 12, pp. 1053– + +1058, 1972. +DOI: [https://doi.org/10.1145/361598.361623](https://doi.org/10.1145/361598.361623) +[10] D. E. Knuth, “Literate Programming,” *The Computer Journal*, vol. 27, no. 2, pp. 97–111, 1984. + +DOI: [https://doi.org/10.1093/comjnl/27.2.97](https://doi.org/10.1093/comjnl/27.2.97) +[11] R. P. Gabriel, “The Rise of ‘Worse is Better’,” Originally part of “Lisp: Good News, Bad News, How to Win Big.” *AI Expert*, vol. 6, no. 6, + +pp. 33–35, 1991. +Available: [https://www.dreamsongs.com/WorseIsBetter.html](https://www.dreamsongs.com/WorseIsBetter.html) +[12] R. Pike, D. Presotto, S. Dorward, B. Flandrena, K. Thompson, H. Trickey, and P. Winterbottom, “Plan 9 from Bell Labs,” *Computing* + +*Systems*, vol. 8, no. 3, pp. 221–254, 1995. +Available: [https://css.csail.mit.edu/6.824/2014/papers/plan9.pdf](https://css.csail.mit.edu/6.824/2014/papers/plan9.pdf) +[13] S. Chacon and B. Straub, *Pro Git*, 2nd ed. Apress, 2014. ISBN: 978-1-4842-0076-6. + +Available: [https://git-scm.com/book](https://git-scm.com/book) +[14] K. Morris, *Infrastructure as Code: Dynamic Systems for the Cloud Age*, 2nd ed. O’Reilly Media, 2021. ISBN: 978-1-098-11467-1. +[15] J. Humble and D. Farley, *Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation*. Addison-Wesley + +Professional, 2010. ISBN: 978-0-321-60191-9. +[16] A. Karpathy, “+1 for ‘context engineering’ over ‘prompt engineering’...,” X (formerly Twitter), June 25, 2025. + +Available: [https://x.com/karpathy/status/1937902205765607626](https://x.com/karpathy/status/1937902205765607626) +[17] L. Martin, “Context Engineering,” LangChain Blog, July 2, 2025. + +Available: [https://blog.langchain.com/context-engineering-for-agents/](https://blog.langchain.com/context-engineering-for-agents/) +[18] S. Willison, “Context Engineering,” *Simon Willison’s Weblog*, June 27, 2025. + +Available: [https://simonwillison.net/2025/jun/27/context-engineering/](https://simonwillison.net/2025/jun/27/context-engineering/) +[19] DAIR.AI, “Context Engineering Guide,” *Prompting Guide*, 2025. + +Available: [https://www.promptingguide.ai/guides/context-engineering-guide](https://www.promptingguide.ai/guides/context-engineering-guide) +[20] Q. Wu, G. Bansal, J. Zhang, Y. Wu, B. Li, E. Zhu, L. Jiang, X. Zhang, S. Zhang, A. Awadallah, R. W. White, D. Burger, and C. Wang, + +“AutoGen: Enabling Next-Gen LLM Applications via Multi-Agent Conversation,” *COLM 2024*, arXiv:2308.08155, August 2023. + +Available: [https://arxiv.org/abs/2308.08155](https://arxiv.org/abs/2308.08155) +[21] H. Chase, *LangChain* [open-source framework]. First released October 2022. + +Available: [https://github.com/langchain-ai/langchain](https://github.com/langchain-ai/langchain) +[22] J. S. Park, J. C. O’Brien, C. J. Cai, M. R. Morris, P. Liang, and M. S. Bernstein, “Generative Agents: Interactive Simulacra of Human + +Behavior,” *Proceedings of UIST ’23*. ACM, 2023. +DOI: [https://doi.org/10.1145/3586183.3606763](https://doi.org/10.1145/3586183.3606763) +[23] Anthropic, “Introducing the Model Context Protocol,” Anthropic Blog, November 25, 2024. + +Available: [https://www.anthropic.com/news/model-context-protocol](https://www.anthropic.com/news/model-context-protocol) +[24] A. Jones and C. Kelly, “Code Execution with MCP,” Anthropic Engineering Blog, 2025. + +Available: [https://www.anthropic.com/engineering/code-execution-with-mcp](https://www.anthropic.com/engineering/code-execution-with-mcp) +[25] N. F. Liu, K. Lin, J. Hewitt, A. Paranjape, M. Bevilacqua, F. Petroni, and P. Liang, “Lost in the Middle: How Language Models Use Long + +Contexts,” *Transactions of the Association for Computational Linguistics*, vol. 12, pp. 157–173, 2024. +Available: [https://arxiv.org/abs/2307.03172](https://arxiv.org/abs/2307.03172) +[26] T. Wu, M. Terry, and C. J. Cai, “AI Chains: Transparent and Controllable Human-AI Interaction by Chaining Large Language Model + +Prompts,” *CHI Conference on Human Factors in Computing Systems (CHI ’22)*. ACM, 2022. +DOI: [https://doi.org/10.1145/3491102.3517582](https://doi.org/10.1145/3491102.3517582) +[27] J. Wei, X. Wang, D. Schuurmans, M. Bosma, B. Ichter, F. Xia, E. Chi, Q. V. Le, and D. Zhou, “Chain-of-Thought Prompting Elicits + +Reasoning in Large Language Models,” *NeurIPS 2022*. +Available: [https://arxiv.org/abs/2201.11903](https://arxiv.org/abs/2201.11903) +[28] T. Schick, J. Dwivedi-Yu, R. Dessì, R. Raileanu, M. Lomeli, L. Zettlemoyer, N. Cancedda, and T. Scialom, “Toolformer: Language Models + +Can Teach Themselves to Use Tools,” *NeurIPS 2023*. +Available: [https://arxiv.org/abs/2302.04761](https://arxiv.org/abs/2302.04761) +[29] S. G. Patil, T. Zhang, X. Wang, and J. E. Gonzalez, “Gorilla: Large Language Model Connected with Massive APIs,” *NeurIPS* *2024*, + +arXiv:2305.15334, 2023. +Available: [https://arxiv.org/abs/2305.15334](https://arxiv.org/abs/2305.15334) +[30] P. Lewis, E. Perez, A. Piktus, F. Petroni, V. Karpukhin, N. Goyal, H. Küttler, M. Lewis, W.-t. Yih, T. Rocktäschel, S. Riedel, and D. Kiela, + +“Retrieval-Augmented Generation for Knowledge-Intensive NLP Tasks,” *NeurIPS 2020*, pp. 9459–9474. + +Available: [https://arxiv.org/abs/2005.11401](https://arxiv.org/abs/2005.11401) + + + +20 +• + +[31] H. Jiang, Q. Wu, C.-Y. Lin, Y. Yang, and L. Qiu, “LLMLingua: Compressing Prompts for Accelerated Inference of Large Language Models,” + +*EMNLP 2023*, pp. 13358–13376. +DOI: [https://doi.org/10.18653/v1/2023.emnlp-main.825](https://doi.org/10.18653/v1/2023.emnlp-main.825) +[32] H. Jiang, Q. Wu, X. Luo, D. Li, C.-Y. Lin, Y. Yang, and L. Qiu, “LongLLMLingua: Accelerating and Enhancing LLMs in Long Context + +Scenarios via Prompt Compression,” *ACL 2024*, pp. 1658–1677. +Available: [https://arxiv.org/abs/2310.06839](https://arxiv.org/abs/2310.06839) +[33] Addyo, “Context Engineering: Bringing Engineering Discipline to Prompts,” Substack, 2025. + +Available: [https://addyo.substack.com/p/context-engineering-bringing-engineering](https://addyo.substack.com/p/context-engineering-bringing-engineering) +[34] S. Amershi, M. Cakmak, W. B. Knox, and T. Kulesza, “Power to the People: The Role of Humans in Interactive Machine Learning,” *AI* + +*Magazine*, vol. 35, no. 4, pp. 105–120, 2014. +DOI: [https://doi.org/10.1609/aimag.v35i4.2513](https://doi.org/10.1609/aimag.v35i4.2513) +[35] J. A. Fails and D. R. Olsen, Jr., “Interactive Machine Learning,” *Proceedings of IUI ’03*, pp. 39–45. ACM, 2003. + +DOI: [https://doi.org/10.1145/604045.604056](https://doi.org/10.1145/604045.604056) +[36] J. J. Dudley and P. O. Kristensson, “A Review of User Interface Design for Interactive Machine Learning,” *ACM Transactions on Interactive* + +*Intelligent Systems*, vol. 8, no. 2, Article 8, pp. 1–37, 2018. +DOI: [https://doi.org/10.1145/3185517](https://doi.org/10.1145/3185517) +[37] E. Horvitz, “Principles of Mixed-Initiative User Interfaces,” *CHI ’99*, pp. 159–166. ACM, 1999. + +DOI: [https://doi.org/10.1145/302979.303030](https://doi.org/10.1145/302979.303030) +[38] M. T. Ribeiro, S. Singh, and C. Guestrin, “‘Why Should I Trust You?’: Explaining the Predictions of Any Classifier,” *KDD ’16*, pp. 1135–1144. + +ACM, 2016. +DOI: [https://doi.org/10.1145/2939672.2939778](https://doi.org/10.1145/2939672.2939778) +[39] S. M. Lundberg and S.-I. Lee, “A Unified Approach to Interpreting Model Predictions,” *NeurIPS 2017*, pp. 4765–4774. + +Available: [https://papers.nips.cc/paper/7062-a-unified-approach-to-interpreting-model-predictions](https://papers.nips.cc/paper/7062-a-unified-approach-to-interpreting-model-predictions) +[40] J. D. Lee and K. A. See, “Trust in Automation: Designing for Appropriate Reliance,” *Human Factors*, vol. 46, no. 1, pp. 50–80, 2004. + +DOI: [https://doi.org/10.1518/hfes.46.1.50_30392](https://doi.org/10.1518/hfes.46.1.50_30392) +[41] R. Parasuraman and V. Riley, “Humans and Automation: Use, Misuse, Disuse, Abuse,” *Human Factors*, vol. 39, no. 2, pp. 230–253, 1997. + +DOI: [https://doi.org/10.1518/001872097778543886](https://doi.org/10.1518/001872097778543886) +[42] R. Parasuraman, T. B. Sheridan, and C. D. Wickens, “A Model for Types and Levels of Human Interaction with Automation,” *IEEE* + +*Transactions on Systems, Man, and Cybernetics — Part A*, vol. 30, no. 3, pp. 286–297, 2000. +DOI: [https://doi.org/10.1109/3468.844354](https://doi.org/10.1109/3468.844354) +[43] B. Shneiderman, “Human-Centered Artificial Intelligence: Reliable, Safe & Trustworthy,” *International Journal of Human–Computer* + +*Interaction*, vol. 36, no. 6, pp. 495–504, 2020. +DOI: [https://doi.org/10.1080/10447318.2020.1741118](https://doi.org/10.1080/10447318.2020.1741118) +[44] B. Shneiderman, *Human-Centered AI*. Oxford University Press, 2022. ISBN: 978-0192845290. +[45] C. Rudin, “Stop Explaining Black Box Machine Learning Models for High Stakes Decisions and Use Interpretable Models Instead,” *Nature* + +*Machine Intelligence*, vol. 1, pp. 206–215, 2019. +DOI: [https://doi.org/10.1038/s42256-019-0048-x](https://doi.org/10.1038/s42256-019-0048-x) +[46] B. Shneiderman, “Direct Manipulation: A Step Beyond Programming Languages,” *IEEE Computer*, vol. 16, no. 8, pp. 57–69, 1983. + +DOI: [https://doi.org/10.1109/MC.1983.1654471](https://doi.org/10.1109/MC.1983.1654471) +[47] S. Amershi, D. Weld, M. Vorvoreanu, A. Fourney, B. Nushi, P. Collisson, J. Suh, S. Iqbal, P. N. Bennett, K. Inkpen, J. Teevan, R. Kikin-Gil, + +and E. Horvitz, “Guidelines for Human-AI Interaction,” *CHI 2019*, Article 3, pp. 1–13. ACM, 2019. +DOI: [https://doi.org/10.1145/3290605.3300233](https://doi.org/10.1145/3290605.3300233) +[48] M. Zaharia, A. Chen, A. Davidson, A. Ghodsi, S. A. Hong, A. Konwinski, S. Murching, T. Nykodym, P. Ogilvie, M. Parkhe, F. Xie, and + +C. Zumar, “Accelerating the Machine Learning Lifecycle with MLflow,” *IEEE Data Engineering Bulletin*, vol. 41, no. 4, pp. 39–45, 2018. +Available: [https://people.eecs.berkeley.edu/~matei/papers/2018/ieee_mlflow.pdf](https://people.eecs.berkeley.edu/~matei/papers/2018/ieee_mlflow.pdf) +[49] L. Enqvist, “‘Human Oversight’ in the EU Artificial Intelligence Act,” *The Theory and Practice of Legislation*, vol. 11, no. 3, 2023. + +DOI: [https://doi.org/10.1080/17579961.2023.2245683](https://doi.org/10.1080/17579961.2023.2245683) +[50] C. Novelli, F. Casolari, A. Rotolo, M. Taddeo, and L. Floridi, “Institutionalised Distrust and Human Oversight of Artificial Intelligence,” + +*Digital Society*, vol. 3, no. 8, 2024. +Available: [https://pmc.ncbi.nlm.nih.gov/articles/PMC11614927/](https://pmc.ncbi.nlm.nih.gov/articles/PMC11614927/) +[51] M. Fink, “Human Oversight under Article 14 of the EU AI Act,” SSRN: 5147196, 2025. Forthcoming in Malgieri et al. (eds.), *AI Act* + +*Commentary*. Hart-Bloomsbury, 2026. +DOI: [https://doi.org/10.2139/ssrn.5147196](https://doi.org/10.2139/ssrn.5147196) +[52] A. V. Aho, M. S. Lam, R. Sethi, and J. D. Ullman, *Compilers:* *Principles,* *Techniques,* *and* *Tools*, 2nd ed. Addison-Wesley, 2006. ISBN: + +978-0-321-48681-3. + + + +• +21 + +[53] A. Zeller, *Why Programs Fail: A Guide to Systematic Debugging*, 2nd ed. Morgan Kaufmann, 2009. ISBN: 978-0-12-374515-6. +[54] Anthropic, “Introducing Claude Opus 4.6,” [https://www.anthropic.com/news/claude-opus-4-6](https://www.anthropic.com/news/claude-opus-4-6), February 2026. diff --git a/README.md b/README.md new file mode 100644 index 0000000..4f527b1 --- /dev/null +++ b/README.md @@ -0,0 +1,94 @@ +# Tool Catalog + +This README catalogs the tools and resources in this directory. It is intended for humans and LLM agents to quickly identify what is available and when to use it. + +## Catalog + +| Tool / Folder | Purpose | Key Files | When to Use | +| --- | --- | --- | --- | +| `tool-catalog-maintainer/` | Creates and maintains catalog READMEs for directories of tools/resources. | `SKILL.md`, `CONTEXT.md`, `references/catalog-format.md` | Use when asked to catalog, index, or update documentation for a folder of tools. | +| `research-dfns/` | DFNS research folder — alerts logs, chat log, and TODO tracking. | `TODO.md`, `AlertsLog_*.txt`, `ChatLog_*.txt` | Use when reviewing or continuing DFNS research. | +| `260731-1330-credit-spread.md` | SPY Bull Put Credit Spread trade plan (0DTE, July 31). | `260731-1330-credit-spread.md` | Use for today's SPY options trade — bullish slow grind thesis. | +| `iron-condor-45dte.md` | SPX Iron Condor trade plan — 45DTE entry, 21DTE time exit, Schwab broker. | `iron-condor-45dte.md` | Use when setting up or managing SPX iron condor spreads. | +| `cha-martin-watchlist.ms.csv` | Cha Martin watchlist export (CSV). | `cha-martin-watchlist.ms.csv` | Use for ticker watchlist reference or scan filtering. | + +## Tools + +### `tool-catalog-maintainer/` + +**Purpose:** +Creates and maintains a `README.md` catalog for a directory containing subfolders of tools, prompts, scripts, docs, workflows, skills, or other reusable resources. The README is a living catalog that improves over time. + +**Contents:** +- `SKILL.md` — skill definition and workflow +- `CONTEXT.md` — full context: inputs, process, outputs, verification +- `references/catalog-format.md` — catalog README structure and cataloging rules +- `output/` — generated artifacts + +**Use when:** +You need to catalog, index, summarize, or update documentation for a folder of tools so humans or LLM agents can quickly choose the right resource. + +**Setup / dependencies:** +None noted. Works with file read/write tools. + +**Notes:** +Always use this tool when asked to catalog a directory — inspect subfolders, read their key files, and write the README using `references/catalog-format.md`. + +### `research-dfns/` + +**Purpose:** +Research folder for DFNS (Digital Frontier Acquisition Corp.) — contains alert logs, chat transcripts, and tracking notes from July 27, 2026. + +**Contents:** +- `TODO.md` — research tracking tasks +- `AlertsLog_Mon Jul 27 2026*.txt` — alert logs (3 files) +- `ChatLog_Mon Jul 27 2026.txt` — chat transcript + +**Use when:** +Reviewing or continuing DFNS research. Note: per ticker tracking rule, DFNS should not be actively tracked unless a fresh positive reason arises. + +**Setup / dependencies:** +None noted. + +### `260731-1330-credit-spread.md` + +**Purpose:** +Active trade plan for a SPY Bull Put Credit Spread (0DTE, July 31, 2026). Sell $740 put / Buy $738 put spread, targeting 20%+ profit with bullish slow grind thesis. + +**Use when:** +Executing or monitoring today's SPY options trade. + +**Setup / dependencies:** +None noted. Trade-specific, not reusable. + +### `iron-condor-45dte.md` + +**Purpose:** +Trade plan for SPX Iron Condor through Schwab broker. 45DTE entry, 30-point wings, forced close at 21DTE. Includes profit target (25% of net credit), stop loss (50% of max loss), and monitoring cadence. + +**Use when:** +Setting up or managing SPX iron condor spreads with Schwab. + +**Setup / dependencies:** +Schwab broker session required. + +### `cha-martin-watchlist.ms.csv` + +**Purpose:** +CSV export of a Cha Martin watchlist — likely contains tickers for scanning or monitoring. + +**Use when:** +Referencing tickers for scans, short squeeze candidates, or watchlist filtering. + +**Setup / dependencies:** +None noted. + +## Maintenance Notes + +When adding or updating a tool folder, update this README with: + +- purpose +- key files and entry points +- usage guidance +- setup requirements +- notable changes or cautions diff --git a/cha-martin-watchlist.ms.csv b/cha-martin-watchlist.ms.csv new file mode 100644 index 0000000..ed27657 --- /dev/null +++ b/cha-martin-watchlist.ms.csv @@ -0,0 +1,55 @@ +AAPL +UPS +UBER +TSM +TSLS +TSLA +TGT +TAN +SQQQ +SPY +SPX +SOXL +SEDG +SBUX +RUN +ROKU +RIVN +RBLX +QQQ +PYPL +PLTR +PINS +PANW +NVDA +NKE +NFLX +MU +MSFT +META +KRE +INTC +HOOD +HD +GOOGL +GOOG +FSLR +FDX +ETSY +ENPH +DIS +DE +DDOG +CRWD +CRM +COST +COIN +CAT +BITO +BABA +BA +ARKK +AMZN +AMD +AFRM +ADBE diff --git a/iron-condor-45dte.md b/iron-condor-45dte.md new file mode 100644 index 0000000..f7faf73 --- /dev/null +++ b/iron-condor-45dte.md @@ -0,0 +1,26 @@ +``` +Iron Condor 45dte Trade Plan +``` + +Trade plan request: + +Execute an iron condor on SPX through my Schwab broker session. + +Underlying: SPX Broker: Schwab Strategy: Iron Condor (4 legs) Entry DTE: ~45 days Wing width: 30 points Spread legs: + +Short put: [strike] +Long put: [strike] +Short call: [strike] +Long call: [strike] Net credit: $[] Max loss: $[] +Exit rules: + +Profit target: Close all 4 legs at 25% of net credit +Stop loss: Close all 4 legs at 50% loss of max loss +Time exit: Close all 4 legs unconditionally on [date — 21 calendar days from entry] +Broker hard stop: Set a Schwab-side stop order at 50% loss as offline protection. Cancel automatically once MARI closes the position. +Monitoring cadence: Swing pace — check net position P&L multiple times per trading day. No intra-second polling needed. + +Close all 4 legs together. Do not roll or manage legs individually. + +Review the plan with me before execution. Confirm buying power and order preview before placing. + diff --git a/scan-watchlist.md b/scan-watchlist.md new file mode 100644 index 0000000..3578a9c --- /dev/null +++ b/scan-watchlist.md @@ -0,0 +1,74 @@ + +## Plan: Watchlist Confluence Scan + +### Phase 1 — Broad filter across all 54 tickers (~5-8 tool calls) + +**1. Market context snapshot** +- Pull `SPY` and `QQQ` snapshots to establish the day's market regime (trend, range, key levels). Everything filters through this — no short setups in a strong uptrend day, no longs into a breakdown. + +**2. Batch screen for daily structure** +- Run a Finviz scan (or equivalent) filtering for: + - Price within ~3% of the 50-day MA (your stated preference) + - Consolidation/base pattern or pullback setup + - Above/below VWAP context +- This narrows 54 → likely 10-15 candidates worth deeper review. + +**3. Parallel ticker snapshots** +- Pull `snapshot` data for the ~10-15 candidates from Phase 2 to get: + - Current price, day range, volume vs average + - Pre-market action (gappers up/down) + - % change from 50MA (if available from scan data) + +### Phase 2 — Confluence analysis on the shortlist (~3-4 calls per ticker × 5-8 tickers) + +For each candidate, evaluate these confluence factors: + +| Factor | Tool / Source | What I'm looking for | +|--------|--------------|----------------------| +| **Daily chart structure** | `chart_command` — load symbol, D timeframe | Trend direction, price vs 50MA/200MA, support/resistance zones, base/consolidation patterns | +| **Intraday setup** | `chart_command` — 3-min or 5-min chart | VWAP relationship, pre-market gap vs overnight range, opening range break potential | +| **Volume profile** | `chart_command` — volume indicator | Above-average volume confirming the move, or thin volume suggesting trap | +| **Options flow / unusual activity** | `mcp` → `ttg-options` chain snapshot | Unusual call/put volume, max pain, gamma exposure — institutional positioning signal | +| **Relative strength** | Visual chart comparison | Is it holding while the sector/market sells? That's a Mike-style confluence flag | + +### Phase 3 — Trade plan construction on top setups (2-4 tickers max) + +For the 2-4 tickers with the strongest confluence: + +**1. Chart the setup** +- Load the ticker on AI chart with overlays: VWAP, 50 EMA, key S/R levels drawn +- Identify the exact entry zone, stop level, and target levels (T1/T2/T3) + +**2. Draft the trade plan** +- Symbol, side, entry zone, stop, targets, time horizon +- **Rationale**: confluence factors that align (daily structure + intraday trigger + flow confirmation) +- **What invalidates it**: the one condition that kills the thesis + +**3. Options structure** +- Given your preference for credit spreads, evaluate: + - Credit spread strikes (defined risk, collect premium) + - Bid-ask spread width (< $0.25 preferred for scalps) + - Time decay working in your favor + +### Phase 4 — Summary card + +Deliver a structured card showing: +- Top 3-5 setups ranked by confluence score +- Each with: setup type, entry/stop/targets, key confluence factors, risk level +- The "sitting on hands" list — tickers that looked okay but lacked a decisive edge + +--- + +### Estimated tool call count +- **Phase 1:** ~8-10 calls +- **Phase 2:** ~15-25 calls (depending on shortlist size) +- **Phase 3:** ~5-8 calls +- **Phase 4:** 1 card build call + +**Total: ~30-45 tool calls** — this is a substantive scan. I'd recommend we do Phase 1 first to see the shortlist, then you can approve Phase 2 on the narrowed candidates rather than burning through credits on all 54. + +### Key question before I proceed: +1. **Long only, or long + short?** You've expressed interest in both — what's the bias today? +2. **Time horizon:** 0DTE intraday scalps, or day/swing holds? +3. **Asset class focus:** Equities only, or include ETFs (SPY/QQQ/TAN/SOXL/SQQQ/KRE) in the confluence review? + diff --git a/workflows/research-dfns/AlertsLog_Mon Jul 27 2026 (1).txt b/workflows/research-dfns/AlertsLog_Mon Jul 27 2026 (1).txt new file mode 100644 index 0000000..bf353ef --- /dev/null +++ b/workflows/research-dfns/AlertsLog_Mon Jul 27 2026 (1).txt @@ -0,0 +1,25 @@ +7/27/2026, 08:19 AM [Admin]: Alerts Cleared. +7/27/2026, 09:38 AM [Cha Martin]: #INTERMEDIATE #OPTION #SWING stopped out 7/31 $ORCL 106P/.40 +7/27/2026, 09:40 AM [Cha Martin]: #ADVANCED #OPTION #DAY bought 7/31 $NVDA 195P/1.18 stop area 207 (TIER 1) +7/27/2026, 09:41 AM [Jay Downing]: #EQUITY stopped covered QBTS @19.10 from 7/25** +7/27/2026, 09:43 AM [Cha Martin]: #ADVANCED #OPTION #DAY took profit 7/31 $NVDA 195P/1.7 still holding some +7/27/2026, 09:46 AM [Cha Martin]: #ADVANCED #OPTION #DAY took profit 7/31 $NVDA 195P/1.9 still holding some +7/27/2026, 10:23 AM [Cha Martin]: #ADVANCED #OPTION #DAY took profit 7/31 $NVDA 195P/2.32 still holding some +7/27/2026, 10:28 AM [Cha Martin]: #ADVANCED #OPTION #SCALP bought 7/31 $NVDA 185P/.70 stop area 200.5 (1/2 TIER 1) +7/27/2026, 10:35 AM [Cha Martin]: #ADVANCED #OPTION #DAY took profit 7/31 $NVDA 195P/2.84 still holding some +7/27/2026, 10:36 AM [Chris Toner]: #INTERMEDIATE #OPTION #SWING buying 7/31 TLT 83.50put $0.34 (stop 0.15) +7/27/2026, 10:36 AM [Cha Martin]: #ADVANCED #OPTION #SCALP took profit 7/31 $NVDA 185P/.79 still holding some +7/27/2026, 10:36 AM [Chris Toner]: #INTERMEDIATE #OPTION #SWING buying 7/31 NEE 89.00put $0.90 (stop 0.50) +7/27/2026, 11:13 AM [Michael Edward]: #ADVANCED #EQUITY #DAY long Tier 1 (25% of normal size) $DFNS $6.83 stop loss $6.25 area (short squeeze or bust type of play) will add Tier 2 through $7.25 +7/27/2026, 11:39 AM [Cha Martin]: #ADVANCED #OPTION #SCALP took profit 7/31 $NVDA 185P/1.19 still holding some +7/27/2026, 12:13 PM [Michael Edward]: #ADVANCED #EQUITY #DAY added Tier 2 $DFNS $7.18 stop loss $6.75 area +7/27/2026, 12:14 PM [Michael Edward]: #ADVANCED #EQUITY #DAY took some profit $DFNS $7.65 still holding some +7/27/2026, 12:14 PM [Michael Edward]: #ADVANCED #EQUITY #DAY took more profit $DFNS $8.21 still holding some +7/27/2026, 12:20 PM [Michael Edward]: #ADVANCED #EQUITY #DAY took more profit $DFNS $9.19 still holding some +7/27/2026, 01:08 PM [Michael Edward]: #ADVANCED #EQUITY #DAY took more profit $DFNS $10.08 still holding small piece +7/27/2026, 01:47 PM [Michael Edward]: #ADVANCED #EQUITY #DAY final take profit $DFNS $11.88 +7/27/2026, 01:57 PM [Cha Martin]: #ADVANCED #OPTION #DAY took profit 7/31 $NVDA 195P/3.5 still holding some +7/27/2026, 01:57 PM [Chris Toner]: #INTERMEDIATE #OPTION #SWING taking profit 7/31 NEE 89.00put $1.40 (still holding some) +7/27/2026, 04:01 PM [Michael Edward]: #ADVANCED #EQUITY #DAY long $DFNS $13.23 stop loss $11.00 area (extreme risk no more than 1/2 size short squeeze or bust type of play) +7/27/2026, 04:13 PM [Michael Edward]: #ADVANCED #EQUITY #DAY took some profit $DFNS $15.71 still holding some +7/27/2026, 04:15 PM [Michael Edward]: #ADVANCED #EQUITY #DAY took more profit $DFNS $17.30 still holding some diff --git a/workflows/research-dfns/AlertsLog_Mon Jul 27 2026 (2).txt b/workflows/research-dfns/AlertsLog_Mon Jul 27 2026 (2).txt new file mode 100644 index 0000000..dcd2e50 --- /dev/null +++ b/workflows/research-dfns/AlertsLog_Mon Jul 27 2026 (2).txt @@ -0,0 +1,27 @@ +7/27/2026, 08:19 AM [Admin]: Alerts Cleared. +7/27/2026, 09:38 AM [Cha Martin]: #INTERMEDIATE #OPTION #SWING stopped out 7/31 $ORCL 106P/.40 +7/27/2026, 09:40 AM [Cha Martin]: #ADVANCED #OPTION #DAY bought 7/31 $NVDA 195P/1.18 stop area 207 (TIER 1) +7/27/2026, 09:41 AM [Jay Downing]: #EQUITY stopped covered QBTS @19.10 from 7/25** +7/27/2026, 09:43 AM [Cha Martin]: #ADVANCED #OPTION #DAY took profit 7/31 $NVDA 195P/1.7 still holding some +7/27/2026, 09:46 AM [Cha Martin]: #ADVANCED #OPTION #DAY took profit 7/31 $NVDA 195P/1.9 still holding some +7/27/2026, 10:23 AM [Cha Martin]: #ADVANCED #OPTION #DAY took profit 7/31 $NVDA 195P/2.32 still holding some +7/27/2026, 10:28 AM [Cha Martin]: #ADVANCED #OPTION #SCALP bought 7/31 $NVDA 185P/.70 stop area 200.5 (1/2 TIER 1) +7/27/2026, 10:35 AM [Cha Martin]: #ADVANCED #OPTION #DAY took profit 7/31 $NVDA 195P/2.84 still holding some +7/27/2026, 10:36 AM [Chris Toner]: #INTERMEDIATE #OPTION #SWING buying 7/31 TLT 83.50put $0.34 (stop 0.15) +7/27/2026, 10:36 AM [Cha Martin]: #ADVANCED #OPTION #SCALP took profit 7/31 $NVDA 185P/.79 still holding some +7/27/2026, 10:36 AM [Chris Toner]: #INTERMEDIATE #OPTION #SWING buying 7/31 NEE 89.00put $0.90 (stop 0.50) +7/27/2026, 11:13 AM [Michael Edward]: #ADVANCED #EQUITY #DAY long Tier 1 (25% of normal size) $DFNS $6.83 stop loss $6.25 area (short squeeze or bust type of play) will add Tier 2 through $7.25 +7/27/2026, 11:39 AM [Cha Martin]: #ADVANCED #OPTION #SCALP took profit 7/31 $NVDA 185P/1.19 still holding some +7/27/2026, 12:13 PM [Michael Edward]: #ADVANCED #EQUITY #DAY added Tier 2 $DFNS $7.18 stop loss $6.75 area +7/27/2026, 12:14 PM [Michael Edward]: #ADVANCED #EQUITY #DAY took some profit $DFNS $7.65 still holding some +7/27/2026, 12:14 PM [Michael Edward]: #ADVANCED #EQUITY #DAY took more profit $DFNS $8.21 still holding some +7/27/2026, 12:20 PM [Michael Edward]: #ADVANCED #EQUITY #DAY took more profit $DFNS $9.19 still holding some +7/27/2026, 01:08 PM [Michael Edward]: #ADVANCED #EQUITY #DAY took more profit $DFNS $10.08 still holding small piece +7/27/2026, 01:47 PM [Michael Edward]: #ADVANCED #EQUITY #DAY final take profit $DFNS $11.88 +7/27/2026, 01:57 PM [Cha Martin]: #ADVANCED #OPTION #DAY took profit 7/31 $NVDA 195P/3.5 still holding some +7/27/2026, 01:57 PM [Chris Toner]: #INTERMEDIATE #OPTION #SWING taking profit 7/31 NEE 89.00put $1.40 (still holding some) +7/27/2026, 04:01 PM [Michael Edward]: #ADVANCED #EQUITY #DAY long $DFNS $13.23 stop loss $11.00 area (extreme risk no more than 1/2 size short squeeze or bust type of play) +7/27/2026, 04:13 PM [Michael Edward]: #ADVANCED #EQUITY #DAY took some profit $DFNS $15.71 still holding some +7/27/2026, 04:15 PM [Michael Edward]: #ADVANCED #EQUITY #DAY took more profit $DFNS $17.30 still holding some +7/27/2026, 05:38 PM [Michael Edward]: #ADVANCED #EQUITY #DAY took more profit $DFNS $20.24 still holding small piece +7/27/2026, 05:55 PM [Michael Edward]: #ADVANCED #EQUITY #DAY final take profit $DFNS $18.24 diff --git a/workflows/research-dfns/AlertsLog_Mon Jul 27 2026.txt b/workflows/research-dfns/AlertsLog_Mon Jul 27 2026.txt new file mode 100644 index 0000000..bf353ef --- /dev/null +++ b/workflows/research-dfns/AlertsLog_Mon Jul 27 2026.txt @@ -0,0 +1,25 @@ +7/27/2026, 08:19 AM [Admin]: Alerts Cleared. +7/27/2026, 09:38 AM [Cha Martin]: #INTERMEDIATE #OPTION #SWING stopped out 7/31 $ORCL 106P/.40 +7/27/2026, 09:40 AM [Cha Martin]: #ADVANCED #OPTION #DAY bought 7/31 $NVDA 195P/1.18 stop area 207 (TIER 1) +7/27/2026, 09:41 AM [Jay Downing]: #EQUITY stopped covered QBTS @19.10 from 7/25** +7/27/2026, 09:43 AM [Cha Martin]: #ADVANCED #OPTION #DAY took profit 7/31 $NVDA 195P/1.7 still holding some +7/27/2026, 09:46 AM [Cha Martin]: #ADVANCED #OPTION #DAY took profit 7/31 $NVDA 195P/1.9 still holding some +7/27/2026, 10:23 AM [Cha Martin]: #ADVANCED #OPTION #DAY took profit 7/31 $NVDA 195P/2.32 still holding some +7/27/2026, 10:28 AM [Cha Martin]: #ADVANCED #OPTION #SCALP bought 7/31 $NVDA 185P/.70 stop area 200.5 (1/2 TIER 1) +7/27/2026, 10:35 AM [Cha Martin]: #ADVANCED #OPTION #DAY took profit 7/31 $NVDA 195P/2.84 still holding some +7/27/2026, 10:36 AM [Chris Toner]: #INTERMEDIATE #OPTION #SWING buying 7/31 TLT 83.50put $0.34 (stop 0.15) +7/27/2026, 10:36 AM [Cha Martin]: #ADVANCED #OPTION #SCALP took profit 7/31 $NVDA 185P/.79 still holding some +7/27/2026, 10:36 AM [Chris Toner]: #INTERMEDIATE #OPTION #SWING buying 7/31 NEE 89.00put $0.90 (stop 0.50) +7/27/2026, 11:13 AM [Michael Edward]: #ADVANCED #EQUITY #DAY long Tier 1 (25% of normal size) $DFNS $6.83 stop loss $6.25 area (short squeeze or bust type of play) will add Tier 2 through $7.25 +7/27/2026, 11:39 AM [Cha Martin]: #ADVANCED #OPTION #SCALP took profit 7/31 $NVDA 185P/1.19 still holding some +7/27/2026, 12:13 PM [Michael Edward]: #ADVANCED #EQUITY #DAY added Tier 2 $DFNS $7.18 stop loss $6.75 area +7/27/2026, 12:14 PM [Michael Edward]: #ADVANCED #EQUITY #DAY took some profit $DFNS $7.65 still holding some +7/27/2026, 12:14 PM [Michael Edward]: #ADVANCED #EQUITY #DAY took more profit $DFNS $8.21 still holding some +7/27/2026, 12:20 PM [Michael Edward]: #ADVANCED #EQUITY #DAY took more profit $DFNS $9.19 still holding some +7/27/2026, 01:08 PM [Michael Edward]: #ADVANCED #EQUITY #DAY took more profit $DFNS $10.08 still holding small piece +7/27/2026, 01:47 PM [Michael Edward]: #ADVANCED #EQUITY #DAY final take profit $DFNS $11.88 +7/27/2026, 01:57 PM [Cha Martin]: #ADVANCED #OPTION #DAY took profit 7/31 $NVDA 195P/3.5 still holding some +7/27/2026, 01:57 PM [Chris Toner]: #INTERMEDIATE #OPTION #SWING taking profit 7/31 NEE 89.00put $1.40 (still holding some) +7/27/2026, 04:01 PM [Michael Edward]: #ADVANCED #EQUITY #DAY long $DFNS $13.23 stop loss $11.00 area (extreme risk no more than 1/2 size short squeeze or bust type of play) +7/27/2026, 04:13 PM [Michael Edward]: #ADVANCED #EQUITY #DAY took some profit $DFNS $15.71 still holding some +7/27/2026, 04:15 PM [Michael Edward]: #ADVANCED #EQUITY #DAY took more profit $DFNS $17.30 still holding some diff --git a/workflows/research-dfns/ChatLog_Mon Jul 27 2026.txt b/workflows/research-dfns/ChatLog_Mon Jul 27 2026.txt new file mode 100644 index 0000000..6c01566 --- /dev/null +++ b/workflows/research-dfns/ChatLog_Mon Jul 27 2026.txt @@ -0,0 +1,1151 @@ +7/26/2026, 11:30 PM [Admin]: Chat Cleared. +7/27/2026, 08:14 AM [Mikaela]: gm fam! +7/27/2026, 08:14 AM [Blue Trader]: 🐜 🐜 G’ Mon Morin ayoo 💥 +7/27/2026, 08:15 AM [Mikaela]: @Blue Trader guess it just us lol +7/27/2026, 08:16 AM [Blue Trader]: @Mikaela🐜 🐜 G’ Mon Morin Mikaele ayoo lol200 pus💥 +7/27/2026, 08:16 AM [Blue Trader]: @Mikaela plus +7/27/2026, 08:17 AM [Mikaela]: haha party time +7/27/2026, 08:17 AM [Mikaela]: like seriously tho. where is everyone lol .... +7/27/2026, 08:18 AM [Mikaela]: its all right everyone know i like to be first to the party and i will dance by myself if i need to ... +7/27/2026, 08:18 AM [Minnesota Trader]: They are still in STR +7/27/2026, 08:19 AM [James Pearson]: Good morning, TTG! +7/27/2026, 08:19 AM [Mikaela]: @Minnesota Trader got it! ha! mine showed closed weird. +7/27/2026, 08:19 AM [Minnesota Trader]: They are coming over now +7/27/2026, 08:19 AM [Mikaela]: @James Pearson morning +7/27/2026, 08:19 AM [BuiltOnMomentum]: Good Morning TTG! 😊 +7/27/2026, 08:19 AM [GREAT_SUCCESS]: aye yo +7/27/2026, 08:19 AM [Nina G]: GM!! +7/27/2026, 08:19 AM [ASL220]: @Mikaela gm +7/27/2026, 08:19 AM [Mikaela]: @ASL220 gm!! +7/27/2026, 08:20 AM [Sheryl Mineo]: gm ttg!!!!! +7/27/2026, 08:20 AM [TTG GadgetGuy]: Gm all +7/27/2026, 08:20 AM [florence]: @Mikaela good morning +7/27/2026, 08:20 AM [Darth Trader RC]: ayooo fam +7/27/2026, 08:20 AM [rebecacordier]: Good morning +7/27/2026, 08:20 AM [Mikaela]: yay my friends here to partaaayyyyy lol +7/27/2026, 08:20 AM [Joe S]: gmeveryone +7/27/2026, 08:20 AM [Sheryl Mineo]: @Mikaela gm!! +7/27/2026, 08:20 AM [Mikaela]: @florence gm sis +7/27/2026, 08:20 AM [Mikaela]: @Sheryl Mineo Hiiiiiii friend!!! +7/27/2026, 08:20 AM [VWAP Sniper]: @Mikaela gm fam!! Happy Monday!! +7/27/2026, 08:20 AM [Mikaela]: @VWAP Sniper gm gm! +7/27/2026, 08:21 AM [Keiko]: good morning family! 😊 +7/27/2026, 08:21 AM [2BigPete]: $EDBL 132% gap up on 3.2mil vol LOW float News pop +7/27/2026, 08:21 AM [Keiko]: round 2 tooobby! +7/27/2026, 08:21 AM [Smoothbrain]: Live! +7/27/2026, 08:21 AM [Mikaela]: @Keiko gm sis! +7/27/2026, 08:22 AM [Nina G]: ayooooo Toby!!!!!! +7/27/2026, 08:22 AM [ASL220]: ayoooooo jsimmy +7/27/2026, 08:22 AM [Smoothbrain]: ayoo +7/27/2026, 08:22 AM [Mikaela]: or a come on........ aaaaaayyyyyooooooooo +7/27/2026, 08:22 AM [Keiko]: ayooooo toby bruno flower!1 +7/27/2026, 08:22 AM [Thomas L]: Ayoooo +7/27/2026, 08:22 AM [2BigPete]: $EDBL deal with Walmart to distribute across mid Atlantic states +7/27/2026, 08:22 AM [Keiko]: @Sheryl Mineo good morning! my homie! +7/27/2026, 08:22 AM [James Pearson]: Good morning, Glenn! +7/27/2026, 08:22 AM [Sheryl Mineo]: gm uncle G!!!!!!! +7/27/2026, 08:23 AM [ASL220]: Glennmeister +7/27/2026, 08:23 AM [Nina G]: Gm Glenny! +7/27/2026, 08:23 AM [Keiko]: good morning Uncle Glenny! +7/27/2026, 08:23 AM [Sheryl Mineo]: @Keiko gm!!!!! +7/27/2026, 08:23 AM [Keiko]: @Sheryl Mineo 😍 +7/27/2026, 08:24 AM [Rafa]: DJ Glenny is in the house +7/27/2026, 08:24 AM [Zina]: GM +7/27/2026, 08:24 AM [Carmen Haas]: Good morning TTG +7/27/2026, 08:24 AM [Mr. Miner]: @Glenny Trades did you have fun at MSG this weekend? +7/27/2026, 08:24 AM [Zina]: How is everyone +7/27/2026, 08:24 AM [Mikaela]: gm Unky G +7/27/2026, 08:24 AM [Mr. Miner]: yeah buddy!! '94 +7/27/2026, 08:24 AM [ASL220]: you better believe he did +7/27/2026, 08:25 AM [Mr. Miner]: Was awseome. My 201st show +7/27/2026, 08:25 AM [ASL220]: Uploaded image: "image.png" https://i.imgur.com/LuuztKp.png +7/27/2026, 08:25 AM [Mr. Miner]: Trey is my spirit animal +7/27/2026, 08:25 AM [Sheryl Mineo]: @ASL220 lol i wish +7/27/2026, 08:25 AM [ASL220]: haha :) +7/27/2026, 08:29 AM [RITESH PATEL]: @Glenny Trades I'm going to NJ this weekend, and maybe downtown NY for an evening +7/27/2026, 08:29 AM [Warren the Ape]: bradley beach is very nice +7/27/2026, 08:33 AM [Chele]: $EDBL walmart expansion +7/27/2026, 08:33 AM [2BigPete]: $ENTX popping +7/27/2026, 08:33 AM [RITESH PATEL]: @Glenny Trades you haven't traded Sun Country Airlines for a while +7/27/2026, 08:34 AM [2BigPete]: IPO Thursday is Jersey Mikes $JMKE +7/27/2026, 08:34 AM [Roline]: Good morning rrg +7/27/2026, 08:35 AM [Semper Fi]: gm Glenny!! +7/27/2026, 08:35 AM [Semper Fi]: value +7/27/2026, 08:36 AM [Sheryl Mineo]: ripping u off homie lol +7/27/2026, 08:36 AM [_Woody_]: youd be better off getting them $1 at a time... LOL +7/27/2026, 08:36 AM [EG]: Alkegiant +7/27/2026, 08:36 AM [Sheryl Mineo]: nope +7/27/2026, 08:36 AM [Semper Fi]: 40 for ten +7/27/2026, 08:36 AM [James Pearson]: Best value for the seller +7/27/2026, 08:36 AM [EG]: By allegiant air +7/27/2026, 08:36 AM [JLee]: Silly +7/27/2026, 08:37 AM [November Ball]: Goo9d Morning All +7/27/2026, 08:37 AM [2BigPete]: $ENTX 46% gap up on 3.7mil vol $275 mil private placement oversubscribed +7/27/2026, 08:38 AM [Sheryl Mineo]: @Jason Simmons $EDBL some news!! +7/27/2026, 08:40 AM [Tonya Brown]: lol +7/27/2026, 08:40 AM [Smoothbrain]: lol +7/27/2026, 08:40 AM [smiley]: @Sheryl Mineo Good morn! Good morn TTG! +7/27/2026, 08:40 AM [Sheryl Mineo]: @smiley good morning fam!!!!! +7/27/2026, 08:40 AM [BigBallah]: @Glenny Trades That's the playboy of TTG Lol +7/27/2026, 08:40 AM [WX2]: @BigBallah GM Bro +7/27/2026, 08:41 AM [BigBallah]: @WX2 Gm sir how are you? +7/27/2026, 08:41 AM [stacknchips]: gm everyone +7/27/2026, 08:41 AM [GREAT_SUCCESS]: $INTC looks like it wants to go fill the gap if it breaks below 89.50 +7/27/2026, 08:41 AM [BigBallah]: @WX2 How did it go on Friday? +7/27/2026, 08:41 AM [ASL220]: @BigBallah haha gm bro +7/27/2026, 08:41 AM [WX2]: I'm good. Thank you for asking, yourself? Have a good weekend? +7/27/2026, 08:41 AM [BigBallah]: @ASL220 There he is the man of the hour! Gm bro lets get it +7/27/2026, 08:42 AM [ASL220]: Lorenzo the bus driver's kid? +7/27/2026, 08:42 AM [WX2]: @BigBallah Oh, I didn't trade on Friday....I remembered I was looking at something but didn't pull the trigger.... +7/27/2026, 08:42 AM [MD]: $SAP is $9 up today +7/27/2026, 08:42 AM [ASL220]: @BigBallah pleasant gm, lets kill it +7/27/2026, 08:42 AM [BigBallah]: @WX2 Great glad your ok my friend yes the weekend had a lot of rain but we need it here in Miami +7/27/2026, 08:43 AM [BigBallah]: @WX2 oh ok +7/27/2026, 08:44 AM [ASL220]: dusty baker hughs +7/27/2026, 08:44 AM [ASL220]: lol +7/27/2026, 08:45 AM [2BigPete]: $ENTX now 57% gap up on 7.8mil vol +7/27/2026, 08:46 AM [ASL220]: Judge n Stanton needa come back. Phils had em last night +7/27/2026, 08:47 AM [ASL220]: Rice getting better and better +7/27/2026, 08:47 AM [ASL220]: thx Glenny +7/27/2026, 08:47 AM [Keiko]: Thank you Glenny +7/27/2026, 08:48 AM [Nina G]: Gm Cha! +7/27/2026, 08:48 AM [Sheryl Mineo]: ty uncle G! +7/27/2026, 08:48 AM [Keiko]: Good morning Cha! +7/27/2026, 08:48 AM [Nina G]: lol +7/27/2026, 08:48 AM [Keiko]: nice +7/27/2026, 08:48 AM [GREAT_SUCCESS]: nothing better than dipping leaves +7/27/2026, 08:48 AM [Sandy]: lol +7/27/2026, 08:48 AM [VWAP Sniper]: yeah I love cleaning the pool!! just love it!!! +7/27/2026, 08:48 AM [Heblsdme]: Lol +7/27/2026, 08:48 AM [Heblsdme]: Naam +7/27/2026, 08:48 AM [JustPatienceKeith]: wow. +7/27/2026, 08:48 AM [Nina G]: nice!! +7/27/2026, 08:48 AM [Bartee]: wow +7/27/2026, 08:48 AM [JustPatienceKeith]: I really need that invite. +7/27/2026, 08:49 AM [ASL220]: you were the Momma +7/27/2026, 08:49 AM [Russell-Goldminer]: the only thing you forgot was my invite...lol +7/27/2026, 08:49 AM [Nina G]: lol +7/27/2026, 08:49 AM [BrendanFraser]: lol +7/27/2026, 08:49 AM [TreyJ]: lol you was working hard +7/27/2026, 08:49 AM [NikNak]: Now it's time to rest! lol +7/27/2026, 08:49 AM [VWAP Sniper]: did you get tips? +7/27/2026, 08:49 AM [TTG GadgetGuy]: oh boy u must really like them +7/27/2026, 08:49 AM [GREAT_SUCCESS]: 5 star host +7/27/2026, 08:49 AM [Bluelark]: LOL... sounds like fun Cha +7/27/2026, 08:49 AM [Heblsdme]: So basically, well rested lol +7/27/2026, 08:49 AM [2BigPete]: $ENTX 86% gap up on 11.3mil vol +7/27/2026, 08:49 AM [Marilyn]: @Jason Simmons $pn +7/27/2026, 08:49 AM [Jennifer Blanchard]: You wore lots of hstd..lol +7/27/2026, 08:49 AM [Jennifer Blanchard]: Hats +7/27/2026, 08:50 AM [2BigPete]: @Marilyn almost no vol on $PN +7/27/2026, 08:50 AM [2BigPete]: Did you get tips at least lol +7/27/2026, 08:51 AM [Marilyn]: @2BigPete I see that just watching for vol +7/27/2026, 08:51 AM [Julie Coultes]: Goooooooood morning fam! +7/27/2026, 08:51 AM [2BigPete]: 👍 +7/27/2026, 08:51 AM [Sheryl Mineo]: @Julie Coultes gm!! +7/27/2026, 08:52 AM [2BigPete]: $IMMR beat on EPS missed on sales +7/27/2026, 08:52 AM [2BigPete]: $SPCX for shorts +7/27/2026, 08:53 AM [mriguy1973]: $mu want to short under tl +7/27/2026, 08:55 AM [Marilyn]: @Jason Simmons $entx on watch +7/27/2026, 08:55 AM [2BigPete]: @Cha Martin check $ZM for short +7/27/2026, 08:56 AM [Dewrantz]: $DDOG looking good this morning. +7/27/2026, 08:56 AM [Keiko]: Gm Toner! +7/27/2026, 08:56 AM [Nina G]: Gm Toner! +7/27/2026, 08:57 AM [Cha Martin]: hey Toner lets gooo +7/27/2026, 08:58 AM [Marilyn]: @Jason Simmons $ddog +7/27/2026, 08:59 AM [Mikaela]: oooh love this. Spicy idea with Chris and Cha on either side $NVDA +7/27/2026, 09:01 AM [Julie Coultes]: Aaaayyyyooooooooooooo +7/27/2026, 09:01 AM [Mikaela]: yo prof good morning!! +7/27/2026, 09:01 AM [stacknchips]: ayooo gm +7/27/2026, 09:01 AM [Carmen Haas]: Good morning +7/27/2026, 09:01 AM [Mikaela]: @Julie Coultes morning love! +7/27/2026, 09:01 AM [Julie Coultes]: @Sheryl Mineo @Mikaela Hi there! +7/27/2026, 09:01 AM [Sheryl Mineo]: @Julie Coultes gm!!!! +7/27/2026, 09:02 AM [Semper Fi]: Gm Killer +7/27/2026, 09:02 AM [Income Trader]: Good morning Jason. +7/27/2026, 09:02 AM [Kevin Castor]: We got two gaps +7/27/2026, 09:03 AM [Chris Toner]: @Mikaela I only like NVDA long if it can get over the 50day. +7/27/2026, 09:03 AM [Tammy]: Good morning all! +7/27/2026, 09:03 AM [Mikaela]: @Chris Toner heard. i was thinking the same thing. +7/27/2026, 09:03 AM [ASL220]: interesting scenario Simm +7/27/2026, 09:03 AM [Just Chilling]: GM ☕️ +7/27/2026, 09:03 AM [Islandgirl]: GM +7/27/2026, 09:04 AM [Chow_mein]: Gm +7/27/2026, 09:04 AM [Bodine]: gm +7/27/2026, 09:04 AM [The Mechanic]: GM TTG Family +7/27/2026, 09:07 AM [2BigPete]: $BAER $58 mil contract for 3 planes from Texas AandM forest service +7/27/2026, 09:07 AM [GREAT_SUCCESS]: $INTC +7/27/2026, 09:08 AM [2BigPete]: $BAER makes the super scooper plane for fighting forest fires. Big demand in EU, Canada and western US +7/27/2026, 09:09 AM [Alex]: Good morning traders +7/27/2026, 09:09 AM [Take5]: what do you think about $KO ? +7/27/2026, 09:09 AM [2BigPete]: $SOXS hod over $49 +7/27/2026, 09:09 AM [Momentum]: thanks for your DD +7/27/2026, 09:09 AM [Pamela Thomas]: Good Morning All! +7/27/2026, 09:09 AM [Hammer19]: $IWM +7/27/2026, 09:10 AM [The Witch]: Morning TTG Fam! +7/27/2026, 09:10 AM [Hammer19]: Thank you.. +7/27/2026, 09:11 AM [Island Trader]: i feel a big fade cooking +7/27/2026, 09:11 AM [Bx-StoNe]: Good morning +7/27/2026, 09:11 AM [Akela]: $ORCL +7/27/2026, 09:11 AM [Bx-StoNe]: Yes I Meade it early today +7/27/2026, 09:11 AM [2BigPete]: $DCOY watch this one, Reported one of it's drug being tested working against Ebola Zaire virus +7/27/2026, 09:13 AM [Take5]: Have you talked about $SOFI already? +7/27/2026, 09:13 AM [Confitrader]: $SLV +7/27/2026, 09:13 AM [2BigPete]: $BIYA 58% gap up on 11.9mil vol with 3mil float +7/27/2026, 09:14 AM [Maurice moe Phillips]: $BABA +7/27/2026, 09:14 AM [Yolo_Trader]: Good morning Fam !! +7/27/2026, 09:15 AM [2BigPete]: $MU China's largest chip IPO is rival $APPL testing it's CXMT memory chips +7/27/2026, 09:15 AM [Basha]: Gm Fam +7/27/2026, 09:15 AM [MoneyMakerPaul]: Good Morning, Bought $tsla on Friday almost near the lows( posted on FRiday) options and stocks +7/27/2026, 09:16 AM [Julie Coultes]: gappity gappity +7/27/2026, 09:16 AM [2BigPete]: $WHLR executed its' 1 for 5 reverse split +7/27/2026, 09:16 AM [Bx-StoNe]: Good stuff @money maker paul +7/27/2026, 09:16 AM [Vman]: GM TTG +7/27/2026, 09:16 AM [Smoothbrain]: 15 +7/27/2026, 09:16 AM [Smoothbrain]: oops +7/27/2026, 09:17 AM [Soni Soni]: Good morning!!! +7/27/2026, 09:17 AM [seeking_gainz]: Good morning +7/27/2026, 09:17 AM [Zina]: yes +7/27/2026, 09:17 AM [Julie Coultes]: Heck yes! +7/27/2026, 09:17 AM [DTrader9999]: 4 +7/27/2026, 09:18 AM [Julie Coultes]: Very ready! +7/27/2026, 09:18 AM [Liz C]: yes +7/27/2026, 09:18 AM [Sheryl Mineo]: volatility is always welcome!! +7/27/2026, 09:18 AM [Liz C]: yes +7/27/2026, 09:18 AM [Yankeeman007]: $EDBL +7/27/2026, 09:18 AM [Garrencee]: chanel=pergaory for me +7/27/2026, 09:18 AM [Julie Coultes]: 4 +7/27/2026, 09:19 AM [Kenneth Ward]: $ONDS professor? +7/27/2026, 09:19 AM [Sheryl Mineo]: $VTIX news +7/27/2026, 09:19 AM [Covstar]: $EDBL professor? +7/27/2026, 09:19 AM [Vladimir Lerner]: 8.15? +7/27/2026, 09:19 AM [Kenneth Ward]: $8 +7/27/2026, 09:19 AM [Takingprofit]: $TSLA im sure you coveed sorry im late +7/27/2026, 09:20 AM [Marilyn]: @Jason Simmons $vtix popped +7/27/2026, 09:20 AM [Frack]: $now ? +7/27/2026, 09:20 AM [Just Chilling]: WWE smack down +7/27/2026, 09:20 AM [Marilyn]: @Jason Simmons $vtix news $tsla +7/27/2026, 09:20 AM [Nas Delanoche]: @BigBallah yoooo gm bro , happy Monday . lets get it +7/27/2026, 09:20 AM [Snowpilot]: $AMD +7/27/2026, 09:20 AM [Michael Edward]: good morning gang +7/27/2026, 09:20 AM [Mikaela]: i am watching $CHWY for toby +7/27/2026, 09:20 AM [Colin]: 🙌🙌🙌 +7/27/2026, 09:20 AM [Sheryl Mineo]: @Michael Edward gm!!!! +7/27/2026, 09:20 AM [Julie Coultes]: @Michael Edward Aaaayyyooooooooooo +7/27/2026, 09:20 AM [TheDoctor]: @Michael Edward the killa! +7/27/2026, 09:20 AM [Skild_Trādsmen]: GM Mr. Mike +7/27/2026, 09:21 AM [stacknchips]: gm ayoooo +7/27/2026, 09:21 AM [Nas Delanoche]: @Sac1334 mister i dont miss , gm bro .lets get it +7/27/2026, 09:21 AM [Bx-StoNe]: Good morning Mike +7/27/2026, 09:21 AM [Just Chilling]: Ive been riding the $DELL roller coaster 🎢 +7/27/2026, 09:21 AM [Parsley]: @Mikaela 🐾 +7/27/2026, 09:21 AM [The Hungry Ghost]: Morning +7/27/2026, 09:21 AM [WX2]: @Nas Delanoche GM Bro +7/27/2026, 09:21 AM [Keiko]: Ayoooo +7/27/2026, 09:21 AM [Dracul]: Ayooooo! +7/27/2026, 09:21 AM [Just Chilling]: Dha khilla +7/27/2026, 09:21 AM [Julie Coultes]: Slay it! +7/27/2026, 09:21 AM [BuiltOnMomentum]: Ayoo! +7/27/2026, 09:21 AM [yonkel rodriguez]: ayooooooo +7/27/2026, 09:21 AM [CandleWixx]: ayooooo +7/27/2026, 09:21 AM [Carmen Haas]: aaaayyyyoooo +7/27/2026, 09:21 AM [Pamela Thomas]: GM Michael!! Ayoooooo +7/27/2026, 09:21 AM [Nas Delanoche]: @ASL220 yoooo gm bro , lets get it +7/27/2026, 09:21 AM [Nina G]: ayoooooo +7/27/2026, 09:21 AM [Baltazar]: good morning everybody +7/27/2026, 09:21 AM [HeBlsdMe1]: Ayyyyyooooooo +7/27/2026, 09:21 AM [Carlos Pujol]: GM +7/27/2026, 09:21 AM [James Pearson]: @Baltazar Good morning! +7/27/2026, 09:21 AM [Mikaela]: aaaayyyooooo killa +7/27/2026, 09:21 AM [Nas Delanoche]: @WX2 gm bro , happy Monday . lets get it +7/27/2026, 09:21 AM [c0ntrl]: aayooo +7/27/2026, 09:21 AM [Akela]: Morning +7/27/2026, 09:21 AM [James Pearson]: Happy Monday! +7/27/2026, 09:22 AM [Colin]: Let’s ride 🙌🙌 +7/27/2026, 09:22 AM [Zane Kimbo]: ayoo +7/27/2026, 09:22 AM [Liz C]: Ayooooo +7/27/2026, 09:23 AM [Liz C]: It a wait wait and see day +7/27/2026, 09:23 AM [Sac1334]: i am hoping for a PB to 742 +7/27/2026, 09:23 AM [TreyJ]: Or chop between? +7/27/2026, 09:23 AM [Rene Moran]: Ayoooo, GM Mr Edwards! +7/27/2026, 09:23 AM [Julie Coultes]: Sitting on hands until direction +7/27/2026, 09:24 AM [BigBallah]: @Nas Delanoche Yo yo gm bro lets get it! +7/27/2026, 09:25 AM [Julie Coultes]: Sippin on java, chillin +7/27/2026, 09:25 AM [Sam VolumeKing]: $EDBL room to 15? +7/27/2026, 09:25 AM [ASL220]: @Nas Delanoche @BigBallah gm ballers, lfg +7/27/2026, 09:26 AM [Nas Delanoche]: @ASL220 lets goooo +7/27/2026, 09:26 AM [BigBallah]: @ASL220 Gm brother lets get it +7/27/2026, 09:27 AM [Sam VolumeKing]: $AAPL any news or tech? +7/27/2026, 09:28 AM [Nas Delanoche]: @BigBallah what u watching this morning ? +7/27/2026, 09:29 AM [Gloves_and_Gains]: $TSLA little pb here +7/27/2026, 09:29 AM [BigBallah]: @Nas Delanoche So far $GE, $WMT, and you? +7/27/2026, 09:29 AM [Gloves_and_Gains]: $TSLA gap fill +7/27/2026, 09:29 AM [Sam VolumeKing]: $AAPL flying to moon? +7/27/2026, 09:29 AM [Island Trader]: just saw the daily chart on $DFNS , yikes! +7/27/2026, 09:29 AM [ASL220]: @Sam VolumeKing 340 +7/27/2026, 09:30 AM [2BigPete]: $SOXS up over $50 +7/27/2026, 09:30 AM [2BigPete]: $PLTR popping +7/27/2026, 09:30 AM [Nas Delanoche]: @BigBallah $USO , $IBIT and $DFNS +7/27/2026, 09:30 AM [BigBallah]: @Nas Delanoche cool lets get it! +7/27/2026, 09:31 AM [Nas Delanoche]: @BigBallah lets goooo +7/27/2026, 09:31 AM [Julie Coultes]: 🐮 🔔 🐻 +7/27/2026, 09:31 AM [Sac1334]: $edbl long 7.33 +7/27/2026, 09:31 AM [2BigPete]: $CLF hod +7/27/2026, 09:31 AM [Sheryl Mineo]: @Sac1334 lol and hakted!!!!! +7/27/2026, 09:31 AM [GREAT_SUCCESS]: watching $AAPL here +7/27/2026, 09:31 AM [Mark Nahas]: Ethereum is looking good. +7/27/2026, 09:32 AM [Sac1334]: @Sheryl Mineo i was typing and didnt get any off +7/27/2026, 09:32 AM [Mark Nahas]: crypto made a move yesterday +7/27/2026, 09:32 AM [Sheryl Mineo]: @Sac1334 we will get it!!!!! +7/27/2026, 09:32 AM [2BigPete]: $SPCX dumping again +7/27/2026, 09:32 AM [Julie Coultes]: Thanks Mike +7/27/2026, 09:33 AM [Skild_Trādsmen]: Thx Mike +7/27/2026, 09:34 AM [ChristinaLovesJaguars:]: $VEEE ww +7/27/2026, 09:34 AM [LadyBo$$]: $SPCX weak again +7/27/2026, 09:34 AM [Zina]: $NVDA falling +7/27/2026, 09:34 AM [Sac1334]: $qbts long 17.7 +7/27/2026, 09:35 AM [Mikaela]: watching $RIVN at the 50d , earnings Thurs +7/27/2026, 09:35 AM [Sandy]: watchng $COIN +7/27/2026, 09:35 AM [Marilyn]: @Jason Simmons $lvwr on watch 👀 for now +7/27/2026, 09:35 AM [2BigPete]: Lots of halts from dropping +7/27/2026, 09:35 AM [Dewrantz]: $ORCL pushing big now +7/27/2026, 09:36 AM [2BigPete]: $IRE woke up +7/27/2026, 09:36 AM [Marilyn]: @Jason Simmons $lvwr hhod +7/27/2026, 09:36 AM [Sac1334]: $qbts tp 18.7 from 17.7 +7/27/2026, 09:37 AM [Sac1334]: $eddl tp 8.45 +7/27/2026, 09:37 AM [Mark Nahas]: $BMNR look +7/27/2026, 09:37 AM [ChristinaLovesJaguars:]: $TRAX ww +7/27/2026, 09:38 AM [2BigPete]: @ChristinaLovesJaguars: $BIYA +7/27/2026, 09:38 AM [ChristinaLovesJaguars:]: @2BigPete 👍 +7/27/2026, 09:38 AM [Island Trader]: NICE POP ON $orcl +7/27/2026, 09:38 AM [Marilyn]: @Jason Simmons $biya +7/27/2026, 09:38 AM [2BigPete]: $PLTR hod $128+ +7/27/2026, 09:38 AM [Sac1334]: $lvwr +7/27/2026, 09:38 AM [Parsley]: @2BigPete $KYTX +7/27/2026, 09:39 AM [Mikaela]: watching my man $HIMS off the lows +7/27/2026, 09:39 AM [Marilyn]: @Jason Simmons $lvwr 💥💥 +7/27/2026, 09:40 AM [Julie Coultes]: $SPY squished between 9ema and pdh +7/27/2026, 09:40 AM [Mark Nahas]: $BMNR is movinggggggggg +7/27/2026, 09:40 AM [Mark Nahas]: up 12 % +7/27/2026, 09:40 AM [2BigPete]: @Parsley looks bigger move than it really is +7/27/2026, 09:40 AM [FERNANDO_RI]: Long $CRWD off $184.11 LFGO +7/27/2026, 09:40 AM [BlessedHotMess]: interested in short squeezes. $OOMER ? +7/27/2026, 09:40 AM [Sac1334]: $lvwr vol is great +7/27/2026, 09:41 AM [2BigPete]: $SOXS over $51.5 +7/27/2026, 09:41 AM [Marilyn]: @Jason Simmons $qbtx hod +7/27/2026, 09:41 AM [Marilyn]: @Jason Simmons $entx hod 💥👀 +7/27/2026, 09:41 AM [BlessedHotMess]: sory $OMER +7/27/2026, 09:42 AM [Dewrantz]: $RTX all time high again +7/27/2026, 09:42 AM [Takingprofit]: $ASML has a ten year back log we supply them +7/27/2026, 09:42 AM [2BigPete]: @Michael Edward Chip also with Chinese chip maker's memory chips being tested by $AAPL +7/27/2026, 09:42 AM [RightSide]: $YSLA starting too +7/27/2026, 09:42 AM [Marilyn]: @Jason Simmons $ionx $rgtx +7/27/2026, 09:42 AM [Mark Nahas]: the stuff they do is like the power of the sun. +7/27/2026, 09:42 AM [Sac1334]: $qbts tp 19.06 from 17.7 +7/27/2026, 09:43 AM [RightSide]: crazy insane who thinks of this stuff +7/27/2026, 09:43 AM [Marilyn]: @Jason Simmons $bmnu hod 🔥 +7/27/2026, 09:43 AM [2BigPete]: $BIYA pop +7/27/2026, 09:43 AM [Mac B.]: $SNDK already down $100 +7/27/2026, 09:43 AM [Island Trader]: $SNDK ugggghhh +7/27/2026, 09:43 AM [Mikaela]: $HIMS would like to see hold 29.17 +7/27/2026, 09:44 AM [Chris Trades]: BTC with a rip off of 65k sup +7/27/2026, 09:45 AM [Rookie]: $SPY hitting support +7/27/2026, 09:45 AM [RightSide]: whats mass produce 4 a year lol +7/27/2026, 09:46 AM [GREAT_SUCCESS]: lets goooo +7/27/2026, 09:46 AM [Marilyn]: @Jason Simmons $oii hod low vol +7/27/2026, 09:46 AM [Mark Nahas]: @Chris Trades nobody talking about the acyion in crypto +7/27/2026, 09:47 AM [Sac1334]: $lvwr still going +7/27/2026, 09:47 AM [Chukar Fly]: @Cha Martin Jumped in with you already at 100% grabbed today 205P +7/27/2026, 09:47 AM [Virgo]: @Sac1334 🔥👍 +7/27/2026, 09:49 AM [Chris Trades]: @Mark Nahas not a lot of crypto talk. There is a tab that sometimes has convos. Mostly use BTC as a guide to trade equities +7/27/2026, 09:49 AM [Sofi]: @Cha M Martin - what about ORCL keep holding +7/27/2026, 09:50 AM [Chris Trades]: @Sofi there is an alert that she stopped out +7/27/2026, 09:50 AM [Cha Martin]: did you miss the first alert of today where I stopped out @Sofi +7/27/2026, 09:50 AM [DigiMik]: LVWR flying this morning +7/27/2026, 09:51 AM [Sofi]: @Cha Martin - Ya misses read .. i bought it insated stopped out .. my bad +7/27/2026, 09:51 AM [2BigPete]: $SPCX $111 +7/27/2026, 09:52 AM [Marilyn]: @Jason Simmons $nne $smr $uec +7/27/2026, 09:52 AM [Mikaela]: $RIVN off 50d over pdh +7/27/2026, 09:52 AM [2BigPete]: $RGTI hod +7/27/2026, 09:53 AM [vicktor valdez]: @Michael Edward which semi conductor causing the sell off? +7/27/2026, 09:53 AM [Michael Edward]: @vicktor valdez $ASML +7/27/2026, 09:53 AM [Sheryl Mineo]: $DFNS building momentum ??!! +7/27/2026, 09:53 AM [vicktor valdez]: s @Michael Edward thank you +7/27/2026, 09:53 AM [Bull Flag]: $CVNA bullflag +7/27/2026, 09:53 AM [Bull Flag]: $CVNA tl cross +7/27/2026, 09:53 AM [2BigPete]: $ADVB halted on rise hod +7/27/2026, 09:54 AM [2BigPete]: $VEEE hod +7/27/2026, 09:54 AM [2BigPete]: $VEEE over $21 +7/27/2026, 09:56 AM [ChristinaLovesJaguars:]: @2BigPete 👍🔥 +7/27/2026, 09:56 AM [ChristinaLovesJaguars:]: $SPY Puts +7/27/2026, 09:56 AM [GREAT_SUCCESS]: lfgo $SPY going to test 740 +7/27/2026, 09:57 AM [RajN]: $ENTX crossed 3.20 +7/27/2026, 09:57 AM [2BigPete]: $ENTX pop into halt +7/27/2026, 09:57 AM [Mac B.]: good lord $SNDK +7/27/2026, 09:57 AM [TTG GadgetGuy]: spy into test area. NVDA holding +7/27/2026, 09:57 AM [Marilyn]: @Jason Simmons $nee selected by Afwerx +7/27/2026, 09:57 AM [Alex]: $MRNA pushing +7/27/2026, 09:58 AM [vicktor valdez]: I need a bounce into 311 $tsla to take puts +7/27/2026, 09:58 AM [2BigPete]: $SOXS still on rise hod over $53 +7/27/2026, 09:58 AM [Marilyn]: @Jason Simmons $omer cleared all dma ww +7/27/2026, 09:59 AM [2BigPete]: $ADVZB out halt and up +7/27/2026, 09:59 AM [2BigPete]: make that $ADVB +7/27/2026, 10:00 AM [Prospector]: I love when SPY bleeds +7/27/2026, 10:00 AM [Kei Lau]: $entx +7/27/2026, 10:00 AM [GREAT_SUCCESS]: $SPY perfect inverse ttg triangle +7/27/2026, 10:01 AM [Jace Wade]: now were below that 742 area, thats been tough +7/27/2026, 10:01 AM [Marilyn]: @Jason Simmons $entx halt hod +7/27/2026, 10:01 AM [2BigPete]: $PLTR getting some big candles +7/27/2026, 10:01 AM [Eric Webb]: $MU puts printing 7/31 $820 Put +7/27/2026, 10:02 AM [GREAT_SUCCESS]: $AAPL is unphased +7/27/2026, 10:02 AM [Island Trader]: got wacked on $SNXX , I was green pre-market.... freaking sucks +7/27/2026, 10:02 AM [2BigPete]: $SOXS hod $54 +7/27/2026, 10:02 AM [Prospector]: TSM ? +7/27/2026, 10:02 AM [Chukar Fly]: $MU puts 400% +7/27/2026, 10:02 AM [WX2]: the inevitable is coming..... +7/27/2026, 10:02 AM [James Masen]: $DFNS making another attempt +7/27/2026, 10:03 AM [2BigPete]: $IRE lod +7/27/2026, 10:03 AM [Gmoney]: typical $SPY shoots up overnight then sells off at open. A lot of weakness in tech +7/27/2026, 10:03 AM [Sac1334]: $qbts tp 19.3 from 17.7 +7/27/2026, 10:03 AM [Birdie-Bull]: QQQs 684p .8-2.4 filled gg +7/27/2026, 10:03 AM [JustPatienceKeith]: $MSFT looks like it wants to test highs +7/27/2026, 10:03 AM [Bobby F.]: Reminds me when Chinas came out with Deep seek +7/27/2026, 10:04 AM [Jason Simmons]: $QQQ lod +7/27/2026, 10:04 AM [2BigPete]: $CRWV lod +7/27/2026, 10:04 AM [Marc Anthony]: $ADBE up 4% +7/27/2026, 10:04 AM [2BigPete]: $YYAI halt on drop Again +7/27/2026, 10:04 AM [Chris Trades]: $DFNS ww. held $6 thru open and testying vwap. 5m tl coming up for more support. need a vol push +7/27/2026, 10:04 AM [JoshBoca]: $DFNS nice consolidation - if volume comes in this will explode +7/27/2026, 10:04 AM [JustPatienceKeith]: $MSFT nHoD +7/27/2026, 10:05 AM [Mikaela]: $ABNB at 20d nhod +7/27/2026, 10:08 AM [2BigPete]: $SPCX under $110 +7/27/2026, 10:08 AM [JoshBoca]: $DFNS back at vwap - LFG +7/27/2026, 10:09 AM [Jay Downing]: $rng ttg set up ww off previous highs +7/27/2026, 10:10 AM [Jay Downing]: $docu day 2 bounce room to 54s +7/27/2026, 10:10 AM [Island Trader]: $QQQ red on the day now +7/27/2026, 10:11 AM [GREAT_SUCCESS]: bannnng +7/27/2026, 10:11 AM [Dewrantz]: $SKHY just hit it's all time low +7/27/2026, 10:11 AM [Bryan]: @Dewrantz was just about to say that also lol whatta sell off +7/27/2026, 10:11 AM [Dewrantz]: Going lower +7/27/2026, 10:12 AM [Dewrantz]: Now let's wait for to see where it finds support. That thing has been a ATM machine for me. $SKHY +7/27/2026, 10:12 AM [bulgarianalien]: We're laughing at South Koreans . however our markets are getting same +7/27/2026, 10:13 AM [Marilyn]: @Jason Simmons $ncty hod +7/27/2026, 10:13 AM [2BigPete]: $VEEE hod $22+ +7/27/2026, 10:13 AM [Marilyn]: @Jason Simmons $veee 👀💥 +7/27/2026, 10:13 AM [Bryan]: @Dewrantz might find resistance at 150. We’ll have to see at that level +7/27/2026, 10:14 AM [2BigPete]: $SOXS hod past $55 +7/27/2026, 10:14 AM [JustPatienceKeith]: $GOOGL testing highs +7/27/2026, 10:15 AM [GREAT_SUCCESS]: crazy +7/27/2026, 10:16 AM [JustPatienceKeith]: $ADBE too +7/27/2026, 10:16 AM [smiley]: $NOW near highs too +7/27/2026, 10:16 AM [Julie Coultes]: So pretty +7/27/2026, 10:16 AM [Prospector]: rotation? some +7/27/2026, 10:16 AM [GREAT_SUCCESS]: heavily weighted +7/27/2026, 10:16 AM [El papiii do braziiiL]: right tricky call +7/27/2026, 10:16 AM [Julie Coultes]: nope +7/27/2026, 10:16 AM [Tabb's Cubes]: AAPL is back on top as the largest +7/27/2026, 10:16 AM [Marilyn]: @Jason Simmons $geni od 👀 +7/27/2026, 10:16 AM [JustPatienceKeith]: Strangely....$ORCL at HoD too +7/27/2026, 10:16 AM [Julie Coultes]: I'm watching $SPY and $QQQ +7/27/2026, 10:17 AM [GREAT_SUCCESS]: $NVDA is doing what $AAPL used to do to the $SPY +7/27/2026, 10:17 AM [bulgarianalien]: So someone is lying lol +7/27/2026, 10:17 AM [bulgarianalien]: no figuratively there is a divergence +7/27/2026, 10:17 AM [Gon Fishin]: $BIYA a bit frisky +7/27/2026, 10:17 AM [Birdie-Bull]: Just look at the Q's +7/27/2026, 10:17 AM [Birdie-Bull]: I've been shorting the Q's over SPY because of this +7/27/2026, 10:18 AM [Goldman's Sach]: @Michael Edward When did it take the top spot? +7/27/2026, 10:18 AM [Parsley]: Good thing I caught Mike talking so I got on line $SOXS 🙏 +7/27/2026, 10:18 AM [El papiii do braziiiL]: yes +7/27/2026, 10:18 AM [GREAT_SUCCESS]: there goes $AAPL new ath +7/27/2026, 10:18 AM [Julie Coultes]: 2026 showing it's face +7/27/2026, 10:18 AM [davidtc]: AAPL flight to safety ... +7/27/2026, 10:18 AM [Birdie-Bull]: @Michael Edward $MRNA calls printing on same sentiment +7/27/2026, 10:19 AM [Vj]: $NVDA down ~ 3% +7/27/2026, 10:19 AM [JOY1234]: $DXY is about to explode up +7/27/2026, 10:19 AM [spike63]: @Michael Edward $SMH and $SPY Identical +7/27/2026, 10:19 AM [Vj]: $NVDA 200 is a level so if no bounce for $NVDA sianara $SMH +7/27/2026, 10:19 AM [TreyJ]: In 7/29 $AAPL 345c .56 +7/27/2026, 10:20 AM [Yankeeman007]: How about $BA +7/27/2026, 10:20 AM [Yankeeman007]: 0 +7/27/2026, 10:20 AM [Skild_Trādsmen]: How can that bit of news abt the Chinese chip making machines cause this amount of drawdown? I can understand a drawdown, but for it to fillthe overnight gap? Really? +7/27/2026, 10:21 AM [Julie Coultes]: $SPY and $QQQ lod +7/27/2026, 10:22 AM [2BigPete]: $NVDA lod $200 +7/27/2026, 10:22 AM [James Pearson]: $NVDA monster. Good one, @Cha Martin , ty. +7/27/2026, 10:22 AM [Billybobble]: What was the news headline for semis? I missed it +7/27/2026, 10:22 AM [BlessedHotMess]: trading $NVDA 195P at .91 for 7/29 and just took profits at 1.25 and just took 1st profit at 2.25 on 7/31 at 1.69 +7/27/2026, 10:22 AM [Prospector]: 736 support? possibly +7/27/2026, 10:22 AM [TreyJ]: $DFNS holding up? +7/27/2026, 10:23 AM [Island Trader]: $CAT down $28 +7/27/2026, 10:23 AM [2BigPete]: $UVXY hod +7/27/2026, 10:23 AM [Gon Fishin]: @Michael Edward are you watching $BIYA today? +7/27/2026, 10:23 AM [2BigPete]: $SOXS hod $56 +7/27/2026, 10:23 AM [BlessedHotMess]: I was able to trade $NVDA this way for a daily trade and weekly trade. helping me to get profits out of the way and to sit more comfortably on the longer term +7/27/2026, 10:23 AM [2BigPete]: $RIOT lod +7/27/2026, 10:23 AM [KAVS]: what about $LVWR +7/27/2026, 10:23 AM [angelad]: meta is strong today +7/27/2026, 10:23 AM [Ski-dude]: @Michael Edward thoughts on $ORCL? Long +7/27/2026, 10:24 AM [Lessi Lu]: $VEEE +7/27/2026, 10:24 AM [BlessedHotMess]: $NVDA 1.40 - 91 tp 2 on the 7/29 exp +7/27/2026, 10:24 AM [2BigPete]: @KAVS sideways chop $LVWR could go either way +7/27/2026, 10:24 AM [Louis Winthorpe III]: $QQQ Below Friday's low now, and dropping to gap fill from May 5th +7/27/2026, 10:24 AM [KAVS]: gotcha just saw good volume +7/27/2026, 10:24 AM [Cha Martin]: letssss gooo +7/27/2026, 10:25 AM [Jace Wade]: 230% on my $spy puts this morning, not bad for monday +7/27/2026, 10:25 AM [2BigPete]: Mike then $SOXS looks great +7/27/2026, 10:25 AM [KSell]: $SPCX testing $110 area again +7/27/2026, 10:25 AM [Cha Martin]: thank you Mike +7/27/2026, 10:25 AM [BlessedHotMess]: Thank you Mike. and thank you Cha for the $NVDA idea !!! +7/27/2026, 10:25 AM [Billybobble]: Wait guys what was the news on semis? +7/27/2026, 10:25 AM [Julie Coultes]: Get it girl! +7/27/2026, 10:25 AM [Michael Soares]: I caught a scalp on $NVDA was not bad at all, nice trade Cha +7/27/2026, 10:25 AM [greenbull]: Couldn't get in the NVDA +7/27/2026, 10:25 AM [Jace Wade]: $spy gap fill in coming +7/27/2026, 10:25 AM [Chukar Fly]: got out a bit early on my $MU 845p's today. +7/27/2026, 10:25 AM [Sheryl Mineo]: $VEEE just needs vol +7/27/2026, 10:26 AM [GREAT_SUCCESS]: 🔥🔥 +7/27/2026, 10:26 AM [Parsley]: Cha-CING! +7/27/2026, 10:26 AM [Julie Coultes]: I've been renewwing $SPY puts on tessts and retests of candles Watching $SPY and $QQQ +7/27/2026, 10:26 AM [Uni]: @Cha Martin wooohooo +7/27/2026, 10:26 AM [Prospector]: 195 NVDAv +7/27/2026, 10:26 AM [Prospector]: ? +7/27/2026, 10:26 AM [Solrae]: Yes, $NVDA a winner +7/27/2026, 10:26 AM [James Pearson]: @greenbull sorry about that. The next deal is right around the corner. +7/27/2026, 10:26 AM [Parsley]: @Billybobble re ASML competition in China +7/27/2026, 10:26 AM [Pamela Thomas]: Great trade @Cha $NVDA Enjoy the ride +7/27/2026, 10:26 AM [GREAT_SUCCESS]: i love mondays +7/27/2026, 10:27 AM [BlessedHotMess]: $NVDA 187.5 7/29 .41 el cheapo s/l 203 area +7/27/2026, 10:27 AM [Prospector]: @Cha Martin 195 NVDA? +7/27/2026, 10:27 AM [2BigPete]: $YYAI halt on drop Again +7/27/2026, 10:27 AM [Dewrantz]: Watch $QQQ 0dte puts here +7/27/2026, 10:27 AM [Takingprofit]: @GREAT_SUCCESS I love mondays thru fridays +7/27/2026, 10:28 AM [Cha Martin]: @Prospector what about it +7/27/2026, 10:28 AM [BigBallah]: $INTC dumping +7/27/2026, 10:28 AM [2BigPete]: $CORD hod +7/27/2026, 10:28 AM [BlessedHotMess]: moving my s/l down to 200 area on the 195 7/31 exp +7/27/2026, 10:28 AM [2BigPete]: $SSOXS $57 hod +7/27/2026, 10:28 AM [angelad]: 700% gain on those qqq puts +7/27/2026, 10:29 AM [ChristinaLovesJaguars:]: $SPY at PDC +7/27/2026, 10:29 AM [Gon Fishin]: $TSAL testing current lows - possible breakdown here +7/27/2026, 10:29 AM [2BigPete]: only one S on $SOXS +7/27/2026, 10:29 AM [Gon Fishin]: $TSLA sorry +7/27/2026, 10:29 AM [RajN]: $ENTX held 3.8 +7/27/2026, 10:29 AM [2BigPete]: $ENTX hod hit $4 +7/27/2026, 10:29 AM [Mikaela]: shooot gonna be time to hide yo kids soooon +7/27/2026, 10:30 AM [Parsley]: @Mikaela 🔥 +7/27/2026, 10:30 AM [Jace Wade]: $0.56 to $3.00 on $spy puts, LFG +7/27/2026, 10:30 AM [Dewrantz]: $QQQ 0dte puts are printing +7/27/2026, 10:30 AM [TreyJ]: $AAPL 7/29 345c tp @.84/.56 2nd tp 1.11/.56 +7/27/2026, 10:31 AM [DungeonMaster]: I guess $SPY is going for 737.29 maybe +7/27/2026, 10:31 AM [TreyJ]: @Jace Wade nice trade +7/27/2026, 10:31 AM [Jace Wade]: @TreyJ ty +7/27/2026, 10:31 AM [Parsley]: @2BigPete SOXS can have as many S as she wants today +7/27/2026, 10:31 AM [AnnieGetYourGun]: $SPY just went red. +7/27/2026, 10:31 AM [Mark Nahas]: damn the candles on $NVDA are gulyyyyy +7/27/2026, 10:31 AM [BlessedHotMess]: whoop there it is. 1.81 - .91 on 195 7/29 exp +7/27/2026, 10:31 AM [TreyJ]: @Jace Wade 0dte? +7/27/2026, 10:32 AM [Takingprofit]: $NVDA under 197.8 takes us to 195 Great Put Cha +7/27/2026, 10:32 AM [Jace Wade]: @TreyJ yeah 740p +7/27/2026, 10:32 AM [Jace Wade]: still holding 1 contract +7/27/2026, 10:32 AM [DungeonMaster]: $SPY has been red +7/27/2026, 10:32 AM [John F]: Well that was a fun morning. Took my profit form last week and now up 30% on the day +7/27/2026, 10:32 AM [Mac B.]: what was the news on semis? I cant find it anywhere +7/27/2026, 10:32 AM [MoneyMakerPaul]: Long MNQ +7/27/2026, 10:32 AM [ChristinaLovesJaguars:]: $SPY, next level, 737.29 to watch +7/27/2026, 10:32 AM [Jace Wade]: @John F yeahhhh +7/27/2026, 10:32 AM [TreyJ]: @Jace Wade beautiful execution +7/27/2026, 10:32 AM [Chris Trades]: $TSLA trying to bounce off of Fridays lows +7/27/2026, 10:32 AM [MoneyMakerPaul]: stop lod +7/27/2026, 10:33 AM [Jace Wade]: @TreyJ i was long this morning intially lol +7/27/2026, 10:33 AM [Mikaela]: $CHWY slow grind woof woof new hod +7/27/2026, 10:34 AM [Marc Anthony]: $ADBE still pushing up over $12 +7/27/2026, 10:34 AM [MoneyMakerPaul]: stopped out +7/27/2026, 10:34 AM [2BigPete]: $IRE lod, Was looking to buy some. Glad I held off, almost $1 lower +7/27/2026, 10:34 AM [BlessedHotMess]: $NVDA 2.90 - 1.69 195P 7/31 exp tp 2 on those +7/27/2026, 10:34 AM [James Masen]: Gimme $47 $DRAM please +7/27/2026, 10:34 AM [TreyJ]: @Jace Wade makes the feeling even better turned a loser in for a winner chicken dinner I’m down to a runner as well on my $AAPL long +7/27/2026, 10:34 AM [JustPatienceKeith]: $PDD HoD +7/27/2026, 10:34 AM [Dewrantz]: $SHOP, anyone catch those calls? Pushing +7/27/2026, 10:34 AM [TreyJ]: $CRCL pulling back +7/27/2026, 10:34 AM [Mac B.]: $SNDK $1248 wow +7/27/2026, 10:35 AM [BlessedHotMess]: Hello Huang ? Yes, this is blessed. yeah, BlessedHotMess. yeahh that girl.. I just called to say I'm breaking up with you. :) haha +7/27/2026, 10:35 AM [TreyJ]: @Cha Martin still like $CRCL long? +7/27/2026, 10:36 AM [Mikaela]: $HIMS watching 29.17 which was an ol gap area +7/27/2026, 10:36 AM [Jace Wade]: @Cha Martin do you hold any $nvda long term? I'd like to add some but not here +7/27/2026, 10:36 AM [LadyBo$$]: Boom @Cha Martin 🔥Ty +7/27/2026, 10:36 AM [EG]: @BlessedHotMess lol sis - come my way to ahve some chicken and waffles and we can cry on the shouldr +7/27/2026, 10:36 AM [James Pearson]: haha +7/27/2026, 10:36 AM [Chukar Fly]: CHA'ANG +7/27/2026, 10:36 AM [Smoothbrain]: Cha Ching!!! +7/27/2026, 10:36 AM [Julie Coultes]: Bring them out! Bring them out! +7/27/2026, 10:36 AM [BlessedHotMess]: lol im not crying :) +7/27/2026, 10:36 AM [Gordon Gekko]: Kaboom! +7/27/2026, 10:37 AM [Pamela Thomas]: lol, yes +7/27/2026, 10:37 AM [Mikaela]: cchhhaaaa chinggggg nice Cha!!! +7/27/2026, 10:37 AM [BlessedHotMess]: yassssssssssssssss :) +7/27/2026, 10:37 AM [Steven Cruz]: @Cha Martin dammm girl you killed that thing!!! +7/27/2026, 10:37 AM [Jace Wade]: 🔥🔥🔥🔥🔥 +7/27/2026, 10:37 AM [Sheryl Mineo]: 🔥🔥🔥🔥 +7/27/2026, 10:37 AM [Forever a student]: yes +7/27/2026, 10:37 AM [Julie Coultes]: Do the Cha Cha! +7/27/2026, 10:37 AM [Truebluegirl]: Oh, and the squirrels🤣🤣 +7/27/2026, 10:37 AM [IveGotThis]: @Cha Martin Thanks!!!!! +7/27/2026, 10:37 AM [Parsley]: 🔥🔥🔥🔥🔥🔥🔥 +7/27/2026, 10:37 AM [Money]: Yesssssssssssssssssssssssss +7/27/2026, 10:37 AM [BlessedHotMess]: thank you Cha !!! fo sho ! +7/27/2026, 10:37 AM [e2]: thank you@Cha Cha +7/27/2026, 10:37 AM [DungeonMaster]: $SPY tested fridays low +7/27/2026, 10:37 AM [Seth Rodrigues]: locked in 200% @Cha Martin +7/27/2026, 10:37 AM [Solrae]: @Cha $NVDA Yaaaaay Great trade +7/27/2026, 10:37 AM [Hammer19]: Awesome trade @Cha!! How far down do you think we go? +7/27/2026, 10:37 AM [Seth Rodrigues]: Thank you +7/27/2026, 10:38 AM [Cha Martin]: @Hammer19 200D +7/27/2026, 10:39 AM [BigBallah]: @WX2 How's it going bro? +7/27/2026, 10:39 AM [BlessedHotMess]: yes ma'am I was able to afford more contracts there and able to buy some longer out all within the same r/r :) netted me a way to take profits earliy to feel more comfortable on the later date :) +7/27/2026, 10:39 AM [Marilyn]: @Jason Simmons $soxs +7/27/2026, 10:39 AM [WX2]: @BigBallah holding tight..... +7/27/2026, 10:39 AM [julesofthesouth]: @Cha Martin Thank you Cha!!! Amazing trade yo!!!!!!! +7/27/2026, 10:39 AM [2BigPete]: $NEE 7/31 $89P in at $0.80 +7/27/2026, 10:40 AM [BigBallah]: @WX2 oh ok no trades yet, im think I'm done for the day small green I don't want to give any back +7/27/2026, 10:40 AM [Texas Trader]: wow +7/27/2026, 10:40 AM [BlessedHotMess]: yep. get em Chris. I made my money week b4 and last week I got out. as I saw the long door open. and now I get to see my long swing on shares start working I have them at 73 avg :) +7/27/2026, 10:41 AM [NavyVet 1957]: $SPX 7400 Puts, 1.75 entry, paying 20.15 +7/27/2026, 10:41 AM [2BigPete]: $RIOT lod +7/27/2026, 10:41 AM [2BigPete]: $CRWV lod +7/27/2026, 10:41 AM [Chukar Fly]: Wow. I jumped in $MU 845 puts at .5 gout out at 3.00 now its at 8.50 Doh! +7/27/2026, 10:41 AM [2BigPete]: $SPCX lod Under $109 +7/27/2026, 10:41 AM [Money]: Watch $TRI looking Good +7/27/2026, 10:41 AM [Chukar Fly]: @2BigPete woot +7/27/2026, 10:41 AM [Bryan]: Good lord what a bleed today +7/27/2026, 10:41 AM [Jace Wade]: $spy 740 puts now over 600% on the runner +7/27/2026, 10:42 AM [LadyQRex]: $IWM - Just took final profit at 156%. Bought puts @ $0.99 and sold at $1.49. 🔥🔥🔥 +7/27/2026, 10:42 AM [Texas Trader]: nuts +7/27/2026, 10:42 AM [Colin]: wild!!!! +7/27/2026, 10:42 AM [Colin]: wow! +7/27/2026, 10:42 AM [Julie Coultes]: Fn Love It! +7/27/2026, 10:42 AM [TreyJ]: In 7/31 $MSTR $88p 1.20 waiting for it to follow $btc +7/27/2026, 10:42 AM [Julie Coultes]: ATM $ +7/27/2026, 10:42 AM [BigBallah]: $INTC +7/27/2026, 10:42 AM [Glenny Trades]: sandisk down 13% +7/27/2026, 10:42 AM [John F]: Locked in 58% on my account from $SPY +7/27/2026, 10:42 AM [BigBallah]: fell out of bed lol +7/27/2026, 10:42 AM [Smoothbrain]: great day $MU/ $TSLA puts done for the day, profits in my pockets, lets go +7/27/2026, 10:42 AM [MEAT]: Michael Burry feeling great today +7/27/2026, 10:42 AM [LadyQRex]: @Jace Wade - Awesome!!! 🔥🔥🔥 +7/27/2026, 10:42 AM [Julie Coultes]: I LOVE the direction! +7/27/2026, 10:42 AM [BlessedHotMess]: good to cry happy tears after being torn down yesterday am because I'm not making 100k ( I think that is what amount he said I should have made by now) +7/27/2026, 10:42 AM [G_FORCE]: wild +7/27/2026, 10:43 AM [bulgarianalien]: how many sputnik moments this year? +7/27/2026, 10:43 AM [e2]: What is the name of that Chinese co? +7/27/2026, 10:43 AM [Bryan]: @Michael Edward where do you think the bottom on $SPY might be? 735 support? +7/27/2026, 10:43 AM [2BigPete]: $SOXS hod over $59 and $60 soon +7/27/2026, 10:43 AM [Artur Gevorkyan]: $IWM went red too +7/27/2026, 10:43 AM [BigBallah]: $MU +7/27/2026, 10:43 AM [BigBallah]: Wow +7/27/2026, 10:44 AM [EG]: @BlessedHotMess i know wgat you mean sis +7/27/2026, 10:44 AM [2BigPete]: it was an IPO not long ago +7/27/2026, 10:44 AM [TTG GadgetGuy]: 1-2 punch man. memory makers and chips +7/27/2026, 10:44 AM [Maryedtothemarket]: $BE at possible buy level? 177.51 +7/27/2026, 10:44 AM [Jace Wade]: what if china companies names themselves like Chinese Resturants in the US - CHINA #1 CHIPS NOW +7/27/2026, 10:44 AM [JOY1234]: $RSP is up +.62% +7/27/2026, 10:45 AM [Learn2Earn]: per ChatGPT - Shanghai Micro Electronics Equipment (Group) Co., Ltd. is the company +7/27/2026, 10:45 AM [OnePlus7]: Shenzhen SiCarrier Technologies +7/27/2026, 10:45 AM [Trader99]: Yuliangsheng is the company +7/27/2026, 10:45 AM [John F]: I’ve been at work for 45 minutes and I made a days worth of my paycheck 🤌🏻 +7/27/2026, 10:45 AM [Jace Wade]: @John F THATS THE GOAL +7/27/2026, 10:46 AM [2BigPete]: @Trader99 isn't that a beer lol +7/27/2026, 10:46 AM [Mikaela]: $HIMS holding 29.17 lines up w vwap test hod +7/27/2026, 10:46 AM [Bull Flag]: Could this also be a yen carry trade unwind or Japanese investors de-risking? +7/27/2026, 10:47 AM [OnePlus7]: kimi k2 +7/27/2026, 10:47 AM [Dewrantz]: $HIMS TL Vwqp cross, HIMS 7/31, $29call +7/27/2026, 10:48 AM [Thrillseeker]: shouldn't be a shocked that they were working on what we are already doing and other countries are probably doing the same +7/27/2026, 10:48 AM [Birdie-Bull]: 700 by 8/14 +7/27/2026, 10:48 AM [Julie Coultes]: lod $SPY $736.54 +7/27/2026, 10:48 AM [Julie Coultes]: Been scalping all morning =0D +7/27/2026, 10:49 AM [Julie Coultes]: yes sir +7/27/2026, 10:49 AM [Dewrantz]: $ORCL just bounced beautifully +7/27/2026, 10:49 AM [Bread]: Takes the stairs down, elevator up +7/27/2026, 10:49 AM [Prospector]: tomorrow? holding swing out $SPY +7/27/2026, 10:50 AM [Bread]: Bread - sorry i was backwards lol +7/27/2026, 10:50 AM [Julie Coultes]: @Bread my job to be bassackwards lol +7/27/2026, 10:51 AM [Bread]: @Julie Coultes 😄 +7/27/2026, 10:51 AM [MoneyMakerPaul]: Dip buying back in session +7/27/2026, 10:52 AM [WX2]: @BigBallah I made an 1R trade on $SOXL bottomfishing but chicken out too early....otherwise would have locked in a 2R trade.....well, not complaining, at least I'm GREEN...woohoo +7/27/2026, 10:54 AM [bulgarianalien]: When is Jensen speaking on CNBC? Must be en route +7/27/2026, 10:55 AM [BigBallah]: @WX2 Lol you chickened out to early, yes at least your green but did you follow your plan or rules that's what you have to ask yourself, don't worry I'm in the same boat I follow it sometimes and then I don't. Like Mike always says you got to trust your analysis and game plan always! +7/27/2026, 10:56 AM [Rafa]: @Chris Toner where do you see $SOXX going from here? +7/27/2026, 10:56 AM [WX2]: @BigBallah BTW, I was so tempted to trade $DFNS but resisted the rush of jumping in and followed my plan +7/27/2026, 10:56 AM [James Pearson]: $NEE going the right way now. Good one, Chris Toner. +7/27/2026, 10:56 AM [Parsley]: @WX2 👏 +7/27/2026, 10:56 AM [Marilyn]: @Jason Simmons $nipg 💥💥 📈 +7/27/2026, 10:56 AM [Chris Toner]: @Rafa potential retest low from 7/17 under 500 +7/27/2026, 10:56 AM [WX2]: @BigBallah Yes, I have a stop loss, and take profit +7/27/2026, 10:57 AM [Rafa]: @Chris Toner Thanks boss +7/27/2026, 10:57 AM [BigBallah]: @WX2 Good job +7/27/2026, 10:57 AM [Mikaela]: $CHWY testing resistance area, nhod, 22.50 target for me if it breaks +7/27/2026, 10:58 AM [Colin]: we got long on that one Mike, great call +7/27/2026, 10:58 AM [Colin]: riding runners here +7/27/2026, 10:58 AM [Julie Coultes]: 🙌 +7/27/2026, 10:58 AM [Money]: Big Ball My Man +7/27/2026, 10:58 AM [Julie Coultes]: @Colin 🐎 +7/27/2026, 10:58 AM [Manus01]: $AAPL making triangles. +7/27/2026, 10:58 AM [Colin]: banger of a trade, great call mike... lined up nicely with our ES levels +7/27/2026, 10:59 AM [Colin]: L3 supporting a bit more here, but down to runners +7/27/2026, 10:59 AM [Jay Downing]: $trip gc daily, back over daily TL +7/27/2026, 10:59 AM [Mikaela]: $CHWY highest vol of the day on the break of hod, still a lower vol stock +7/27/2026, 10:59 AM [BigBallah]: @Money Gm Gleen how are you? +7/27/2026, 11:00 AM [Money]: Doing Great @BigBallah +7/27/2026, 11:03 AM [MoneyMakerPaul]: Debbie Dingell Democrat Representative purchased over 60K in Fmcc on 7/22 . I wonder what she knows? +7/27/2026, 11:05 AM [Mikaela]: $HIMS hod test again 15m looking good +7/27/2026, 11:05 AM [Marilyn]: @Jason Simmons $rklb awarded a $266 M multi launch contract with the US Space Force +7/27/2026, 11:06 AM [Rookie]: $SPY trying to get back to VWAP +7/27/2026, 11:06 AM [Mikaela]: $HIMS nhod, needs more volume +7/27/2026, 11:08 AM [ChristinaLovesJaguars:]: $SPY rejection at VWAP? +7/27/2026, 11:10 AM [Jay Downing]: $dbx room to 31s daily then range to 32.5 +7/27/2026, 11:12 AM [Sheryl Mineo]: $VEEE vol light but ww over 18 +7/27/2026, 11:12 AM [Dumb-Money]: $AMD getting smashed +7/27/2026, 11:12 AM [Ziggy]: @Chris Toner taking some profit on $NU thank you. +7/27/2026, 11:15 AM [Confitrader]: @Chris Toner Hi Chris, what's our next take on $NFLX please +7/27/2026, 11:16 AM [Daffy Duck]: 25 shares for me +7/27/2026, 11:16 AM [James Pearson]: 25 million +7/27/2026, 11:16 AM [vicktor valdez]: @Michael Edward where do you see support on asml +7/27/2026, 11:17 AM [TTG GadgetGuy]: $NOW moving with software. broke out of regression channel. +7/27/2026, 11:17 AM [TTG GadgetGuy]: might be ww tomorrow +7/27/2026, 11:18 AM [2BigPete]: $PLTR hod +7/27/2026, 11:19 AM [Marilyn]: @Jason Simmons $pltr 1 min +7/27/2026, 11:19 AM [John Wick]: @Michael Edward What about a BUY STOP order at around $7.30 on $DFNS? +7/27/2026, 11:20 AM [Mikaela]: $RIVN hod test, daily tl above, pdh and 50d below , earnings this week +7/27/2026, 11:20 AM [Marilyn]: @Jason Simmons $acgl just under hod / 52wkh 👀 +7/27/2026, 11:21 AM [Thrillseeker]: $NVDA news that they had a billionish investment in some company missed it but can't imagine them spending money is a goo dthing +7/27/2026, 11:22 AM [Eric Webb]: $GLW earnings tomorrow 7AM, it has pulled back near its 200 SMA, almost 50% off its high... should be interesting. +7/27/2026, 11:23 AM [BigBallah]: @Money Great glad to hear I hope you are feeling better my friend +7/27/2026, 11:23 AM [Marilyn]: @Jason Simmons $kidz 👀💥 +7/27/2026, 11:23 AM [Sac1334]: this $fiee no vol but indicating to open up $2...be careful +7/27/2026, 11:25 AM [Sac1334]: $fiee halt again... +7/27/2026, 11:25 AM [Goldman's Sach]: @Michael Edward Thoughts on $JPM here? +7/27/2026, 11:26 AM [Eric Webb]: Is $UNH finding support at $414/415 level ?? +7/27/2026, 11:26 AM [ChristinaLovesJaguars:]: $FIEE came out of halt & popped from $6.53 to $10.33. The squeeze is on. no position +7/27/2026, 11:27 AM [Marilyn]: @Jason Simmons $fiee nice pop to hod after halt +7/27/2026, 11:28 AM [Mikaela]: $NFLX looking good into that gap +7/27/2026, 11:28 AM [Marilyn]: @Jason Simmons $fiee halt again needs high vol +7/27/2026, 11:30 AM [Julie Coultes]: Friendly reminder: You do not have to trade everything you see. It is very important not to over trade and keep your profits in your pockets 🤗 +7/27/2026, 11:33 AM [Marilyn]: @Jason Simmons $rng 👀💥 +7/27/2026, 11:34 AM [Jay Downing]: $pypl ww bounce off daily TL +7/27/2026, 11:37 AM [Mikaela]: @Julie Coultes lol can you come sit next to me just to make sure i dont lolol +7/27/2026, 11:38 AM [Cha Martin]: RIDE THE WAVE +7/27/2026, 11:38 AM [Mohamed Ali]: $SPY Nlod +7/27/2026, 11:38 AM [Cha Martin]: ride the wave +7/27/2026, 11:38 AM [Rafa]: @Michael Edward where do you see a bounce in $SOXL? +7/27/2026, 11:39 AM [Marilyn]: @Jason Simmons $bsx $jbs $cprt $abt $acn gap fill $pep $tsn $mdt $bkng $adt $tal see daily on these +7/27/2026, 11:42 AM [Jesse_Livermore]: Taking a nibble on $SPY calls here. I see an H pattern intraday +7/27/2026, 11:43 AM [JustPatienceKeith]: $NOW is a beast +7/27/2026, 11:43 AM [Money]: Went in $SPCX @$109.40 Today +7/27/2026, 11:43 AM [Money]: Looking Nce +7/27/2026, 11:43 AM [Money]: Nice +7/27/2026, 11:43 AM [TreyJ]: Waiting on $MSTR to pick a direction preferably the $BTC direction +7/27/2026, 11:44 AM [2BigPete]: $MF out halt and pb +7/27/2026, 11:45 AM [Julie Coultes]: @Mikaela They're affirmations to myself as well, sis. (hugs) +7/27/2026, 11:46 AM [Marilyn]: @Jason Simmons $rtx just under ATH +7/27/2026, 11:47 AM [JOY1234]: $MSTR reports earnings at the end of the month. I am certain a direction with be confirmed soon. +7/27/2026, 11:48 AM [ChristinaLovesJaguars:]: $FIEE is halting so much, even the NASDAQ Trade Halts table is having trouble keeping up! +7/27/2026, 11:51 AM [Mikaela]: @Julie Coultes thats right. i will sit next to you 2. 😍 +7/27/2026, 11:53 AM [RahulGK80]: Any target today on Amazon please 🙏 +7/27/2026, 11:57 AM [Smoothbrain]: Even tho I made more on $MU my favorite trade was $TSLA puts @ a rejection of 315.75, had my plan wrote down and it worked perfectly, TP was @306 +7/27/2026, 11:58 AM [Marilyn]: @Jason Simmons $immr right under hod / 52wkh +7/27/2026, 11:59 AM [Julie Coultes]: @Mikaela Y'all ALL are Always welcome. =0D +7/27/2026, 12:00 PM [Julie Coultes]: @Mikaela It helps ME be acccountable to myself as well. 100% +7/27/2026, 12:00 PM [Debs]: $NFLX pushing higher. +7/27/2026, 12:01 PM [Mikaela]: @Julie Coultes we all need the reminder. anyone who says they dont....name is MIke. thats it lol +7/27/2026, 12:02 PM [Julie Coultes]: @Mikaela We're stronger and better together. +7/27/2026, 12:02 PM [Mikaela]: @Julie Coultes 😍🔥💪👊 +7/27/2026, 12:03 PM [Jay Downing]: $vtrs breakout ww this week, gap fill to 18 from 2021 +7/27/2026, 12:05 PM [Marilyn]: @Jason Simmons $rddt just on watch for the week gap not quite filled yet 5 min and 2 hr +7/27/2026, 12:06 PM [Marilyn]: @Jay Downing no charts today ? +7/27/2026, 12:07 PM [Jay Downing]: @Marilyn i got you, lost power earlier +7/27/2026, 12:07 PM [Marilyn]: 👍😃 +7/27/2026, 12:08 PM [Marilyn]: @Jay Downing nice picks 😃 +7/27/2026, 12:09 PM [Jay Downing]: @Marilyn some solid dailys today +7/27/2026, 12:09 PM [Marilyn]: 👍 +7/27/2026, 12:10 PM [Mohamed Ali]: markets making a U-turn +7/27/2026, 12:12 PM [Mikaela]: $CHWY volume spike new hod +7/27/2026, 12:13 PM [Sling]: DFNS +7/27/2026, 12:14 PM [Marilyn]: @Jason Simmons $mmsi daily 👀 steady up +7/27/2026, 12:14 PM [Zuby]: woof $NVDA +7/27/2026, 12:15 PM [2mittenz]: $DFShalted +7/27/2026, 12:15 PM [Marilyn]: @Jason Simmons $dfns halt hod +7/27/2026, 12:15 PM [GREAT_SUCCESS]: nice work mike !! +7/27/2026, 12:15 PM [Blondie]: @Michael Edward nice +7/27/2026, 12:15 PM [Burt]: @Michael Edward nice! +7/27/2026, 12:16 PM [Thrillseeker]: $DFNS only bought 25 shares to play along and it's going to pay. proves small positions with litlle risk works. Gobble up profits like pac man my new motto +7/27/2026, 12:16 PM [Daffy Duck]: We need to burn you on a stake like a witch this is some witchcraft how you knew it will squeez . :) @Michael Edward +7/27/2026, 12:16 PM [Mohamed Ali]: i got 20 shares couldnt buy more +7/27/2026, 12:16 PM [BrendanFraser]: damn, missed the bulk add +7/27/2026, 12:16 PM [GREAT_SUCCESS]: $SPY testing lod +7/27/2026, 12:16 PM [Mike H.]: I missed it! figures +7/27/2026, 12:17 PM [Mike H.]: I missed tp! +7/27/2026, 12:17 PM [Marilyn]: @Jason Simmons $vrsk hod +7/27/2026, 12:17 PM [John Wick]: @MichaelEdward What about a BUY STOP order at around $7.30 on $DFNS ? +7/27/2026, 12:17 PM [BrendanFraser]: had all morning to add t1 +7/27/2026, 12:17 PM [Thrillseeker]: @BrendanFraser you will still make bank if it's a true squeeze +7/27/2026, 12:17 PM [Burt]: Plenty opportunity on $DFNS +7/27/2026, 12:17 PM [Jace Wade]: got int at 6.93 +7/27/2026, 12:17 PM [2mittenz]: agreed Tier1 +7/27/2026, 12:18 PM [BrendanFraser]: @Thrillseeker yeah ill could be fun +7/27/2026, 12:18 PM [Bull Flag]: just watching my memory stocks bleeding lol +7/27/2026, 12:18 PM [SmokedOne]: I got in at 6.65 awesome trade mike +7/27/2026, 12:18 PM [ChristinaLovesJaguars:]: @Michael Edward You were SOOOO patient on that sideways move on $DFNS - so patient! +7/27/2026, 12:18 PM [Burt]: I got in at $6.68 +7/27/2026, 12:21 PM [Michael Edward]: BOOM +7/27/2026, 12:21 PM [Burt]: @Michael Edward 👍 +7/27/2026, 12:21 PM [GREAT_SUCCESS]: 🔥🔥 +7/27/2026, 12:21 PM [Sac1334]: @Michael Edward well done... +7/27/2026, 12:21 PM [BrendanFraser]: dang, I haven't caught a small cap with you in years. forgot how fun +7/27/2026, 12:22 PM [BAM81620]: Sometimes. lol +7/27/2026, 12:22 PM [Pamela Thomas]: lol +7/27/2026, 12:22 PM [Mohamed Ali]: this is a slow moving not too fast not too aggressive +7/27/2026, 12:22 PM [Sac1334]: small caps make me happy! lol +7/27/2026, 12:22 PM [Burt]: My retirement job +7/27/2026, 12:22 PM [Gordon Gekko]: Oh yes, just the T1 +7/27/2026, 12:22 PM [El Salsero 66]: yes +7/27/2026, 12:22 PM [JoshBoca]: Yes sir +7/27/2026, 12:22 PM [Vladimir Lerner]: i caught some +7/27/2026, 12:22 PM [TreyJ]: 6.68avg thanks +7/27/2026, 12:22 PM [dayton4440]: Caught it thx +7/27/2026, 12:22 PM [Jewels for Jules]: both tiers +7/27/2026, 12:22 PM [Mohamed Ali]: i had my tier 2 at $7.98 and it just took off +7/27/2026, 12:22 PM [Eric Webb]: YES, bought $DFNS earlier +7/27/2026, 12:22 PM [Russell-Goldminer]: I was riding from $6.43 +7/27/2026, 12:22 PM [_Knot On Duty 24/7]: I'm in thanks Mike +7/27/2026, 12:23 PM [Mikaela]: or if you dont trade that way and just ignored it all together :) +7/27/2026, 12:23 PM [KLeese]: i bailed on the stop loss under 6.50 +7/27/2026, 12:23 PM [KLeese]: bummer...just needed to hold a bit longer...ughh +7/27/2026, 12:23 PM [Michael Edward]: @KLeese why is gods name did u do that. the stop loss is 6.25 +7/27/2026, 12:23 PM [DDTraderSHO]: I was in at 6.98 out 8.5 to 9.26 at 25% intervals +7/27/2026, 12:23 PM [KLeese]: i read it wrong... just my luck +7/27/2026, 12:23 PM [Wood1]: $912. Thanks Mike +7/27/2026, 12:23 PM [Artlib]: 50 shares@6.84 +7/27/2026, 12:23 PM [KLeese]: great call +7/27/2026, 12:24 PM [Eric Webb]: $AMZN puts into earnings +7/27/2026, 12:24 PM [Birdie-Bull]: @Michael Edward you are the squeeze god +7/27/2026, 12:24 PM [El Salsero 66]: $DFNS got in @$6,83 +7/27/2026, 12:24 PM [Michael Edward]: @KLeese ugh damn its ok. get the next one. there will be more +7/27/2026, 12:24 PM [Bull Flag]: $FFIE halt +7/27/2026, 12:24 PM [Artlib]: Out @9.21 +7/27/2026, 12:25 PM [SimplyPut]: I got a good lil bit off that - good for me, anyway! Most ive made on just one equities trade... +7/27/2026, 12:25 PM [KLeese]: yep..feeling so stupid..I will get the next one..thanks! +7/27/2026, 12:25 PM [Thrillseeker]: @Michael Edward #DFNS only added my tier 1 and it's all I need with this move. Manage risk #1 +7/27/2026, 12:25 PM [Michael Edward]: @KLeese honest mistake, keep the head up like u said we'll get the next one +7/27/2026, 12:25 PM [AdriansPro]: nice spy +7/27/2026, 12:25 PM [Michael Edward]: @Thrillseeker great job +7/27/2026, 12:25 PM [Birdie-Bull]: I knew something was sus when they rolled up the GEX base +7/27/2026, 12:26 PM [James Pearson]: @KLeese Everyone makes stupid mistakes. If you don't believe me, ask my wife. +7/27/2026, 12:26 PM [TraderOne]: was waiting for that +7/27/2026, 12:26 PM [KLeese]: lol...mine will talk to you all day about my stupid mistakes +7/27/2026, 12:26 PM [James Pearson]: @KLeese Heheh cheers +7/27/2026, 12:27 PM [Artlib]: Patients pays. Been in since the open. +7/27/2026, 12:27 PM [TraderOne]: oops..that was to a diff window +7/27/2026, 12:27 PM [Michael Edward]: @Artlib well done +7/27/2026, 12:28 PM [Money]: @Michael Edward Thank You on $DFNS +7/27/2026, 12:28 PM [Michael Edward]: @Money my pleasure +7/27/2026, 12:30 PM [Artlib]: Have to thank guys for the watchlist +7/27/2026, 12:30 PM [Bull Flag]: $FIG nhod, still red on my swing +7/27/2026, 12:32 PM [Jason Simmons]: $GLD back to hod +7/27/2026, 12:33 PM [Mudman]: Made 20% on $dfns thanks Mike! +7/27/2026, 12:34 PM [Michael Edward]: @Mudman 🔥🔥 +7/27/2026, 12:35 PM [JW]: $BMNR popping back over vwap +7/27/2026, 12:36 PM [2BigPete]: $PLTR hod +7/27/2026, 12:38 PM [2BigPete]: $STAK halt on rise +7/27/2026, 12:39 PM [Mikaela]: $CHWY new hod....cmon Toby lets go +7/27/2026, 12:41 PM [Eric Webb]: $EBAY found footing, it's over its 50 SMA +7/27/2026, 12:43 PM [Marilyn]: @Jason Simmons $stak halted hod 7 mill +7/27/2026, 12:46 PM [Nas Delanoche]: @Chris Toner where is ur tp on $NEE ? +7/27/2026, 12:46 PM [Chris Toner]: @Nas Delanoche 88.5 +7/27/2026, 12:47 PM [Nas Delanoche]: @Chris Toner got it thx +7/27/2026, 12:47 PM [angelad]: i missed it was it recorded? +7/27/2026, 12:47 PM [BlessedHotMess]: @angelad yes +7/27/2026, 12:47 PM [Colin]: SUCH an impressive platform and tool +7/27/2026, 12:47 PM [Colin]: insanely cool +7/27/2026, 12:48 PM [jayprospers]: i didnt know that was going on? +7/27/2026, 12:48 PM [2 Percent All Day]: https://ai.truetradinggroup.com/dashboard/videos/live-trading-and-the-ttg-desktop-app-workshops +7/27/2026, 12:49 PM [2BigPete]: $NOW hod up 7.4% +7/27/2026, 12:49 PM [BlessedHotMess]: Thanks Mike. waiting patiently :) not worried a bit :) today successful with the help of Cha and mind set myself. now working on my LLC and finding grants +7/27/2026, 12:49 PM [BlessedHotMess]: @jayprospers he sent out notifications :) +7/27/2026, 12:50 PM [2BigPete]: $NEE lod +7/27/2026, 12:51 PM [James Pearson]: $NEE is an example where we could get in better than the mod who alerted it. +7/27/2026, 01:01 PM [OnePlus7]: H oil y +7/27/2026, 01:03 PM [Learning trader]: @OnePlus7 what does that mean? +7/27/2026, 01:05 PM [Marilyn]: @Jason Simmons $m 👀 +7/27/2026, 01:05 PM [bulgarianalien]: Congratulations to the bears I guess +7/27/2026, 01:07 PM [GREAT_SUCCESS]: $SPY one more bounce +7/27/2026, 01:07 PM [OnePlus7]: @Learning trader 🤯, H 🛢️ y oil +7/27/2026, 01:07 PM [OnePlus7]: @Learning trader oil 84.37 acting resistance +7/27/2026, 01:08 PM [2BigPete]: Airline possible merger on watch $UAL approached $DAL before going to $AAL +7/27/2026, 01:08 PM [2BigPete]: $DFNS hod +7/27/2026, 01:10 PM [Jace Wade]: 50% profits on $DFNS for those that got in with mike +7/27/2026, 01:10 PM [DollaDolla]: Nvda 195 sheesh +7/27/2026, 01:11 PM [2BigPete]: $NEE lod Closing in on 100% profit on $89 puts. In at $0.77, at $1.40 +7/27/2026, 01:11 PM [2BigPete]: $DFNS still going +7/27/2026, 01:12 PM [GREAT_SUCCESS]: $SPY doesnt hold on here we roll over into the close +7/27/2026, 01:13 PM [Michael Soares]: not sure about $DFNS at 12 here i took my last piece off at 10.80 +7/27/2026, 01:13 PM [2BigPete]: $PLTR hod +7/27/2026, 01:13 PM [GREAT_SUCCESS]: $NVDA still has room down to the 200d lgo +7/27/2026, 01:15 PM [Thrillseeker]: $NVDA hitf 100d may see a small bounce +7/27/2026, 01:15 PM [Thrillseeker]: not financial advice +7/27/2026, 01:16 PM [Mohamed Ali]: I ran out of shares $DFNS lol +7/27/2026, 01:16 PM [bulgarianalien]: I got $HOOD 92P for this friday and 90P for next a bit above 4.20 each +7/27/2026, 01:18 PM [2BigPete]: $WLDS hod +7/27/2026, 01:21 PM [Marilyn]: @Jason Simmons $team $rng both a few cents under hod +7/27/2026, 01:24 PM [Marcel Charlebois]: $DFNS why the stock move so much, i was in meetings all morning +7/27/2026, 01:26 PM [2BigPete]: Post market Monday and premarket Tuesday earnings charts up in off topic +7/27/2026, 01:27 PM [2BigPete]: $NEE lod +7/27/2026, 01:27 PM [Marilyn]: @Jason Simmons $brze hod +7/27/2026, 01:27 PM [Nas Delanoche]: $NEE lets get it.. 1.35 +7/27/2026, 01:27 PM [Zuby]: 😴 +7/27/2026, 01:27 PM [GREAT_SUCCESS]: 736.5 starting to act as res $SPY +7/27/2026, 01:28 PM [Bicycle Shorts]: Im curious as to know why today DFNS was a candidate for short squeeze? Like what was the theory behind this +7/27/2026, 01:29 PM [Marilyn]: @Jason Simmons $asan hod +7/27/2026, 01:31 PM [Marilyn]: @Jason Simmons $immr hod +7/27/2026, 01:33 PM [Tricky Trader]: @Michael Edward $dfna awesome trade. @Cha Martin $nvda crushed that one. ty so much +7/27/2026, 01:34 PM [Chris Toner]: BTC pop back over 65k +7/27/2026, 01:35 PM [Marilyn]: @Jason Simmons $pltr hod +7/27/2026, 01:37 PM [vicktor valdez]: $asml 1645 level for rejection area +7/27/2026, 01:41 PM [Mohamed Ali]: damn $DFNS was truly remarkable trade i got in at $6.92 until i ran out of shares +7/27/2026, 01:43 PM [James Pearson]: Good one +7/27/2026, 01:43 PM [Dewrantz]: $DFNS, the 50 day is at 27.47, not saying we are going there +7/27/2026, 01:44 PM [OnePlus7]: Dang it Toby +7/27/2026, 01:45 PM [Gordon Gekko]: $DFNS at 11.65 +7/27/2026, 01:46 PM [Money]: Just ran out Shares $DFNS nice $3620.00 Profit +7/27/2026, 01:48 PM [Jason Simmons]: Nice work @Money +7/27/2026, 01:48 PM [ProfitsProphet]: @Michael Edward banger trade! +7/27/2026, 01:48 PM [Analog Kid]: @Michael Edward nice! +7/27/2026, 01:48 PM [Money]: WTG @Michael Edward @Michael Edward +7/27/2026, 01:48 PM [Julie Coultes]: Green! +7/27/2026, 01:48 PM [Julie Coultes]: BOOM!@ +7/27/2026, 01:48 PM [Analog Kid]: do it! +7/27/2026, 01:48 PM [2BigPete]: $PLTR is whats up +7/27/2026, 01:48 PM [Colin]: SOOOOO sick +7/27/2026, 01:48 PM [Duck]: whoa sick +7/27/2026, 01:48 PM [Colin]: just mind blowing, on MNAY levels +7/27/2026, 01:48 PM [Analog Kid]: wow +7/27/2026, 01:48 PM [2 Percent All Day]: https://ai.truetradinggroup.com/dashboard/videos/live-trading-and-the-ttg-desktop-app-workshops +7/27/2026, 01:48 PM [Grey Beard]: It posted for you? +7/27/2026, 01:49 PM [IveGotThis]: @Michael Edward I scalped in and out on $DFNS for $825 profit. 100 hares only +7/27/2026, 01:49 PM [IveGotThis]: Thanks! +7/27/2026, 01:50 PM [Money]: @Michael Edward You Made My Days Thank +7/27/2026, 01:50 PM [JPTherapy]: can we do that now after Sunday? Or is it still being finalized? +7/27/2026, 01:51 PM [Colin]: same, not to mention, that is SO Much better for you over all trading brain... get some perspective, some fresh air +7/27/2026, 01:51 PM [Marcel Charlebois]: why +7/27/2026, 01:51 PM [bulgarianalien]: Any hope for the $SPY today!? +7/27/2026, 01:52 PM [Zuby]: Mike just made me think of the Bodybreak 80's commercial +7/27/2026, 01:52 PM [Zuby]: be active , get moving +7/27/2026, 01:52 PM [El Salsero 66]: @Michael Edward I got flat @$12 on $DFNS, in at $6.83. nice trade Mike! Thanks! +7/27/2026, 01:53 PM [Blondie]: Very nice +7/27/2026, 01:53 PM [Zuby]: yeah Semi's holding back my $CBRS long shares at 183.10 trade , and 200 weekly calls, hope we bounce it end of day or tmrw +7/27/2026, 01:53 PM [Mohamed Ali]: Semi getting cooked today +7/27/2026, 01:53 PM [Colin]: great call on the level mike, we scalped some bounecs. pretty chopy here through lunch, but we're watching for either a reclaim or rejection from our PDL level +7/27/2026, 01:56 PM [TTG GadgetGuy]: what a move on $NOW. grabbed some at 104.20. +7/27/2026, 01:56 PM [Mohamed Ali]: I would like for the Markets to bounce at these levels +7/27/2026, 01:57 PM [Trial4life Dylan]: @Colin just grabbed 15 pts off mike great bottom call +7/27/2026, 01:58 PM [Michael Edward]: @Chris Toner nice trade +7/27/2026, 01:58 PM [Michael Edward]: @Cha Martin nice trading today +7/27/2026, 01:58 PM [Michael Edward]: @Colin nice trading +7/27/2026, 01:59 PM [Glenny Trades]: Great Trade @Chris Toner +7/27/2026, 01:59 PM [Solrae]: Thanks Colin +7/27/2026, 01:59 PM [Colin]: @Trial4life Dylan NICE! yea buyers stubborn down there for sure. ES specifically, watching our PDL closely here. We've got a lot of confluence with othere elments at that level. IF byers can reclaim, we'll start looking for IBL, and PDC... potentiall back into VWAP +7/27/2026, 02:00 PM [Colin]: sellers fade this tho, close a large upper wick again rejecting IBL, easily get b ack down into l,ows. Favoring the long, very much a counter trend scalp tho +7/27/2026, 02:05 PM [DipHunter]: @Chris Toner are you still eyeing $CVNA maybe just a lil early the other week ? +7/27/2026, 02:05 PM [Trial4life Dylan]: @Colin yea it was definitely a slow bounce back up buyers not supper strong but that support been hit 3x lol +7/27/2026, 02:05 PM [Colin]: @Trial4life Dylan exactly +7/27/2026, 02:05 PM [Colin]: agreed. this PDL / EMA backtest is a big watch +7/27/2026, 02:06 PM [Chris Toner]: @DipHunter earnings wednesday, premiums elevated, will reevaluate after the report +7/27/2026, 02:06 PM [Jason Simmons]: $META still weak lod bounce , $AMZN testing prevous close +7/27/2026, 02:06 PM [Colin]: NQ too popping that LOD wedge here... but until NQ reclaims PDL, still looks pretty heavy the further up the TF's you go +7/27/2026, 02:06 PM [DipHunter]: @Chris Toner thanks +7/27/2026, 02:08 PM [2BigPete]: $WLDS hod +7/27/2026, 02:08 PM [2BigPete]: and halted on rise +7/27/2026, 02:09 PM [Mohamed Ali]: Surprisingly, $ MSFT is having a great day +7/27/2026, 02:11 PM [OnePlus7]: H oil y +7/27/2026, 02:12 PM [2BigPete]: $WLDS out and up +7/27/2026, 02:13 PM [BlessedHotMess]: @2BigPete Will never happen. government wont allow it, airlines already consolidated over the last 20 years with now only 4 major carriers owning the market. Antitrust laws and regulators would eat them for lunch. +7/27/2026, 02:14 PM [2BigPete]: @BlessedHotMess yeh not the 1st time for this BUT can still move the stock $$ +7/27/2026, 02:14 PM [vicktor valdez]: $tsla 5 min trendline rejection +7/27/2026, 02:14 PM [vicktor valdez]: looking for a pop on $asml to bring down the market +7/27/2026, 02:15 PM [GREAT_SUCCESS]: there bang +7/27/2026, 02:19 PM [Nas Delanoche]: $USO new lod +7/27/2026, 02:19 PM [OnePlus7]: H oil y TP time +7/27/2026, 02:20 PM [OnePlus7]: 82 area +7/27/2026, 02:20 PM [Jen]: 4PLTR 50 day SMA rejected +7/27/2026, 02:20 PM [OnePlus7]: @Jason Simmons what you see target? +7/27/2026, 02:21 PM [DoctorStocks]: anyone like PEP? +7/27/2026, 02:21 PM [OnePlus7]: @DoctorStocks I like sprite +7/27/2026, 02:21 PM [Michael Edward]: @DoctorStocks wonderful support confirmed in id 130s resstance 142-143 from here +7/27/2026, 02:22 PM [DoctorStocks]: ty +7/27/2026, 02:22 PM [Jason Simmons]: if 82 breaks 80 @OnePlus7 +7/27/2026, 02:22 PM [Jason Simmons]: 82 such a key area @OnePlus7 +7/27/2026, 02:29 PM [GREAT_SUCCESS]: slam it down $SPY +7/27/2026, 02:30 PM [2BigPete]: $WLDS hod and halted +7/27/2026, 02:32 PM [Vj]: @DoctorStocks $KO earnings tomorrow before open, may impact $PEP trade +7/27/2026, 02:35 PM [2BigPete]: $BIYA hod +7/27/2026, 02:36 PM [2BigPete]: $WLDS extended halt +7/27/2026, 02:36 PM [Dewrantz]: $BIYA breaking structure +7/27/2026, 02:38 PM [Mikaela]: Unky Glennys $TOST looking good over 200d +7/27/2026, 02:38 PM [Mike H.]: G! +7/27/2026, 02:39 PM [Uni]: lol +7/27/2026, 02:42 PM [Eric Webb]: $OWL earnings in 3 days, revenue should be thru the roof +7/27/2026, 02:43 PM [Dewrantz]: $HIMS broke structure +7/27/2026, 02:43 PM [Dewrantz]: I am already in the $29 calls $HIMS +7/27/2026, 02:43 PM [Mikaela]: @Dewrantz just watching that ... $HIMS +7/27/2026, 02:45 PM [Mikaela]: $CHWY also new hod woof woof +7/27/2026, 02:46 PM [2BigPete]: $PHG h news halt +7/27/2026, 02:46 PM [2BigPete]: $DFNS hod +7/27/2026, 02:47 PM [Mikaela]: or me at least lol $CHWY +7/27/2026, 02:47 PM [Mohamed Ali]: damn $DFNS punching the air +7/27/2026, 02:49 PM [Bull Flag]: $FIG nhod +7/27/2026, 02:50 PM [2BigPete]: $HIMS hod +7/27/2026, 02:50 PM [Mikaela]: $HIMS approaching 50d +7/27/2026, 02:50 PM [Eric Webb]: $OWL earnings, someone just bought 9892 Aug 21 $10 calls ~ $375,000 worth. Nothing to write home about but worth a $35 bet, open interest bearish, today's buys bullish +7/27/2026, 02:52 PM [vicktor valdez]: $asml give me a rejection at 1645 +7/27/2026, 02:52 PM [2BigPete]: $WLDS halt on rise again +7/27/2026, 02:52 PM [Bull Flag]: $DRAM 31 Jul 59c @0.55, only 1 lotto +7/27/2026, 02:55 PM [Trial4life Dylan]: @Colin there’s the es buyers +7/27/2026, 02:55 PM [Mikaela]: i like 30.88 tp for $HIMS , right under 200d is my line +7/27/2026, 02:55 PM [Dewrantz]: @Mikaela Me as well +7/27/2026, 02:56 PM [Skip]: lets see $SPY Hg says short rejection at res 737.80 - 739.20 res , looks like its going to rip thru there +7/27/2026, 02:59 PM [Julie Coultes]: @Skip I was thinking a Power Hour push back to $742 as a possibility, +7/27/2026, 03:00 PM [vicktor valdez]: $asml on the move +7/27/2026, 03:00 PM [vicktor valdez]: come on pop already +7/27/2026, 03:00 PM [GREAT_SUCCESS]: @Skip patience lets see if rejection at vwap +7/27/2026, 03:00 PM [2 Percent All Day]: Uploaded image: "Toby Says Its Powwwwwerrr Hourrr.gif" https://i.imgur.com/ZLZxxwN.gif +7/27/2026, 03:00 PM [GREAT_SUCCESS]: brrrr brrrr ppppowa hour +7/27/2026, 03:00 PM [Keiko]: Toooby Bruno Flower 🌺 Power!!!🔥🔥🔥 +7/27/2026, 03:00 PM [Keiko]: Toooby cutie +7/27/2026, 03:01 PM [Skip]: @Julie Coultes @GREAT_SUCCESS Totally appreciate it Guys, I'm running it again on $SPY Hg that is, best of all to you... +7/27/2026, 03:01 PM [Julie Coultes]: pockets! +7/27/2026, 03:02 PM [BigBallah]: @WX2 How you doing bro? +7/27/2026, 03:02 PM [BigBallah]: @Nas Delanoche Dimelo mi parce Delanoche +7/27/2026, 03:03 PM [Skip]: @GREAT_SUCCESS @Julie Coultes now HG its 62% long $SPY / 737.50 738.20 support, so maybe just chill some more +7/27/2026, 03:03 PM [BigBallah]: @Nas Delanoche How funny it did an auto correct for using a different language first time I saw that +7/27/2026, 03:05 PM [Bx-StoNe]: NeuroNests I miss you 😢 I love you ❤️ +7/27/2026, 03:05 PM [JPTherapy]: $BMNR? +7/27/2026, 03:05 PM [Eric Webb]: $MU coming back +7/27/2026, 03:06 PM [GREAT_SUCCESS]: @Skip looking for a wick off of vwap +7/27/2026, 03:06 PM [Bull Flag]: $DRAM moving +7/27/2026, 03:07 PM [Skip]: just missed that 18.50 call $19 's $QBTS there it goes +7/27/2026, 03:07 PM [JW]: BMNR hod +7/27/2026, 03:08 PM [JPTherapy]: @Chris Toner Were you the one talking about $BMNR this morning? +7/27/2026, 03:09 PM [Chris Toner]: @JPTherapy was on watch premarket, shot up off the bell +7/27/2026, 03:11 PM [JPTherapy]: @Chris Toner well thanks. got in quickly off the bell, took profit and re-entered. lookin good! +7/27/2026, 03:11 PM [Chris Toner]: @JPTherapy nice work +7/27/2026, 03:11 PM [GREAT_SUCCESS]: @Skip there +7/27/2026, 03:11 PM [vicktor valdez]: $asml wont budge +7/27/2026, 03:11 PM [vicktor valdez]: looking at vwap now for a rejcetion +7/27/2026, 03:13 PM [Skip]: @GREAT_SUCCESS 👍 +7/27/2026, 03:13 PM [GREAT_SUCCESS]: @Skip 🔥 +7/27/2026, 03:14 PM [JW]: $CLF back over vwap +7/27/2026, 03:15 PM [Chukar Fly]: @vicktor valdez Just know while the news today was not good for $ASML it is not going to make a huge dent in their business just yet. I would be surprised if it reclaims this selloff in the near future. +7/27/2026, 03:15 PM [Chukar Fly]: Wouldn't be surprised. +7/27/2026, 03:16 PM [vicktor valdez]: @Chukar Fly i scalp moves not trying to go short till 1000. but im using it to gauge the market. any big rejection ill get thos $tsla puts +7/27/2026, 03:17 PM [Eric Webb]: @Michael Edward you were spot on with $DFNS, thanks. I rarely do short squeezes, bought it right after the open, the 1/125 and 112% of the float short is insane +7/27/2026, 03:17 PM [Michael Edward]: @Eric Webb yup was nice one +7/27/2026, 03:17 PM [Chukar Fly]: @vicktor valdez gotcha. +7/27/2026, 03:18 PM [vicktor valdez]: @Chukar Fly one more move to the downside so i can go take a nap +7/27/2026, 03:18 PM [Chukar Fly]: @vicktor valdez 😄 +7/27/2026, 03:18 PM [Julie Coultes]: Beautiful levels <3 +7/27/2026, 03:19 PM [Chukar Fly]: I'd like to see $MU get back to fridays low. +7/27/2026, 03:19 PM [vicktor valdez]: @Michael Edward $asml at vwap too +7/27/2026, 03:19 PM [DollaDolla]: 735 never broke down today Green $SPY +7/27/2026, 03:19 PM [ConsistentlyImproving]: @Michael Edward $QQQ is above vwap +7/27/2026, 03:19 PM [Skip]: slighty otm calls $12 $CLF 7/31's for .36 would be nice to hold over $12 for Bell +7/27/2026, 03:20 PM [Bull Flag]: $DRAM 16 Oct 75c add@3.4 +7/27/2026, 03:20 PM [Babadoo]: @Michael Edward what's your thoughts on $DFNS? +7/27/2026, 03:22 PM [DollaDolla]: $QQQ held equal lows all day +7/27/2026, 03:23 PM [Marilyn]: @Jason Simmons $ @Jason Simmons $dfns halted hod +7/27/2026, 03:23 PM [Sac1334]: isnt Trump speaking +7/27/2026, 03:23 PM [sparty-sparky]: @Michael Edward $JPM was a good call bouncing off Friday's high +7/27/2026, 03:24 PM [Michael Edward]: @sparty-sparky ah yes very nice +7/27/2026, 03:25 PM [Skip]: sold a few .45 from .36 $12 $CLF calls 7/31 last week was in the $11's 70% long swing on HG +7/27/2026, 03:27 PM [FishteyLife]: looks like VWAP rejection is in play on $SPY +7/27/2026, 03:27 PM [Jace Wade]: @Michael Edward holding some runners on $DFNS still, 86% ahhhhh lol +7/27/2026, 03:28 PM [Skip]: there always 1 that I have my eye on I miss $QBTS (ADD) had the $18 call tee'd up 7/31 for 1.10 its gone print 1.70 +7/27/2026, 03:29 PM [Mohamed Ali]: $DFNS wow i left alot of food on the table +7/27/2026, 03:30 PM [Bull Flag]: @Cha Martin do you like $DRAM for long? +7/27/2026, 03:30 PM [Bull Flag]: memory ETF +7/27/2026, 03:31 PM [Bull Flag]: @Cha Martin$DRAM is Roundhill memory etf +7/27/2026, 03:32 PM [Skip]: $QBTS Its off 5 straight weeks of weekly losses 10 day ma holding it down 17.6 % of float short the early testing with $T workloads for network optimization reduced processing time from 1 hour to 15 sec. not bad +7/27/2026, 03:34 PM [Skip]: sold some more at .49 from .36 $12 calls $CLF 7/31 👍give us a new hod by Bell +7/27/2026, 03:35 PM [BigBallah]: @Nas Delanoche Yo yo +7/27/2026, 03:35 PM [Jace Wade]: My SL on my $DFNS runners is now $13 lol +7/27/2026, 03:35 PM [BrendanFraser]: @Jace Wade lescooo +7/27/2026, 03:35 PM [BigBallah]: @Nas Delanoche Yo how did it go today bro? +7/27/2026, 03:35 PM [Jace Wade]: @BrendanFraser yahhhhhhhhh +7/27/2026, 03:36 PM [Jace Wade]: did we just halt lol +7/27/2026, 03:36 PM [Money]: Watch $SPCX Moving up took some today $111.01 +7/27/2026, 03:36 PM [Marilyn]: @Jason Simmons $dfns new hod 🌟 and halted +7/27/2026, 03:36 PM [Nas Delanoche]: @BigBallah small green day , still have some open positions . how about u +7/27/2026, 03:37 PM [BigBallah]: @Nas Delanoche Cool green is green, me too small green and no more trades till tomorrow my man +7/27/2026, 03:37 PM [Nas Delanoche]: @BigBallah nice work bro +7/27/2026, 03:38 PM [BigBallah]: @Nas Delanoche Thank you sir +7/27/2026, 03:38 PM [Skip]: wow I actually thought it would never clear $92 and I was right this time omg $INTC has had my number lately +7/27/2026, 03:40 PM [Skip]: could not have asked for a nicer stress free close 3rd tp .54 from .36 $CLF $12 calls 7/31 no worries +7/27/2026, 03:41 PM [GREAT_SUCCESS]: he forgot to put a stop loss in +7/27/2026, 03:42 PM [John Wick]: yikes. watch out for an offering +7/27/2026, 03:43 PM [$martTrade$]: Make sure to tell your wife you will be late for dinner. :-) +7/27/2026, 03:44 PM [Mohamed Ali]: I think i am going after it too if it gets back to $12-$12:50 tight stop loss at $11:50 +7/27/2026, 03:44 PM [Skip]: /ES +7/27/2026, 03:46 PM [Jason Craig]: Glenn Trades, did you even buy more $ONDS since the 24th? +7/27/2026, 03:46 PM [Marilyn]: $wlds an activist investor filed Form 13D +7/27/2026, 03:48 PM [The Witch]: @Michael Edward would you say nows a good time to scoop up some $CRWD if I don't have any in LTP? +7/27/2026, 03:49 PM [WX2]: @BigBallah I'm good. GREEN. Took another trade on same $SOXL, didn't have the greatest entry but chicken out. Need to do trust the setup more as well as my own analysis more. But that's it, keeping all my profits +7/27/2026, 03:50 PM [Marilyn]: $biya 💥💥👀 +7/27/2026, 03:53 PM [Mark Nahas]: @michael Edward. I'm holding PayPal stock at $40 a share for my ltp would you hold it through earnings?. +7/27/2026, 03:54 PM [Prosper]: 100% $BMNR thx Toner! +7/27/2026, 03:55 PM [BigBallah]: @WX2 You love trading those highly volatile movers lol! Yes like Mike says all the time trust yr analysis +7/27/2026, 03:55 PM [Money]: $SPCX nice +7/27/2026, 03:57 PM [WX2]: @BigBallah Bro, what did u trade today? +7/27/2026, 03:57 PM [GREAT_SUCCESS]: good work today fam !!! +7/27/2026, 03:57 PM [Jason Craig]: $DFNS is for after the end of 4PM +7/27/2026, 04:00 PM [Grey Beard]: TSLA hasn't been this low since 8/6/25 +7/27/2026, 04:00 PM [Glenny Trades]: nice red to green move on ONDS +7/27/2026, 04:00 PM [BigBallah]: @WX2 I traded $WMT and $KO +7/27/2026, 04:00 PM [Cha Martin]: $NVDA 🔥🔥🔥 +7/27/2026, 04:01 PM [BigBallah]: @WX2 I wish I would of traded $NVDA +7/27/2026, 04:01 PM [BigBallah]: What a move to the downside it made +7/27/2026, 04:02 PM [Buttercup]: With oil falling our Fed Chairman is not in a hurry to raise rate. +7/27/2026, 04:02 PM [WX2]: Wow, Mike in a position after hours, that's almost non-existant +7/27/2026, 04:03 PM [Glenny Trades]: @Buttercup - chairman is one vote +7/27/2026, 04:04 PM [Glenny Trades]: @Buttercup - and it's one day of falling Earl +7/27/2026, 04:04 PM [Marilyn]: Ryanair and AWS extend agreement for another 5 years +7/27/2026, 04:04 PM [Money]: Great Day today !!! +7/27/2026, 04:04 PM [Jason Craig]: @Glenny Trades did you sell any more ONDS since the 24th? +7/27/2026, 04:04 PM [Buttercup]: @Glenny Trades Do you have to spoil my happy day? +7/27/2026, 04:05 PM [Buttercup]: I was happy to see oil falling. +7/27/2026, 04:07 PM [Glenny Trades]: @Jason Craig - I bought back some at 7.72 on 7/24 +7/27/2026, 04:07 PM [Jason Craig]: @Glenny Trades just making sure.... I actually put in about 25% or so +7/27/2026, 04:08 PM [Jason Craig]: just to keep something live +7/27/2026, 04:09 PM [Buttercup]: Done for today, face this crazy market again tomorrow. +7/27/2026, 04:09 PM [Glenny Trades]: Uploaded image: "ChatGPT Image Jul 27, 2026, 07_58_44 AM.jpg" https://i.imgur.com/4sNM1WR.jpeg +7/27/2026, 04:10 PM [Julie Coultes]: Thankss @Glenny Trades +7/27/2026, 04:10 PM [Mohamed Ali]: Wednesday & Thursday those earnings are massive +7/27/2026, 04:13 PM [Mohamed Ali]: whoaa $DFNS +7/27/2026, 04:14 PM [Glenny Trades]: LETS GO\ +7/27/2026, 04:14 PM [GREAT_SUCCESS]: send it +7/27/2026, 04:16 PM [Colin]: 👏👏👏 +7/27/2026, 04:17 PM [Bobby F.]: TOs wont let me trade $DFNS after hours +7/27/2026, 04:17 PM [Eric Webb]: $DFNS back in at $12.88, threw a sell in at $20 +7/27/2026, 04:17 PM [BigBallah]: The killa himself!!! +7/27/2026, 04:17 PM [Russell-Goldminer]: another shrimp on the barbie +7/27/2026, 04:17 PM [GREAT_SUCCESS]: 🔥🔥 +7/27/2026, 04:17 PM [Bodine]: $DFNS traded good after hours on TastyTrade +7/27/2026, 04:17 PM [DoctorFunk]: stop limit, or stop loss? +7/27/2026, 04:17 PM [WickasaurusRex]: @Bobby F. it should. Limit order ext hours +7/27/2026, 04:17 PM [GREAT_SUCCESS]: 11.$ area +7/27/2026, 04:18 PM [Michael Edward]: @DoctorFunk neither brother stops dont work after hours. im saying im going to get out via a limit sell order if it gets back to 13 +7/27/2026, 04:20 PM [Bobby F.]: @WickasaurusRex dont see that option limit order ext hours +7/27/2026, 04:20 PM [Mohamed Ali]: I had to chase this a little on the upside to $14 but i am not mad at it +7/27/2026, 04:21 PM [WickasaurusRex]: @Bobby F. hmmmm. I'm doing it on my phone. +7/27/2026, 04:21 PM [Bobby F.]: @WickasaurusRex iteresting and i do have a margin acct +7/27/2026, 04:22 PM [DoctorFunk]: Thanks, thats why i asked, but just wondered if your premium broker could work some magic. +7/27/2026, 04:24 PM [Chris Trades]: @Michael Edward next take around 19? +7/27/2026, 04:24 PM [GREAT_SUCCESS]: ahhh pppush it ppush it real good +7/27/2026, 04:24 PM [Michael Edward]: @DoctorFunk i wish lol +7/27/2026, 04:24 PM [Michael Edward]: @Chris Trades yea 19-20 +7/27/2026, 04:25 PM [Chris Trades]: thank you diff --git a/workflows/research-dfns/TODO.md b/workflows/research-dfns/TODO.md new file mode 100644 index 0000000..8807afa --- /dev/null +++ b/workflows/research-dfns/TODO.md @@ -0,0 +1,10 @@ +260727 Mike identified DFNS as a SS candidate. I took the trade around the same time he did and MARI set the stop. Well, it stopped out and a little later popped for a win. It continued all day and even a reload candidate for after hours continuation. + +I've inclued the alert and chat log from the day to analyze with other analysis of the price action that is not collected yet + +The point is: +- rev engineer what Mike saw in this one? +- why play it the way he direted? +- Conversing with MARI about it's analysis and conclusions that helped me to fail are over. Now it's on to what would I do next time? + + diff --git a/workflows/scan-watchlist-icm/CLAUDE.md b/workflows/scan-watchlist-icm/CLAUDE.md new file mode 100644 index 0000000..065df7e --- /dev/null +++ b/workflows/scan-watchlist-icm/CLAUDE.md @@ -0,0 +1,17 @@ +# Scan Watchlist ICM Workspace + +This workspace orchestrates a multi-stage watchlist confluence scan for trading ideas. +The agent follows the numbered stages to filter tickers, analyze confluence, construct trade plans, and produce a summary card. + +Folder structure: +- CLAUDE.md (Layer 0): workspace identity +- CONTEXT.md (Layer 1): workspace-level routing +- stages/: numbered stage folders + - 00_clarify/: ask key questions + - 01_broad_filter/: broad filter across tickers + - 02_confluence_analysis/: confluence analysis on shortlist + - 03_trade_plan/: trade plan construction + - 04_summary_card/: summary card creation +- _config/: Layer 3 reference material (stable across runs) +- shared/: Layer 3 shared references +- Each stage's output/ holds Layer 4 working artifacts for handoff to next stage. \ No newline at end of file diff --git a/workflows/scan-watchlist-icm/CONTEXT.md b/workflows/scan-watchlist-icm/CONTEXT.md new file mode 100644 index 0000000..05c6a28 --- /dev/null +++ b/workflows/scan-watchlist-icm/CONTEXT.md @@ -0,0 +1,16 @@ +# Workspace Context: Watchlist Confluence Scan + +## Routing +Given the goal to scan 54 tickers for trade setups with confluence, the workflow proceeds through stages: + +1. **00_clarify** - Ask clarifying questions about long/short bias, time horizon, asset class focus. +2. **01_broad_filter** - Perform broad filter across all tickers to narrow candidates. +3. **02_confluence_analysis** - Analyze confluence factors for each candidate. +4. **03_trade_plan** - Construct detailed trade plans for top setups. +5. **04_summary_card** - Produce a structured summary card of setups and sitting-on-hands list. + +## Shared Resources +- _config/: Contains references such as ticker list, default parameters. +- shared/: May contain common tools or scripts (if any). + +The agent should read the stage's CONTEXT.md for detailed inputs, process, and outputs. \ No newline at end of file diff --git a/workflows/scan-watchlist-icm/_config/trade_plan_template.md b/workflows/scan-watchlist-icm/_config/trade_plan_template.md new file mode 100644 index 0000000..15a700f --- /dev/null +++ b/workflows/scan-watchlist-icm/_config/trade_plan_template.md @@ -0,0 +1,14 @@ +# Trade Plan Template + +**Symbol:** +**Side:** (Long/Short) +**Entry Zone:** +**Stop:** +**Targets:** T1: , T2: , T3: +**Time Horizon:** +**Rationale:** +**Invalidation Condition:** +**Options Structure (if applicable):** +- Credit spread strikes: +- Bid-ask spread: +- Time decay: \ No newline at end of file diff --git a/workflows/scan-watchlist-icm/shared/cha-martin-watchlist.ms.csv b/workflows/scan-watchlist-icm/shared/cha-martin-watchlist.ms.csv new file mode 100644 index 0000000..ed27657 --- /dev/null +++ b/workflows/scan-watchlist-icm/shared/cha-martin-watchlist.ms.csv @@ -0,0 +1,55 @@ +AAPL +UPS +UBER +TSM +TSLS +TSLA +TGT +TAN +SQQQ +SPY +SPX +SOXL +SEDG +SBUX +RUN +ROKU +RIVN +RBLX +QQQ +PYPL +PLTR +PINS +PANW +NVDA +NKE +NFLX +MU +MSFT +META +KRE +INTC +HOOD +HD +GOOGL +GOOG +FSLR +FDX +ETSY +ENPH +DIS +DE +DDOG +CRWD +CRM +COST +COIN +CAT +BITO +BABA +BA +ARKK +AMZN +AMD +AFRM +ADBE diff --git a/workflows/scan-watchlist-icm/stages/00_clarify/CONTEXT.md b/workflows/scan-watchlist-icm/stages/00_clarify/CONTEXT.md new file mode 100644 index 0000000..d96eb8b --- /dev/null +++ b/workflows/scan-watchlist-icm/stages/00_clarify/CONTEXT.md @@ -0,0 +1,15 @@ +# Stage 00 Clarify: Ask Key Questions + +## Inputs +- (none) - Start of workflow + +## Process +Ask the user the following key questions to configure the scan: +1. Long only, or long + short? (Specify bias: long, short, or both) +2. Time horizon: 0DTE intraday scalps, or day/swing holds? +3. Asset class focus: Equities only, or include ETFs (SPY/QQQ/TAN/SOXL/SQQQ/KRE) in the confluence review? + +Record the answers in a markdown file. + +## Outputs +- user_preferences.md -> output/ \ No newline at end of file diff --git a/workflows/scan-watchlist-icm/stages/01_broad_filter/CONTEXT.md b/workflows/scan-watchlist-icm/stages/01_broad_filter/CONTEXT.md new file mode 100644 index 0000000..edf7e3b --- /dev/null +++ b/workflows/scan-watchlist-icm/stages/01_broad_filter/CONTEXT.md @@ -0,0 +1,18 @@ +# Stage 01 Broad Filter: Initial Ticker Screening + +## Inputs +- Layer 4 (working): ../00_clarify/output/user_preferences.md +- Layer 3 (reference): shared/cha-martin-watchlist.ms.csv + +## Process +1. Read user preferences to determine bias, time horizon, and asset class focus. +2. Load the full ticker list from the watchlist CSV. +3. Establish market context by pulling snapshot data for SPY and QQQ to determine the day's regime (trend, range, key levels). +4. Perform a batch scan (using Finviz or equivalent) filtering for: + - Price within ~3% of the 50-day MA + - Consolidation/base pattern or pullback setup + - Above/below VWAP context +5. Record the resulting shortlist of candidates (expected 10-15 tickers) for further analysis. + +## Outputs +- shortlist.md -> output/ \ No newline at end of file diff --git a/workflows/scan-watchlist-icm/stages/02_confluence_analysis/CONTEXT.md b/workflows/scan-watchlist-icm/stages/02_confluence_analysis/CONTEXT.md new file mode 100644 index 0000000..2ba6e7b --- /dev/null +++ b/workflows/scan-watchlist-icm/stages/02_confluence_analysis/CONTEXT.md @@ -0,0 +1,18 @@ +# Stage 02 Confluence Analysis: Evaluate Candidates + +## Inputs +- Layer 4 (working): ../01_broad_filter/output/shortlist.md +- Layer 3 (reference): shared/cha-martin-watchlist.ms.csv (full ticker list for reference) + +## Process +For each ticker in the shortlist, evaluate the following confluence factors: +1. Daily chart structure: load symbol, D timeframe to assess trend, price vs 50MA/200MA, support/resistance zones, base/consolidation patterns. +2. Intraday setup: load 3-min or 5-min chart to examine VWAP relationship, pre-market gap vs overnight range, opening range break potential. +3. Volume profile: check volume indicator for above-average volume confirming move or thin volume suggesting trap. +4. Options flow / unusual activity: use MCP → ttg-options chain snapshot to spot unusual call/put volume, max pain, gamma exposure. +5. Relative strength: visually compare chart to sector/market to see if holding while sector/market sells. + +Record analysis for each ticker, noting which factors align. + +## Outputs +- confluence_analysis.md -> output/ \ No newline at end of file diff --git a/workflows/scan-watchlist-icm/stages/03_trade_plan/CONTEXT.md b/workflows/scan-watchlist-icm/stages/03_trade_plan/CONTEXT.md new file mode 100644 index 0000000..4bcd5ee --- /dev/null +++ b/workflows/scan-watchlist-icm/stages/03_trade_plan/CONTEXT.md @@ -0,0 +1,23 @@ +# Stage 03 Trade Plan: Construct Detailed Trade Plans + +## Inputs +- Layer 4 (working): ../02_confluence_analysis/output/confluence_analysis.md +- Layer 3 (reference): _config/trade_plan_template.md (optional template for structuring plans) + +## Process +1. From the confluence analysis, select the top 2-4 tickers with the strongest confluence. +2. For each selected ticker: + - Load the ticker on AI chart with overlays: VWAP, 50 EMA, key support/resistance levels. + - Identify the exact entry zone, stop level, and target levels (T1/T2/T3). + - Draft a trade plan including: + * Symbol, side, entry zone, stop, targets, time horizon + * Rationale: confluence factors that align (daily structure + intraday trigger + flow confirmation) + * What invalidates it: the one condition that kills the thesis + - Given preference for credit spreads, evaluate options structure: + * Credit spread strikes (defined risk, collect premium) + * Bid-ask spread width (< $0.25 preferred for scalps) + * Time decay working in your favor +3. Compile all trade plans into a single document. + +## Outputs +- trade_plans.md -> output/ \ No newline at end of file diff --git a/workflows/scan-watchlist-icm/stages/04_summary_card/CONTEXT.md b/workflows/scan-watchlist-icm/stages/04_summary_card/CONTEXT.md new file mode 100644 index 0000000..1d028be --- /dev/null +++ b/workflows/scan-watchlist-icm/stages/04_summary_card/CONTEXT.md @@ -0,0 +1,20 @@ +# Stage 04 Summary Card: Produce Final Scan Summary + +## Inputs +- Layer 4 (working): ../03_trade_plan/output/trade_plans.md +- Layer 4 (working): ../02_confluence_analysis/output/confluence_analysis.md (for sitting-on-hands list) +- Layer 4 (working): ../01_broad_filter/output/shortlist.md (optional reference) + +## Process +1. Review the trade plans and confluence analysis to rank setups by confluence score. +2. Select the top 3-5 setups. +3. For each selected setup, extract: + - Setup type (e.g., pullback, breakout, etc.) + - Entry zone, stop level, target levels (T1/T2/T3) + - Key confluence factors that aligned + - Risk level (based on stop distance, volatility, etc.) +4. Compile a "sitting on hands" list: tickers from the shortlist that showed some promise but lacked a decisive edge (note reasons). +5. Produce a structured summary card in markdown format. + +## Outputs +- summary_card.md -> output/ \ No newline at end of file diff --git a/workflows/tool-catalog-maintainer/CONTEXT.md b/workflows/tool-catalog-maintainer/CONTEXT.md new file mode 100644 index 0000000..53a04f2 --- /dev/null +++ b/workflows/tool-catalog-maintainer/CONTEXT.md @@ -0,0 +1,66 @@ +# Tool: Tool Catalog Maintainer + +## Purpose +Create and maintain a `README.md` catalog for a user-specified directory containing subfolders of tools, prompts, scripts, docs, workflows, skills, or other reusable resources. + +The README is a living catalog. It should improve over time as new subfolders are added and existing ones are updated. Future humans and LLM agents will refer to this README to decide which resource to use for a request. + +Invoke this tool when the user asks to: + +- create a catalog README for a folder of tools/resources +- update an existing catalog after tools change +- summarize available prompts, scripts, docs, workflows, or reusable assets +- make a directory easier for LLMs to navigate +- document a collection of reusable tools +- generate or refresh an index for agent skills, prompts, scripts, references, or workflows + +## Inputs + +| Layer | Path | Required | Notes | +| --- | --- | --- | --- | +| Layer 4 working | `/` | Yes | The folder the user points to. It should contain one or more direct subfolders to catalog. | +| Layer 4 working | `/README.md` | No | Existing catalog to preserve and improve when present. | +| Layer 3 reference | `tools/tool-catalog-maintainer/references/catalog-format.md` | Yes | Defines the recommended README structure and cataloging rules. | + +## Process + +1. Confirm the target folder exists. +2. Inspect the target folder's direct subfolders. Treat each direct subfolder as one catalog entry unless the user's request says otherwise. +3. For each subfolder, inspect enough contents to understand its purpose and use: + - `README.md`, `CONTEXT.md`, `SKILL.md`, `PROCEDURE.md`, and other Markdown files + - prompt files + - scripts such as `.py`, `.sh`, `.js`, `.ts`, `.rb`, `.go`, etc. + - config files such as `package.json`, `pyproject.toml`, `requirements.txt`, `uv.lock`, `.env.example` + - `references/`, `docs/`, `assets/`, `output/`, or similarly named support folders +4. Do not deeply read generated outputs, large dependency folders, archives, or binary assets unless they are necessary to identify the tool. +5. If a catalog README already exists, preserve useful existing content and improve it rather than replacing blindly. +6. Write for future LLM consumption: + - use explicit folder names and paths + - state when to use each tool + - name key files and entry points + - call out setup requirements and cautions + - prefer structured tables plus short per-tool sections +7. Create or update `/README.md` using the format in `references/catalog-format.md`. +8. Verify the README covers every relevant direct subfolder and does not invent capabilities not supported by the inspected files. + +## Outputs + +Update or create: + +```text +/README.md +``` + +The README should be a durable catalog, not a one-time summary. + +## Verify + +Before finishing, verify that: + +- the target folder exists +- every relevant direct subfolder is represented in the catalog +- each entry has a purpose and “when to use” guidance +- key files or entry points are listed where known +- setup or dependency notes are included when visible +- existing README content was preserved when useful +- unsupported claims were avoided diff --git a/workflows/tool-catalog-maintainer/README.md b/workflows/tool-catalog-maintainer/README.md new file mode 100644 index 0000000..f02389c --- /dev/null +++ b/workflows/tool-catalog-maintainer/README.md @@ -0,0 +1,21 @@ +# Tool Catalog Maintainer + +This folder contains the `tool-catalog-maintainer` ICM tool/agent skill. + +## Start here + +- Agent operating contract: [`CONTEXT.md`](CONTEXT.md) +- Agent Skills adapter: [`SKILL.md`](SKILL.md) +- Catalog README format rules: [`references/catalog-format.md`](references/catalog-format.md) + +## Intent + +Use this tool to create or update a living `README.md` catalog for a target folder of tools, prompts, scripts, docs, workflows, skills, or reusable resources. + +Example request: + +```text +Use tool-catalog-maintainer on tools/ +``` + +`CONTEXT.md` is the source of truth for how the tool runs. Keep this README as a short landing page only. diff --git a/workflows/tool-catalog-maintainer/SKILL.md b/workflows/tool-catalog-maintainer/SKILL.md new file mode 100644 index 0000000..15e1761 --- /dev/null +++ b/workflows/tool-catalog-maintainer/SKILL.md @@ -0,0 +1,52 @@ +--- +name: tool-catalog-maintainer +description: Creates and maintains a README.md catalog for a directory containing subfolders of tools, prompts, scripts, docs, workflows, skills, or reusable resources. Use when asked to catalog, index, summarize, or update documentation for a folder of tools so humans or LLMs can quickly choose the right resource. +--- + +# Tool Catalog Maintainer + +## Purpose + +Create and maintain a `README.md` catalog for a user-specified directory containing subfolders of tools, prompts, scripts, docs, workflows, skills, or other reusable resources. + +The README is a living catalog. It should improve over time as new subfolders are added and existing ones are updated. Future humans and LLM agents will refer to this README to decide which resource to use for a request. + +## When to use + +Use this skill when the user asks to: + +- create a catalog README for a folder of tools/resources +- update an existing catalog after tools change +- summarize available prompts, scripts, docs, workflows, or reusable assets +- make a directory easier for LLMs to navigate +- document a collection of reusable tools +- generate or refresh an index for agent skills, prompts, scripts, references, or workflows + +## Workflow + +1. Confirm the target folder exists. +2. Inspect the target folder's direct subfolders. Treat each direct subfolder as one catalog entry unless the user says otherwise. +3. For each subfolder, inspect enough contents to understand its purpose and use: + - `README.md`, `CONTEXT.md`, `SKILL.md`, `PROCEDURE.md`, and other Markdown files + - prompt files + - scripts such as `.py`, `.sh`, `.js`, `.ts`, `.rb`, `.go`, etc. + - config files such as `package.json`, `pyproject.toml`, `requirements.txt`, `uv.lock`, `.env.example` + - `references/`, `docs/`, `assets/`, `output/`, or similarly named support folders +4. Do not deeply read generated outputs, dependency folders, archives, or binary assets unless needed to identify the tool. +5. If a catalog README already exists, preserve useful existing content and improve it rather than replacing blindly. +6. Write for future LLM consumption: + - use explicit folder names and paths + - state when to use each tool + - name key files and entry points + - call out setup requirements and cautions + - prefer structured tables plus short per-tool sections +7. Create or update `/README.md` using `references/catalog-format.md`. +8. Verify the README covers every relevant direct subfolder and does not invent unsupported capabilities. + +## Output + +Create or update: + +```text +/README.md +``` diff --git a/workflows/tool-catalog-maintainer/output/.gitkeep b/workflows/tool-catalog-maintainer/output/.gitkeep new file mode 100644 index 0000000..e69de29 diff --git a/workflows/tool-catalog-maintainer/references/catalog-format.md b/workflows/tool-catalog-maintainer/references/catalog-format.md new file mode 100644 index 0000000..cf147b0 --- /dev/null +++ b/workflows/tool-catalog-maintainer/references/catalog-format.md @@ -0,0 +1,60 @@ +# Catalog README Format + +Use this reference when creating or updating a catalog README for a folder of tools, prompts, scripts, docs, workflows, or other reusable resources. + +## Recommended README shape + +```markdown +# Tool Catalog + +This README catalogs the tools and resources in this directory. It is intended for humans and LLM agents to quickly identify what is available and when to use it. + +## Catalog + +| Tool / Folder | Purpose | Key Files | When to Use | +| --- | --- | --- | --- | +| `example-tool/` | Brief summary of what it does. | `README.md`, `script.py` | Use when... | + +## Tools + +### `example-tool/` + +**Purpose:** +Describe what this tool/resource does in 1–3 sentences. + +**Contents:** +- `README.md` — usage notes and overview +- `script.py` — command-line entry point +- `references/` — supporting documentation + +**Use when:** +Describe the requests or situations where an agent should choose this tool. + +**Setup / dependencies:** +List visible install steps, runtimes, package managers, API keys, or “None noted.” + +**Notes:** +Include cautions, output locations, maintenance hints, or limitations. + +## Maintenance Notes + +When adding or updating a tool folder, update this README with: + +- purpose +- key files and entry points +- usage guidance +- setup requirements +- notable changes or cautions +``` + +## Cataloging rules + +- Prefer accuracy over completeness. If purpose is unclear, say so and name the files inspected. +- Do not claim a tool can do something unless the files support it. +- Keep the table compact; put detail in the per-tool sections. +- Include exact relative paths so future agents can load the right files quickly. +- Distinguish source files from generated `output/` artifacts. +- Mention whether a tool is prompt-only, script-driven, documentation-only, or a workflow. +- If a folder has its own README, use it as the primary source but still verify key files. +- Preserve useful existing catalog notes during updates. +- Remove stale entries only when the corresponding folder is gone or clearly obsolete.