C886 Advanced Calculus, catalog number MATH 5104, is the two-CU proof course in the WGU School of Education that reconsiders calculus rigorously: real-number systems, sequences, limits, continuity, differentiation and integration, all established by proof rather than by procedure. It is a legacy code paired with the current D894, so students land here from older programme versions. The subject matter looks familiar and is not, because for the first time the question is not how to compute a limit but how to prove that the limit is what you say it is.
The same calculus, a different obligation
Every topic in MATH 5104 has a name you already know. That familiarity is the trap. In a first calculus course, continuity is described as drawing without lifting the pencil, and a limit is described as what the function approaches. In advanced calculus both descriptions are retired and replaced with statements involving quantifiers, where continuity at a point means that for every positive tolerance there exists a positive distance such that a specific inequality holds. The mathematics did not change. What changed is that intuition is no longer accepted as an argument.
The genuine difficulty is almost never the calculus. It is quantifier order and the logic of proof. Students who have never written a formal proof find that their instincts, which have served them well for years, produce sentences that are true and unusable. Knowing that a sequence converges is not the same as producing, for an arbitrary tolerance, an index beyond which every term is within it. The second is what the course wants, and it has to be practised rather than understood.
For a future teacher there is a further reason this course exists. Rigour is where mathematics keeps its integrity, and a teacher who has proved the intermediate value theorem rather than merely used it explains it differently. Reviewers in a School of Education programme are watching for that shift, which is why proof-writing style and clarity are usually scored alongside correctness.
Planning from the scoring detail
The scoring detail for your course sits inside your Course of Study, not in the public catalog. Open it first, because a School of Education mathematics course may use a submitted performance assessment, a proctored objective assessment, or both, and proof work and timed work reward very different preparation.
Under a performance assessment, each scored aspect is judged independently on a three-point scale, and a 2 in every aspect passes the task. Nothing averages. In a proof course this usually means each proof, or each part of a proof, is its own aspect, so an elegant argument for one theorem cannot cover a circular one for another.
The word budget, worked. Proof writing is prose, so the budget is genuinely about words. With five scored aspects and directions asking for around 1,600 words, reserve 100 for framing and 100 for a close, leaving 1,400, about 280 words per proof. That is enough for a statement of what is given and what is to be shown, the construction step where you produce the delta or the index, the inequality chain, and a closing sentence tying the chain back to the definition. Proofs that come back are rarely too long. They are usually 90 words, missing the construction, and effectively saying that the result is obvious.
Budget rewriting time as well as writing time. A first-draft proof that is correct is common; a first-draft proof that is also readable is rare, and readability is scored.
A structure that fits a proof
Where task directions specify a format, follow them. Where they do not, this arrangement is what a reviewer of proof work expects to find and in this order.
| Section | What belongs in it | How it gets scored |
|---|---|---|
| Statement | The claim written out in full, with all hypotheses, before any argument begins | An unstated hypothesis used later is the classic hidden flaw reviewers hunt for |
| Definitions invoked | The formal definitions the proof will use, quoted precisely as your course states them | Scored where rigour is named; informal definitions void the argument |
| Strategy | One sentence naming the approach: direct, contrapositive, contradiction, induction, epsilon construction | Not always scored alone, but it makes the rest readable and it exposes circularity early |
| Construction | The explicit choice of delta, index or partition, and where it came from | The heart of most analysis proofs and the step most often skipped |
| Argument | The inequality chain or logical sequence, each step justified by a named result | Scored on validity and on whether each step is supported rather than asserted |
| Conclusion | An explicit statement that the definition is now satisfied, matching the original claim | Scored for closing the loop; a proof that stops mid-chain is incomplete |
Scratch work belongs in scratch, not in the submitted proof. Analysis proofs are usually discovered backwards, by working out what delta must be, and then written forwards. Submitting the discovery instead of the exposition is a common reason competent mathematics reads as muddled.
What rigour looks like on the page
In a proof course the evidence is the argument itself, and reviewers read for specific failure modes rather than for style.
- Justify each step by naming the theorem, definition or algebraic property that licenses it. A step with no license is a gap even when it is true.
- Watch quantifier order relentlessly. For every epsilon there exists a delta is a different statement from there exists a delta for every epsilon, and only one of them is continuity.
- Never use the conclusion in the argument. Circularity is the most common serious flaw and it hides easily inside familiar material.
- Say where each hypothesis is used. A proof that never uses a stated hypothesis is either wrong or proving a stronger theorem, and both deserve comment.
- Keep notation fixed. Reusing a symbol for two purposes inside one proof is enough to make a valid argument unreadable.
- Cite outside sources properly in APA where the task involves any, and write proofs in your own words, since WGU runs submissions through a similarity check and standard proofs are widely reproduced.
The habit that marks strong analysis writing is stating the sharpness of a result. Noting that the converse fails, and giving the counterexample in a single line, shows that you know the boundary of what you have just proved.
What separates Competent from a return
WGU records Competent or Not Competent rather than letter grades, and produces no ordinary grade point average. Each aspect is scored on its own, so proof work usually returns for one identifiable flaw rather than for general weakness.
- Every claim is stated in full before it is argued.
- Every definition used is the formal one, written as your course writes it.
- Every construction is explicit, with the delta or index produced rather than promised.
- Every step names its justification.
- Every proof ends by explicitly satisfying the definition it set out to satisfy.
Because performance assessment work can be revised and resubmitted without a grade penalty, a returned proof is a rewriting exercise rather than a failure, and rewriting proofs is how people learn to write them. The cost is the six-month flat-rate term, where closing more courses is the only lever on effective cost per course.
Where a proctored objective assessment applies, our limit is firm. Proctored assessments are yours to sit. We prepare with proof technique drills, worked model arguments and an honest readiness call, and we never ask for portal credentials.
Six mistakes that cost time in C886
- Arguing from intuition. The whole point of MATH 5104 is that the intuitive account is being replaced by a formal one, so appeals to the picture score nothing.
- Submitting the scratch work. Find delta backwards, then write the proof forwards. Reviewers score the exposition.
- Getting quantifier order wrong. It is the most frequent technical flaw in analysis proofs and it silently changes what you proved.
- Proving the converse by accident. Restate the claim before you argue and check at the end that you satisfied that claim and not its mirror.
- Skipping the counterexample. Where a rubric asks whether a converse holds, a one-line counterexample is the complete answer and a paragraph of discussion is not.
- Underestimating a two-CU proof course. Unit count reflects credit weight, not the hours it takes to learn to write proofs, and this is the course where that gap is widest.
How support works on this course
Send your Course of Study for C886 with the rubric and the task directions. What comes back is a proof-by-proof review that names the actual flaw rather than telling you to be more rigorous, model arguments in the same style for the theorems you are stuck on, and an aspect-mapped draft where the construction step is explicit and every justification is named.
Because C886 is a legacy code paired with the current D894, the material also transfers cleanly if your programme version moves. Learning to write a proof properly once is the last time you need to learn it.
Questions students ask about C886
Is C886 the same course as MATH 5104?
Do I need to have written proofs before C886?
Can you sit a proctored assessment for me?
Correct mathematics, proofs still coming back?
Send your Course of Study and rubric. You get a proof-by-proof review that names the real flaw, model arguments in the same style, and aspect-mapped drafting with explicit constructions.
Where C886 sits in WGU's programs
The July 2026 catalog places this code in 1 current WGU program. Open a program page for the complete standard path and term positions. The live Degree Plan remains authoritative after transfer credit, substitutions, and mentor planning.
The assessments, one by one
The public catalog does not publish this course's PA/OA identity or task count. WGU Tutors publishes at most one PA manual per course and only from a WGU-controlled public rubric. Until that source exists, PA help begins from the student's real Course of Study and OA support remains preparation only.