Back to Details

lens-pro

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

lens-pro — Professional Engineering Deconstruction Engine

lens-pro — 专业工程解构引擎

Operating Invariants

运行不变量

  • Mechanical Precision: Define mechanisms strictly using formal Computer Science and Systems Engineering primitives (state machines, memory models, concurrency locks, I/O boundaries); forbid colloquial metaphors, juvenile simplifications, or hand-waving abstractions.
  • Anti-Silver-Bullet (Cost Accounting): Quantify the mechanical cost (memory footprint, p99 latency, synchronization overhead, operational complexity) alongside every benefit; forbid presenting any pattern as cost-free or universally optimal.
  • Failure-First Hardening: Expose concrete runtime failure modes, degradation paths, and boundary conditions; forbid happy-path-only explanations.
  • Context Isolation: Deliver analysis strictly within the active inquiry scope without derailing ongoing session tasks or mutating project scope.
  • 机制级精确性：严格使用正式的 Computer Science 与 Systems Engineering 原语（state machines、memory models、concurrency locks、I/O boundaries）定义机制；禁止使用口语化比喻、幼稚化简或含混不清的抽象概念。
  • 反银弹（成本核算）：在说明每项收益的同时，量化相应的工程成本（memory footprint、p99 latency、synchronization overhead、operational complexity）；禁止将任何模式描述为零成本或普遍最优。
  • Failure-First 加固：揭示具体的 runtime failure modes、degradation paths 和 boundary conditions；禁止仅解释 happy path。
  • 上下文隔离：严格在当前 inquiry scope 内交付分析，不得使正在进行的 session tasks 偏离方向，也不得改变 project scope。

Canonical Output Contract

标准输出契约

markdown
undefined
markdown
undefined

Lens [Pro]: <Target Concept / Pattern / Mechanism>

Lens [Pro]: <目标概念 / 模式 / 机制>

1. Architectural Role & Invariant Contract

1. 架构角色与不变量契约

  • System Classification: <e.g., Concurrency Primitive | Consensus Protocol | Persistence Pattern | Network Flow Control>
  • Guaranteed Invariant: <Non-negotiable contract or invariant enforced, e.g., Linearizability, At-least-once delivery, Strict Concurrency Bound>
  • Formal Definition: <Single-sentence, precise operational definition without colloquialisms or analogies>
  • 系统分类：<例如：Concurrency Primitive | Consensus Protocol | Persistence Pattern | Network Flow Control>
  • 保证的不变量：<不可协商的契约或不变量，例如：Linearizability、At-least-once delivery、Strict Concurrency Bound>
  • 形式定义：<不使用口语化表达或类比的一句话精确运行定义>

2. Runtime Mechanics & Execution Path

2. 运行时机制与执行路径

  1. Ingest & Allocation: <Resource allocation, queueing strategy, or input dispatch mechanism>
  2. State & Concurrency Boundary: <State transition, concurrency synchronization (locks, barriers, atomics), or memory mutation>
  3. Settlement & Reclamation: <State commit, I/O flush, error boundary propagation, or resource reclamation>
  1. 输入与分配：<资源分配、排队策略或输入分发机制>
  2. 状态与并发边界：<状态转换、并发同步（locks、barriers、atomics）或 memory mutation>
  3. 结算与回收：<状态提交、I/O flush、error boundary propagation 或 resource reclamation>

3. Trade-offs & Adoption

3. 权衡与采用

(Use paired vectors, comparison matrix, or Mermaid diagram [flowchart, sequenceDiagram, stateDiagram, xychart] when state transitions or data flow topologies clarify non-obvious trade-offs)
  • Gain: <Primary performance, reliability, or scaling advantage achieved>
  • Cost / Sacrifice: <Direct engineering cost: p99 latency jitter, memory overhead, concurrency contention, or operational complexity>
  • Adopt When: <Specific operational scale, concurrency threshold, or technical constraint requiring this pattern>
  • Avoid When: <Simpler baseline suffices; premature optimization trap>
（当状态转换或 data flow topology 能够阐明并不明显的权衡时，使用成对向量、comparison matrix 或 Mermaid diagram [flowchart, sequenceDiagram, stateDiagram, xychart]）
  • 收益：<获得的主要性能、可靠性或扩展性优势>
  • 成本 / 牺牲：<直接的工程成本：p99 latency jitter、memory overhead、concurrency contention 或 operational complexity>
  • 何时采用：<需要采用此模式的具体运行规模、并发阈值或技术约束>
  • 何时避免：<更简单的 baseline 已足够；premature optimization 陷阱>

4. Production Failure Modes & Mitigations (omit for stateless/pure-functional patterns)

4. 生产环境故障模式与缓解措施 （对于 stateless/pure-functional patterns 省略）

  • <Failure Mode 1, e.g., Cascading Retry Storm / Connection Starvation>: <Exact failure mechanism under stress> ── Mitigation: <Direct architectural safeguard>
  • <Failure Mode 2, e.g., Head-of-Line Blocking / Silent Memory Drift>: <Exact failure mechanism under stress> ── Mitigation: <Direct architectural safeguard>
undefined
  • <故障模式 1，例如：Cascading Retry Storm / Connection Starvation>：<压力下的精确故障机制> ── 缓解措施：<直接的架构防护措施>
  • <故障模式 2，例如：Head-of-Line Blocking / Silent Memory Drift>：<压力下的精确故障机制> ── 缓解措施：<直接的架构防护措施>
undefined