Skip to content

Latest commit

 

History

History
62 lines (49 loc) · 3.68 KB

implementation-plan.md

File metadata and controls

62 lines (49 loc) · 3.68 KB

Implementation plan

English | 简体中文

Status: macOS source development is active. Windows read-only implementation is in progress; native acceptance is pending. Use acceptance for verification criteria and SYNC.md for platform alignment.

See the next-release development plan for capability improvements, release options and concrete work packages. It does not replace owning product contracts or actual acceptance status.

Product decisions

Decision Contract
DEC01 Shou / 收拾一下; consistent product identity
DEC02 Native macOS SwiftUI/AppKit with Swift domain services
DEC03 Desktop and CLI independently call their platform's shared domain services
DEC04 Optional cleanup AI proposes drafts; deterministic validation and confirmed execution own mutations
DEC05 External agents use discoverable public CLI commands
DEC06 Windows uses C# / .NET 10 LTS / WinUI 3 and an independent C# Core
DEC07 Prioritize storage evidence, reusable rules and safe daily cleanup
DEC08 English and Simplified Chinese engineering docs; Chinese/English runtime resources and 11 README languages

Delivery sequence

flowchart LR
    Contracts[Product and safety contracts] --> Mac[macOS implementation and acceptance]
    Contracts --> WN01[Windows toolchain and signed shell]
    WN01 --> WN02[Pure Core and Presentation]
    WN02 --> WN03[Read-only native vertical slice]
    WN03 --> WN04[Confirmed cleanup and recovery]
    WN04 --> WN05[Feature increments]
    WN05 --> WN06[Distribution acceptance]
Loading

macOS priorities are scan correctness, current evidence, immutable plans, durable item receipts, recovery, bounded performance and native interaction. Implement product improvements in small independently verifiable slices. Windows stages and their exit criteria are defined in the native plan. Portable logic and read-only source work have started; no stage has completed its required native acceptance.

AI work packages

Work item Scope
AI01 Annotated generated cases and investigation-quality baseline
AI02 macOS model SDK and transport behavior, cancellation and budgets
AI03 Bounded evidence tools, investigation state and disabled drafts
AI04 Protocol, endpoint, model and independent credential configuration
AI05 Native entry points, questions, current states and rule preview
AI06 Quality, privacy, safety, offline cleanup and actual-service acceptance
AI07 Default-off switch and request revocation
AI08 Local handling, structured decision routing and necessary escalation
AI09 Contextual launches from cleanup, space, large files and personal rules
AI10 State, accessibility and user-journey acceptance
AI11 Public CLI contract and independently implemented Windows parity

The macOS investigation source exists; tests and native interaction establish only their executed scope. Windows AI remains planned and must use the .NET implementation boundary. See AI implementation and AI acceptance.

Definition of done

  • The owning product, safety, data and CLI contracts agree.
  • Code implements the smallest current capability without speculative frameworks.
  • Relevant domain, CLI, native and UI checks have recorded results.
  • Shared resources are reproducible and both documentation editions agree.
  • Capability availability, platform differences and pending work are accurate in the ledger.
  • Signing, install and update claims have independent native evidence.