7.1.2. Ownership and Limitations of Outputs
💡 First Principle: Under GitHub's terms, you own the suggestions you accept and the code you build with Copilot — but ownership doesn't erase the limitations: output may resemble public code, may be imperfect, and you remain responsible for verifying and for any IP considerations.
Key facts the exam expects:
- You own the output — GitHub's terms assign ownership of Copilot's suggestions to you, the user; Copilot is a tool, and what you produce with it is yours.
- Limitations remain — because output is generated probabilistically, it can be incorrect, insecure, or (rarely) resemble existing public code. Ownership doesn't mean correctness or freedom from all IP concerns.
- IP indemnity — on Business and Enterprise plans, GitHub offers IP indemnity for suggestions, contingent on having the duplication-detection (public-code matching) filter enabled. That's a concrete tie between a safeguard and a protection.
- Responsibility stays with you — consistent with Phase 3, accountability for what's committed and shipped remains the developer's and organization's.
💡 Key Point: Ownership and responsibility travel together. You own the output, which is exactly why you're responsible for validating it.
⚠️ Exam Trap: "Because Copilot generated it, there are no IP or quality concerns" is wrong. Ownership doesn't equal guaranteed originality or correctness; the public-code filter and review exist precisely because resemblance and errors are possible. And IP indemnity on Business/Enterprise depends on enabling the matching filter.
Reflection Question: If you own Copilot's output, why are you also responsible for it, and what condition must a Business/Enterprise customer meet to receive IP indemnity?
