capability-driven-development
A theoretical and procedural framework for designing AI-enabled software systems that prioritize human and institutional capability.
Closes the gap between abstract AI ethics/capability frameworks and practical software implementation; prevents "technology-first" design that automates tasks at the expense of human oversight and institutional governance.
Software designers, developers, learning technologists, and applied researchers.
Provides the methodology (the "HOW") that translates the AI Capability Framework (the "WHAT") into concrete system design decisions and architectural choices.
- (Conceptual) Method Steps: An 8-stage design sequence.
- (Conceptual) Design Artifacts: Templates for documenting intent, boundaries, and risk.
- (Conceptual) Patterns: Technology-agnostic implementations of responsibility (e.g., oversight, delegation).
- Define Intent: Establish human and institutional capability goals.
- Boundary Design: Specify human-AI split of duties.
- Risk/Governance Mapping: Identification of harms and design of oversight/traceability.
- Architectural Selection: Choosing implementation patterns that respect capability constraints.
- Lifecycle Management: Planning for evaluation, iteration, and retirement.
- Extensive
/methodguidelines. /foundationsfor framework alignment./design-artifactstemplates./patternslibrary for responsible implementation./examplesfor applied illustrations./ai-assisted-reflectionprompts for design teams.
- The method is described as a "living method" with individual documents potentially marked as Draft.
- N/A: This is a pure documentation and methodology repository.
Acts as the meta-framework that defines the design logic behind all other CloudPedagogy software tools (e.g., it informs the UI and data models of assessment and mapping engines).
Might overlap with theoretical research repos; distinguished by its focus on application and software systems design.
Focuses specifically on the procedural design steps needed to ensure institutional responsibility is "baked in" to software, not added as a training or policy afterthought.
(Inferred) Creation of a digital "Design Wizard" or IDE plugins that surface CDD patterns during active coding; automated audits of system architecture against CDD patterns.
While the method is procedural, the repository does not contain an executable "engine"—it relies on the user to apply the markdown-based methodology to their own development projects.