KyoheiG3/Plan
68.7
Adequate · 9 November 2026
3.9k
lines of production code
Swift
primary language
7
measurements over time
What this system is
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.
Features
Add iOS RAC example app with UI catalog and snapshot 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
Added Plan example project with clean architecture structure
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
Added Xcode project and test scheme for the Plan framework
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
Added fastlane configuration for iOS testing
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
Introduce Plan architecture for state management and dispatching
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
Behavioural changes
Default Swift and deployment target settings for new Plan project
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
Test coverage
Initial test suite for the Plan architecture
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
Dependencies
Added Swift Package Manager and CocoaPods support for the Plan library
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 cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
How this codebase got here
Score
- CAI 68 → 69 (+0.4)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.
Lenses
- Code Health 96 → 96 (+0.0)
- Architecture 98 → 98 (-0.1)
- Maturity 62 → 63 (+1.6)
- Readiness 56 → 56 (+0.0)
- Security 90 → 90 (+0.0)
- Domain Modelling 100 → 100 (+0.0)
Resolved (2)
- Inconsistent abstraction for transformation. AnyDispatcher uses a functional 'map' to transform actions, while Presenter relies on a constructor-injected 'translator' object. Both concepts involve transforming data/actions, but the API surface exposes two different patterns (functional composition vs. dependency injection) for similar intent.
- Redundant 'asDispatcher' method on AnyDispatcher. Since AnyDispatcher is already the target type, calling asDispatcher() on it is a no-op identity operation that adds noise. It suggests a pattern where types convert to a dispatcher, but the base type shouldn't need to convert to itself.
Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
Survey your own repository
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.
About this page
- The score is its most recent published measurement, taken on 9 November 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit 49f53128eac924d9723b31ee4b0240d62bd0e12d — the exact code this score is about.
- Scored under rubric-2026.11.2 — the same rubric and the same method as every other entry in this index.
- Measured by Canine Code Analyzer (cca.canine.dev) using cca measure-2026.11.3+preprod-bb0cb800cd0f.