Course 001 · founding learner beta
Manual reviewSupport boundaryNo checkout yet

Course 001 terms, support scope and payment-readiness boundary.

This page sets the public operating boundary for D’Key Digital Presence Fundamentals while it remains a controlled founding learner beta route.

Current status.

Course 001 is currently presented as a founding learner interest route. A submitted form is a request to be considered, not payment, enrolment, access approval or certification.

Any paid route, checkout, refund wording, digital-content access rules or service package must be introduced through a later approved release. Until then, the safer operating model is manual review and manual access issue only.

Learner expectations

What approved founding learners should expect.

The course is practical, implementation-based and evidence-led. The learner remains responsible for applying the material to their own project.

Check readiness
AccessManual access issueAccess is issued only after review and approval.
LearningSelf-directed course workLessons, audio, transcripts, workbook, quizzes and audit tasks guide the process.
EvidenceImplementation proofProgress should be supported by screenshots, workbook entries and practical outputs.
CompletionCompletion boundaryCompletion is based on course evidence, not external commercial outcomes.

Support scope.

Founding learner support may include reasonable access help, route guidance, feedback review, clarification of course tasks and manual check-ins during the beta cycle.

Support does not include emergency help, legal advice, financial advice, accountancy, regulatory advice, guaranteed ranking/traffic/enquiries, done-for-you website delivery or unlimited business consulting.

Course and service separation.

Course 001 teaches a structured digital-presence method. D’Key Digital service work, such as done-for-you website building, marketing support, analytics setup, brand implementation or client delivery, must be agreed separately if offered at all.

Payment and refund readiness.

No public checkout is enabled for Course 001 in this release. Before any paid route is introduced, the Academy should publish clear pre-contract information, price, access terms, refund/cancellation wording, digital-content access position, support scope, complaint route and service separation wording.

Current position: interest only · manual review · no payment taken · no automatic enrolment · no automatic certificate · no business-result guarantee.

Safe next step for applicants.

Read the beta status, applicant readiness filter and data notice before submitting interest. Only apply if you understand that this is a manual review route and that access is not automatic.

Checkout is still disabled. Review the payment gate status before any future payment provider, buy button or paid cohort route is considered.

Learner agreement status.

Review the pre-access agreement, support scope, cancellation/refund acknowledgement and digital-content consent boundary before any paid digital access is issued.

First paid learner SOP.

Review the controlled first paid learner route before any paid access is issued manually.

D’Key Commerce account and checkout readiness.

The Academy now has a server-side learner-account, order, entitlement, receipt and reconciliation architecture. This infrastructure does not by itself make checkout public. Paid enrolment remains fail-closed until the seller identity, final price, receiving bank details and an explicit public-checkout launch switch have all been configured and the public terms have been accepted for launch.

When the bank-transfer route is enabled, a learner must sign in, submit the checkout acknowledgements and receive a signed D’Key order reference. Course access is granted only after the Academy reconciles the exact amount received against that order reference. A future card or wallet route must use a regulated payment component so raw card credentials do not enter Academy application code.

v0.3 control: commerce infrastructure ready · learner account required · public payment remains fail-closed until explicit launch activation.