05 / ACADEMY ARCHITECTURE

Configure how capability is developed through doing.

Experience Architecture defines how BUILD experiences are selected, structured, supervised, evidenced and connected to capability — moving beyond consumption into practice and demonstration.

PracticeContributionSupervisionEvidenceReflection
Academy principle
Experience is part of the curriculum.

BUILD should not be an unstructured add-on. The Academy configures the experiences through which capability becomes observable and evidence can be generated.

Experience architecture

01

Experience Types

Configure projects, capstones, simulations, fellowships, residencies, internships and other appropriate experiences.

02

Experience Intent

Define which capability the experience is meant to develop or demonstrate.

03

Contribution

Clarify what the learner is expected to do, not merely attend.

04

Supervision

Define mentors, reviewers, sponsors and escalation paths.

05

Evidence

Capture work, feedback, reflection and outcomes with provenance.

06

Transition

Determine when experience evidence can support opportunity or credential pathways.

Experience lifecycle

SelectExperience
PrepareReadiness
EngagePractice
ContributeWork
ReviewFeedback
EvidenceProof
ReflectProgress

Experience design principles

01

Authenticity

The experience should reflect a meaningful practice context.

02

Agency

The learner has a defined role and contribution.

03

Supervision

Appropriate guidance and review are available.

04

Safety & Integrity

Confidentiality, privacy, IP and conduct are explicit.

05

Evidence

Contribution and outcomes are distinguishable from claims.

06

Reflection

Experience informs future capability direction.

BUILD connection

Experience Architecture is the design layer behind the BUILD ecosystem. It should make it possible to connect guided capstones, simulated industry projects, fellowships, hackathons, apprenticeships, residencies, internships and portfolio evidence without turning them into disconnected products.