Skip to content

INSTRUCTIONS.md

Latest commit

 

History

History
47 lines (38 loc) · 2.1 KB

INSTRUCTIONS.md

File metadata and controls

47 lines (38 loc) · 2.1 KB

Capability-Driven Development — User Instructions

2. What This Tool Does

Rather than a software application, this is the foundational methodology and design framework governing the entire ecosystem. It provides the structured rules, definitions, and philosophy ensuring that all CloudPedagogy tools enforce human oversight and institutional governance context.

3. Role in the Ecosystem

  • Phase: Phase 5 — Infrastructure
  • Role: The meta-methodology guiding the system’s design.
  • Reference: ../SYSTEM_OVERVIEW.md

4. When to Use This Tool

  • When preparing to build a new feature or application for the CloudPedagogy ecosystem.
  • When assessing whether a proposed AI integration aligns with institutional ethics.
  • To resolve arguments about system behavior (e.g., "should the AI automate this step?").

5. Inputs

  • Strategic input, ethical priorities, and operational requirements from governance boards.

6. How to Use (Step-by-Step)

  1. Read the core methodology documents to understand the distinction between "Capability" and "Convenience."
  2. Before designing software logic, review the CDD principles to ensure a "human-in-the-loop" constraint exists.
  3. Validate emerging UI/UX decisions against the framework's requirement for transparency and explicability.
  4. Ensure new schemas capture necessary audit metadata as dictated by the capability model.

7. Key Outputs

  • A coherent, ethically sound architectural foundation for software engineers.
  • A baseline standard for rejecting features that prioritize automation over institutional safety.

8. How It Connects to Other Tools

  • Upstream: N/A (Foundational).
  • Downstream: Dictates the behavior, UI language, and data structures of every other tool in Phases 1 through 4.

9. Limitations

  • It is a conceptual methodology, not executable code.
  • Cannot enforce itself; relies on the discipline of the engineering and design teams.

10. Tips

  • If a tool feels "too easy" and skips a human review step, it is likely violating the Capability-Driven Development framework.