> For the complete documentation index, see [llms.txt](https://docs.kc7cyber.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kc7cyber.com/camp/kc7-attribution-challenge/team-composition.md).

# Team Composition

Each team should consist of 4–5 students. Every student is assigned a role that comes with unique responsibilities:

| Role                       | Description                                                                                                                                   |
| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
| **Analyst**                | Works inside the KC7 platform to conduct technical analysis. Solves puzzles and queries logs to identify malicious activity.                  |
| **Investigator**           | Explores the physical artifacts placed around the room. Builds the theory of who did it and why. Also speaks with the Investigative Database. |
| **Case Manager**           | Maintains the team’s casebook. Coordinates submissions to the Investigative Committee. Leads the final attribution decision.                  |
| *(Optional)* **Presenter** | (If used) Helps the team organize and deliver findings during a wrap-up, if the game concludes with student presentations.                    |

Roles are enforced by game rules: students must operate **within the boundaries of their assigned roles**, reinforcing teamwork and accountability. Players cannot switch roles mid-game unless facilitators explicitly allow it (e.g., to address absences).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.kc7cyber.com/camp/kc7-attribution-challenge/team-composition.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.