Skip to content

Article Catalog ​

Start with the nine architecture principles and seven engineering methods to orient your reading. Every article links back to that map, whether or not it belongs to a numbered principle.

This library lists the original Chinese essays in three canonical categories. Completed English translations live under /en/articles/<slug> and share the same slug as the original.

Availability: Fully translated articles link directly to their English Markdown and localized Mermaid/table content. “Chinese original” means a full English edition has not yet been published; those links still lead to the original Chinese text.

ESSENTIAL READING · START HERE

01 / THE SYSTEM MAPSix-layer request lifecycle V3Follow a question through admission, context, Main and subagents, optional tools, Publication and the user interface.Read the complete architecture →02 / THE DECISION MAPNine architecture principlesUnderstand who owns semantics, permission, effects, recovery and the complexity of long-lived systems.Explore the core principles →
CURATED READING PATHS3 categories · 63 articles
MODULE DEEP DIVES

01 / Module Deep Dives

Concrete mechanisms from input through execution to delivery.

31 articles →
01 / 04

Research, Reading and Computing

How Entry, Web, PDF, subagents and isolated computation cooperate.

  1. Entry: Why the Entry Point Became Simpler (Chinese original)
  2. Web Research: From Search to Deep Reading (Chinese original)
  3. When an Agent Says Today: User Time and Market Sessions
  4. PDF: From Text to Evidence
  5. Subagents: Isolation and Specialized Collaboration
  6. A Custom Expert Should Be More Than a Prompt Field
  7. Adaptive Research and Python
  8. Python: From Tool to Computational Workbench
  9. Connecting Portfolio Data Through a Read-Only MCP (Chinese original)
  10. Controlled Refresh for Stale Data
02 / 04

Context, Results and Knowledge

What the model sees and which evidence it may read.

  1. Externalized Results and Input Completeness
  2. Main Context Compaction Without Rewriting Facts
  3. Memory: From Saving and Recall to Safe Forgetting
  4. RAG: Revocation and Historical Replay
03 / 04

Runtime, Extensions and Observability

How capabilities are discovered, authorized, executed and observed.

  1. Provider: Why a Unified API Still Needs Shared Admission
  2. Why the Next Model Request Still Queues After HTTP 200
  3. Extension Host: From Feature Phone to Smartphone
  4. MCP Host: From Discovery to Usable Tools
  5. Tool Surface: Why the Model Cannot See an Available Tool
  6. Prompt Injection Is More Than Malicious Text: An Agent Content Trust Boundary
  7. Multi-Ecosystem Hooks: Claude, Pi and Codex
  8. Observing the Tool-to-Model Input Lifecycle
  9. Run Budget and Constraint Governance
  10. Agent Usage: Requests, Tokens and Shadow Credits
  11. Why an Agent Cannot Execute a Stop Command Immediately
  12. Scheduled Research Beyond a Conversation
  13. Langfuse: From Traces to Trustworthy Observability
04 / 04

Answer Delivery and Recovery

An answer candidate, durable effects and delivery are separate facts.

  1. Publication: Why Answers Need Their Own Delivery System (Chinese original)
  2. Keeping Progressive Answers Coherent
  3. Async Research: Delivering on Time After Users Leave
  4. After an Agent Asks: Durable Human Response Adoption
ARCHITECTURE & SYSTEMS THINKING

02 / Architecture and Systems Thinking

System boundaries, responsibility, reliability and change.

24 articles →
01 / 04

Deep and Continuous Research

Long-running background research, staged delivery, recovery and continuity of investment theses.

  1. Keep Chatting: Adding Async Background Research to an Agent in a Day
  2. After the Weekly Report, Does the Agent Remember Why?
  3. Why Saved HTML Can Still Fail Delivery
  4. Failover: Change the Route Without Resetting the Task
  5. Run Termination, Stage Budgets and Safe Recovery
02 / 04

Subagents and Experts

Investment perspectives, bounded peer dialogues and collaboration across expert agents.

  1. More Than One Investment Expert: How Multi-Perspective Agents Test an Investment Thesis
  2. When Two Agents Talk Directly: Bounded Bull–Bear Research
  3. From Multiple Experts to One Research Result: The Next Step for Multi-Layer Agents (2026 Outlook)
03 / 04

Finance and Engineering

Financial evidence, reproducible results, system evolution and end-to-end engineering quality.

  1. Why Financial Market MCP Became a Decision System
  2. Boundaries Between Research, Advice and Trading
  3. Financial Data: Time, Definitions and Reproducibility
  4. Why Python Results Can Still Be Misused in Reports
  5. A Trustworthy Evidence Chain for Financial Agents (Chinese original)
  6. A Research Agent Needs More Than Tools: Model, Harness, and Loop
  7. Why More Citations Do Not Prove Reliability
  8. Building an ETF Research Assistant
  9. Code Is Cheaper; Why Are Systems Harder to Evolve?
  10. What Should Stay Stable—and What Should Change—in an Agent Architecture?
  11. Stop Blaming Every Failure on the Model
  12. Local Improvements Are Not System Progress
04 / 04

Other Architecture Topics

System overviews, model/runtime responsibilities, authorization and capability ownership.

  1. Six-Layer Request Lifecycle V3: From Prompt to Visible Answer
  2. Models Understand; Code Authorizes
  3. Don't Turn the Model into a State Machine
  4. Responsibilities of Model, Runtime, MCP and Skills
AI-ASSISTED ENGINEERING

03 / AI Agent Engineering Practice

How coding agents develop, validate, maintain and evolve software.

8 articles →

Historical architecture editions ​

The current six-layer V3 lifecycle is the one canonical reading entry. The complete V2 English edition and the V1 Chinese original remain readable as dated historical snapshots and are not counted again.

Engineering notes, evidence and boundaries. · Contact: hpoenixf@foxmail.com · WeChat: hpoenixf0510