How charnyanton/rulesengine works
Project type and purpose
• This is an actor-based, rule-evaluation Swift library (not a full-stack app).
• Its purpose is to provide a generic, priority-based decision-making engine that evaluates a set of independent rules against a mutable context.
File structure
• Top-level files:
• Package.swift – Swift Package Manager manifest
• README.md, LICENSE, .gitignore
• Sources/RulesEngine
• Core types: AnyRule.swift, EvaluationResult.swift
• Protocols: ApplicationContextProtocol, RuleProtocol, RulesEngineProtocol
• Implementation: RulesEngine.swift
• Tests/RulesEngineTests
Key points from README
• Engine accepts:
• A list of main rules (type-erased to AnyRule)
• A list of override rules
• A fallback EvaluationResult
• A default context
• It sorts rules by priority, applies them against the context, handles overrides, returns a final decision.
Main components
a. Protocol layer
• ApplicationContextProtocol
• RuleProtocol<Context,Outcome>
• RulesEngineProtocol
b. Core data structures
• AnyRule (type erasure wrapper)
• EvaluationResult (decision + reason)
c. Engine implementation
• RulesEngine (actor)
d. Client code (example)
• Concrete Context (e.g., MyContext)
• Concrete Rules (e.g., AdminRule)
e. External boundaries
• Consumer application calling engine.makeOutcome()
Relationships and data flow
• Consumer → initializes RulesEngine with:
– [AnyRule<ConcreteRule>] (main rules)
– [AnyRule<OverrideRule>]
– fallback EvaluationResult
– default Context
• RulesEngine actor
↓ (await)
• sorts rules by priority
• for each rule: rule.evaluate(context) → optional Outcome
• applies override logic
• if no rule matches, uses fallback
↓
returns EvaluationResult to consumer
Architectural patterns & principles
• Protocol-oriented design (Protocols folder)
• Type erasure (AnyRule) to store heterogeneous RuleProtocol implementations
• Actor isolation for thread safety
• Priority queue pattern for rule ordering
• Context-driven mutable state passed to rules
Detailed component breakdown
• ApplicationContextProtocol
• RuleProtocol (generic interface)
• AnyRule (type erasure)
• RulesEngineProtocol (engine interface)
• RulesEngine (actor implementation)
• EvaluationResult (decision + reason)
• Concrete rule implementations (e.g., AdminRule)
• Consumer context (e.g., MyContext)
Putting it all together
• Inside RulesEngine: