# Page Not Found

The URL `project-portal/learn-about-project-training/commitment-vs.-job-function-vs.-people-on-teams` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Commitment vs. Job Function vs. People on Teams](https://guide.techfleet.org/team-portal/new-teammate-handbook/expectations-for-teammates/commitment-vs.-job-function-vs.-people-on-teams.md)
- [Project Components](https://guide.techfleet.org/project-portal/project-success-handbook/project-components.md)
- [Keys to Project Success](https://guide.techfleet.org/project-portal/project-success-handbook/keys-to-project-success.md)
- [Completing Vision and Scope Milestones](https://guide.techfleet.org/project-portal/project-success-handbook/keys-to-project-success/completing-vision-and-scope-milestones.md)
- [Supported Team Functions in Project Training](https://guide.techfleet.org/team-portal/new-teammate-handbook/project-training-teams/supported-team-functions-in-project-training.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://guide.techfleet.org/team-portal/new-teammate-handbook/expectations-for-teammates/commitment-vs.-job-function-vs.-people-on-teams.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

### Option 2 — Browse the documentation index

Full index: https://guide.techfleet.org/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://guide.techfleet.org/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/team-portal/new-teammate-handbook/expectations-for-teammates/commitment-vs.-job-function-vs.-people-on-teams.md`).

You may also use `Accept: text/markdown` header for content negotiation.