> ## Documentation Index
> Fetch the complete documentation index at: https://cxity.kairaxis.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Day 0 Project Flow: First-Time Contexity Onboarding

> Attach Contexity to a project for the first time. Day 0 seeds candidate context from README, commits, and structure — without auto-trusting anything.

"Day 0" is the first time Contexity sees a project. The goal is to seed useful candidate context quickly — giving the agent something to work with from the start — without pretending the system already knows everything. Contexity is honest about what it has verified and what is still a candidate.

## Run the Day 0 Flow

Point Contexity at your project and describe the first task you want help with:

```bash theme={null}
contexity --project /path/to/project day0 --task "understand this project"
```

Day 0 runs a sequence of initialization steps automatically:

* **Initialize project identity** — creates a stable project ID and baseline metadata in `.cxcap/`
* **Attach local state** — reads the current working tree, branch, and recent history
* **Run fast project analysis** — scans structure, entry points, package manifests, and top-level docs
* **Seed safe candidate context** — stores orientation-level signals, labeled as candidates
* **Prepare a first task-aware pack** — assembles an initial context pack scoped to the task you provided
* **Optionally preview host installs** — if no host is configured, surfaces the install prompt for Codex, Claude Code, or another supported host

## What Gets Trusted

Most Day 0 discoveries are **candidates**, not verified facts. Contexity seeds them as useful orientation material, but it does not treat them as confirmed ground truth until evidence revalidates them.

Common candidate sources from Day 0 include:

* README summaries
* Package manager hints (`package.json`, `Cargo.toml`, `pyproject.toml`, and similar)
* Recent commit context
* Top-level docs and configuration files

These give the agent a useful starting picture of the project without overstating confidence in what has actually been validated.

<Note>
  Candidates are labeled in context packs and suppressed from verified-only retrieval until you confirm them. If a candidate conflicts with something verified later, the verified signal takes precedence.
</Note>

## When to Re-Run

Re-run Day 0 — or at minimum a fresh fast analysis — whenever the project's structure or configuration has changed significantly enough that the seeded context may be stale:

* The project was heavily refactored or reorganized
* `.cxcap/` was restored from a backup or transferred from another machine
* The host config changed and you need to re-align project intelligence
* Contexity itself reports stale project intelligence during a run

To run a fast analysis without the full Day 0 initialization sequence:

```bash theme={null}
contexity --project /path/to/project analyze --depth fast
```

This refreshes structure signals and candidate context without resetting project identity or host config.