-
Notifications
You must be signed in to change notification settings - Fork 52
All issues
Issue creation is restricted in this repository
Issues
is:issue state:open
is:issue state:open
Search results
Define armory-core integration strategy on top of RIMS
architectureArchitecture and system design decisionsArchitecture and system design decisionsintegrationIntegration strategy between systems or modulesIntegration strategy between systems or modulesplanningPlanning, scoping, and roadmap workPlanning, scoping, and roadmap workStatus: Open.#187 In DamageLabs/rims;Validate RIMS core design against Cellar Sync use cases
architectureArchitecture and system design decisionsArchitecture and system design decisionsplanningPlanning, scoping, and roadmap workPlanning, scoping, and roadmap workvalidationValidation of assumptions or architecture against use casesValidation of assumptions or architecture against use casesStatus: Open.#186 In DamageLabs/rims;Define generic reporting and export primitives for RIMS
architectureArchitecture and system design decisionsArchitecture and system design decisionsreportingReporting and export capabilitiesReporting and export capabilitiesStatus: Open.#185 In DamageLabs/rims;Remove electronics-specific assumptions from RIMS core
architectureArchitecture and system design decisionsArchitecture and system design decisionscleanupCleanup, neutralization, or simplification workCleanup, neutralization, or simplification workrefactorStructural code changes without new product behaviorStructural code changes without new product behaviorStatus: Open.#184 In DamageLabs/rims;Plan RIMS migration to Angular 21, Express 5, TypeScript, SQLite, and Drizzle
architectureArchitecture and system design decisionsArchitecture and system design decisionsmigrationMigration or replatforming workMigration or replatforming workplanningPlanning, scoping, and roadmap workPlanning, scoping, and roadmap workStatus: Open.#183 In DamageLabs/rims;Design schema-driven field and form system for RIMS
architectureArchitecture and system design decisionsArchitecture and system design decisionsformsSchema-driven forms and field systemsSchema-driven forms and field systemsStatus: Open.#182 In DamageLabs/rims;Define domain module boundaries for RIMS core vs domain-specific logic
architectureArchitecture and system design decisionsArchitecture and system design decisionsdesignDesign decisions and boundary definitionDesign decisions and boundary definitionplanningPlanning, scoping, and roadmap workPlanning, scoping, and roadmap workStatus: Open.#181 In DamageLabs/rims;Design the neutral RIMS core data model
architectureArchitecture and system design decisionsArchitecture and system design decisionsdata-modelSchema and data model designSchema and data model designplanningPlanning, scoping, and roadmap workPlanning, scoping, and roadmap workStatus: Open.#180 In DamageLabs/rims;Audit current RIMS features into keep, generalize, or remove
architectureArchitecture and system design decisionsArchitecture and system design decisionsauditAudits, classification, and review tasksAudits, classification, and review tasksplanningPlanning, scoping, and roadmap workPlanning, scoping, and roadmap workStatus: Open.#179 In DamageLabs/rims;Re-scope RIMS as a generic inventory and collection framework
architectureArchitecture and system design decisionsArchitecture and system design decisionsplanningPlanning, scoping, and roadmap workPlanning, scoping, and roadmap workStatus: Open.#178 In DamageLabs/rims;- Status: Open.#173 In DamageLabs/rims;
- Status: Open.#158 In DamageLabs/rims;