Capability Domains
Organise capability into coherent areas of practice.
Capability Architecture gives an Academy a structured language for capabilities, skills, proficiency, evidence, relationships and development — so learning and experience can be connected to what people can actually do.
A course can describe content. A capability architecture describes the ability the Academy is trying to develop, observe and evidence.
Organise capability into coherent areas of practice.
Define the abilities and constituent skills that matter.
Represent prerequisite, adjacent, transferable, complementary and role-specific relationships.
Describe what capability looks like at meaningful stages without reducing it to a universal score.
Define what evidence can support a capability claim.
Account for recency, context and continued relevance.
Capability evidence should not be trapped inside one learning activity.
Assessments, demonstrations, knowledge application and learning artefacts.
Projects, capstones, simulations, portfolios and supervised experiences.
Work records, host feedback, project outcomes and professional contribution.
Assessment decisions and verified achievement records.
Recognised evidence from outside the Academy where provenance can be established.
Learner interpretation that remains distinguishable from verified fact.
The architecture should distinguish a capability definition, a learner claim, an evidence item, an assessment decision and a credential. They are related, but they are not interchangeable.