vexa: Instructions file for Codex

AGENTS.md — the agent front door (in-repo)

Two constitutions govern everything here — read them on the docs site or in this tree:

• Architecture — the P-book (docs/docs/governance/architecture.mdx): what the software must be (P1–P23, enforced by the CI gate suite). Your change must fit these.
• Delivery — the D-book (docs/docs/governance/delivery.mdx): how change ships — the whole loop (roadmap · PREPARE · TAKE · validation · merge bar · ship bar) in one file.

This file is the actor contract: intake, claim, and how a session behaves in the checkout.

Researching Vexa? Start here

• Found something (bug, gap, docs lie)? File a GitHub issue — every report enters state: incoming and waits for triage — three days is our target and we are not hitting it (measured 2026-08-20: 26 waiting, median 13 days). Findings are contributions.
• Want to contribute? The whole roadmap comes back in one public GraphQL call:

gh api graphql -f query='
query { organization(login: "Vexa-ai") { projectV2(number: 2) {
  items(first: 100) { nodes {
    content {
      ... on Issue { number title url state milestone { title } labels(first: 10) { nodes { name } } }
      ... on DraftIssue { title body }
    }
    fieldValues(first: 20) { nodes {
      ... on ProjectV2ItemFieldSingleSelectValue {
        field { ... on ProjectV2SingleSelectField { name } } name }
    } }
  } }
} } }'

Four axes per item: Lane — the business value, named by who feels it (Google Meet · MS Teams · Zoom · API integrators · Transcription · Recordings · Webhooks & billing · First run · Production ops · Feature shelf) — match it to what your contributor actually uses. Human bar — what validation costs in human terms (Desk check · Operator run · Solo meeting · Small group · Crowd 5+ · In-the-loop UX). Setup — the infrastructure floor (None · Lite · Compose · k8s/helm). Milestone — the version it gates (currently v0.12.x).