Architecture and Systems Thinking
Explore ownership, authorization, reliability and evolution across modules—and whether a change improves the result users receive.
These reading groups are not a product-release checklist. Each article distinguishes design, bounded verification and actual delivery. Links marked “Chinese original” lead to articles without a published English edition.
Counts include articles in this category only; related reading is listed separately.
Deep and Continuous Research
Long-running background research, staged delivery, recovery and continuity of investment theses.
- Agent Client Interaction Panorama: From Asking a Question to Understanding Results and Continuing Research
- Long-Horizon Research Panorama: Continuing Across Context, Interruptions and Time
- Designing Half-Hour Agent Research: From Ordinary Research to Reliable Delivery
- Keep Chatting: Adding Async Background Research to an Agent in a Day
- From Investment-Research Chat to Ongoing Research: Lessons from DeepSeek Super-agent
- After the Weekly Report, Does the Agent Remember Why?
- Why Saved HTML Can Still Fail Delivery
- Failover: Change the Route Without Resetting the Task
- A Disconnected Browser Is Not a Crashed Agent
- Run Termination, Stage Budgets and Safe Recovery
- A Research Agent Needs More Than Tools: Model, Harness, and Loop
- Deep Research: From Budget Upgrades to Delivery—What We Built and What the Tests Show
- Adaptive Research and Python
- Async Research: Delivering on Time After Users Leave
- Keeping Progressive Answers Coherent
Subagents and Experts
Investment perspectives, bounded peer dialogues and collaboration across expert agents.
Financial Research and Business Accountability
Financial data and calculation semantics, research-service boundaries and investment-business responsibilities.
- After General-Purpose Agent Frameworks, Why Build Financial Domain Capabilities?
- From a General Harness to Financial Research: A Four-Way Architecture Comparison of ETF Agent
- Financial Agents in Context: Systems, Lifecycles, and Accountability
- Trusted Handoffs Between Financial Business Agents: Why a Router Is Not Enough
- Why Financial Market MCP Became a Decision System
- Boundaries Between Research, Advice and Trading
- Financial Data: Time, Definitions and Reproducibility
- Why Python Results Can Still Be Misused in Reports
- Why Can a Fund Research Report Still Make Unsupported Conclusions?
Architecture Learning Path
An ordered getting-started series: concepts, execution, system design, hands-on research, roles, review and the six-layer architecture.
- Agents in 15 Minutes
- Prompt, Context, RAG and Memory — Where Does the Model Input Come From?
- Agent Intermediate: Ten Core Modules in Open ETF Agent
- Tools, Function Calling, MCP and Skills — How Does an Action Happen?
- History, Context, Memory and Checkpoints — How Does an Agent Continue?
- Agent Execution Identity Panorama: From a Conversation to Model Turns—What Actually Continues?
- Agent Deep Dive: From One Report to Durable Execution and Specialist Collaboration
- Bring Your Own Documents to an Agent: From the First Report to a Resumable Research Project
- Expert, Subagent, Review, Judge: If They All Use Another Model, Why Are They Different?
- After the report: source checks, specialist work, and independent review
- Six-Layer Request Lifecycle: From Prompt to Visible Answer
- Agent Context Governance Panorama · Principles: Keep Every Decision Aligned with the Goal
- Agent Context Governance Panorama · Practice: From the First Request to Long-Term Memory
System Boundaries and Evolution
Cross-module evidence, responsibility, failure attribution, reliability and long-term architecture evolution.
- ETF Agent vs LangGraph: Concept Mapping, Recovery, and Research Delivery
- From Chat to Copilot to Agent: What Actually Changes in the Architecture?
- Why Split an Agent into Three Processes? Independent Lifecycles Without Splitting Business Truth
- How Agent Development Differs from Backend Development: From One Request to a Long-Term Personal Assistant
- Nine Architecture Judgments Behind One Report
- What to Trust in Agent Engineering: From Local Facts to System Commitments
- Agent Fragility and Antifragility: When Safeguards Start Causing Failures
- The Failure Is Already Known. Why Hasn't the Call Returned? Cleanup and Result Ownership
- Don't Turn the Model into a State Machine
- Responsibilities of Model, Runtime, MCP and Skills
- A Trustworthy Evidence Chain for Financial Agents
- Why AI Agents Need Thinking, Fast and Slow
- Designing Agent Citations: From Host-Issued References to Revision-Safe Independent Review
- Code Is Cheaper; Why Are Systems Harder to Evolve?
- What Should Stay Stable—and What Should Change—in an Agent Architecture?
- Stop Blaming Every Failure on the Model
- Local Improvements Are Not System Progress
- Agent Observability Panorama: From Model Requests to Verifiable Research Facts
- What Does an Agent-Generated Report Actually Cost?
- Observing the Tool-to-Model Input Lifecycle
Modules · Engineering · Finance · Panorama · All articles