KyoheiG3/Plan

This system is a state management and dispatching architecture for iOS and macOS applications, centered around the 'Plan' framework. It provides a structured approach to managing application state and actions through an Interactor, Dispatcher, and Store, supporting concurrent action dispatching and thread-safe state updates. The system includes example projects demonstrating clean architecture and UI cataloging, along with comprehensive testing infrastructure via fastlane and unit tests.

A new iOS example application built with ReactiveCocoa (RAC) and ReactiveSwift is added, providing a complete reference implementation of the architecture. The example includes multiple view controllers (Entrance, Home, Login, MyPage, UserEdit) with their corresponding use cases, presenters, and UI components. A Catalog app is introduced to showcase all UI components via Playbook scenarios, enabling visual regression testing through snapshot tests that capture UI states across different devices and user conditions.

Examples/Example-iOS-RAC · high confidence

A new example project has been added to demonstrate a clean architecture implementation using the Plan framework. The entry includes a README.md file that explains the project's structure, which is divided into two apps (Example.app and Catalog.app) and five frameworks (Presentation, Gateway, UseCase, Component, and Domain). The architecture enforces dependency isolation by limiting Component to Boundary and Entity, facilitating easier testing. A plan.pu file provides a visual representation of the dependencies between these layers.

Examples · high confidence

The Plan.xcodeproj project file, workspace configuration, and run scheme have been added to the repository. This establishes the build configuration for the Plan framework and its associated unit tests (including Executor, Atomic, Dispatcher, Translator, Interactor, and Presenter), enabling developers to build and run the test suite directly within Xcode.

Plan.xcodeproj · high confidence

The fastlane directory now includes an Appfile and a Fastfile that define an iOS build lane named 'run\_project\_tests'. This lane executes tests using fastlane's scan tool, targeting the 'Plan' scheme on an iPhone 11 Pro device. A README.md has also been added to document the available fastlane actions.

fastlane · high confidence

Added a new Plan module providing a structured approach to managing application state and actions. This includes an Interactor base class for handling actions, a Dispatcher system that routes actions through a Translator to update a Store, and an Executor for managing asynchronous work on specific queues (immediate, main thread, or custom). The architecture supports multiple interactors dispatching actions concurrently, with thread-safe state updates via the Atomic wrapper and queue-based execution.

Plan · high confidence

A new configuration file, Plan.xcconfig, has been added to the Support Files directory. This file establishes the default build settings for the Plan project, specifically setting the Swift version to 5.0 and defining deployment targets for iOS (10.0), macOS (10.12), tvOS (10.0), and watchOS (3.0). It also explicitly lists the supported platforms, ensuring consistent build environments across Apple ecosystems.

Support Files · high confidence

Added comprehensive unit tests for the Plan architecture, covering the core components: Atomic operations, Dispatcher, Executor, Interactor, Presenter, and Translator. The test suite includes mock implementations for testing the flow of actions through the system, ensuring that dispatching actions correctly triggers translations and store updates.

PlanTests · high confidence

The Plan library is now available via Swift Package Manager and CocoaPods, enabling easier integration into iOS, tvOS, and macOS projects. The Swift Package Manager configuration defines the Plan target and its dependencies, while the CocoaPods podspec specifies version 0.2.1 and sets deployment targets for iOS, tvOS, macOS, and watchOS.

(dependencies) · high confidence

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

• CAI 69 → 66 (-3.0)
• Rubric changed (rubric-2026.08.19 → rubric-2026.09.15) — scores are not directly comparable.

• Code Health 100 → 95 (-4.7)
• Architecture 100 → 97 (-2.5)
• Maturity 62 → 66 (+4.0)
• Readiness 57 → 53 (-3.8)
• Security 92 → 85 (-7.1)

• Coverage not included — suite not readable by the collector
• Dependency hygiene not measured — dependency manifest found but not parsed for hygiene
• No exposed public API
• Test reliability not included
• The overview section describes a single ideal processing flow diagram but does not explain how the five main types (Interactor, Dispatcher, Store, Translator, Presenter) fit together in the actual architecture. (README.md)
• complexity unreadable for .swift — churn × complexity hotspots could not be measured
• early-stage repository — too little history to judge knowledge freshness
• single-maintainer — knowledge-concentration (bus factor) risk

• Ambiguous constructor overloading for AnyDispatcher. One initializer takes a generic D (likely a concrete dispatcher type), and the other takes a closure. This creates confusion about whether D is a type-erased wrapper or a concrete implementation. If D is meant to be any type conforming to a protocol, the signature should explicitly state the constraint (e.g., init<D: Dispatcher>(_ dispatcher: D)). The current signature init(D) is syntactically incomplete in Swift (missing generic constraint or type alias definition context), suggesting a potential API design flaw where the intent of D is unclear compared to the explicit closure initializer.
• Coverage not measured — Swift suite
• Dependency hygiene PARTLY measured — SwiftPM pinning read, dependency currency NOT established
• Documentation: no architecture or design documentation (README.md)
• Documentation: no installation or build instructions (README.md)
• Documentation: no usage examples (README.md)
• Duplicated block (10 lines × 2) (Examples/Example-iOS-RAC/Catalog/SceneDelegate.swift)
• Duplicated block (10 lines × 2) (Examples/Example-iOS-RAC/Gateway/Repositories/UserRepository.swift)
• Duplicated block (11 lines × 2) (Examples/Example-iOS-RAC/Component/Components/MyPage/MyPageViewController.swift)
• Duplicated block (11 lines × 2) (Examples/Example-iOS-Rx/Component/Components/Home/HomeViewController.swift)
• Duplicated block (12 lines × 2) (Examples/Example-iOS-RAC/Component/Components/Home/HomeViewController.swift)
• Duplicated block (12 lines × 2) (Examples/Example-iOS-RAC/Component/Components/Login/LoginViewController.swift)
• Duplicated block (12 lines × 2) (Examples/Example-iOS-RAC/Component/Components/MyPage/Entities/MyPageItem.swift)
• Duplicated block (12 lines × 2) (Examples/Example-iOS-RAC/Component/Components/MyPage/MyPageViewController.swift)
• Duplicated block (12 lines × 2) (Examples/Example-iOS-RAC/Component/Components/User/Edit/UserEditViewController.swift)
• Duplicated block (12 lines × 2) (Examples/Example-iOS-RAC/Example-iOS-RAC/Router/TabRouter.swift)
• Duplicated block (14 lines × 2) (Examples/Example-iOS-RAC/Component/Components/TabBarController.swift)
• Duplicated block (17 lines × 2) (Examples/Example-iOS-RAC/Catalog/Scenarios/HomeScenarios.swift)
• Duplicated block (17 lines × 2) (Examples/Example-iOS-RAC/Catalog/SceneDelegate.swift)
• Duplicated block (17 lines × 4) (Examples/Example-iOS-RAC/UseCase/Components/Home/HomeInteractor.swift)
• …and 34 more

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

KyoheiG3/Plan was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.