CareerVector Repository Operating Contract

The repository is a monorepo for CareerVector, the JobCache peer product, shared libraries, the architecture/Wiki knowledge system, and delivery tools. The top-level map in AGENTS.md is canonical; the nearest directory AGENTS.md adds local constraints.

Authority

• architecture/ owns whole-system geometry, boundaries, and contract intent.
• Markdown owns human meaning and decisions; graph frontmatter connects it to the nine semantic hubs.
• Schemas and typed source own wire and state contracts.
• Tests, probes, receipts, and runtime observations own evidence.
• Generated Wiki pages, JSON projections, diagrams, and presentations are not separate authorities.

Operating rules

1. CareerVector remains no-account and link-access. JobCache identity does not cross that boundary.
2. Browser, TUI, Tauri, REST, MCP, and chat tools do not create parallel state paths.
3. Production credentials, workspace links, and personal data stay outside Git and external CI.
4. Local product work uses Miniflare and synthetic state. Deployed-worker tests are explicit, bounded operator actions because Cloudflare's request quota is account-wide.
5. User-visible changes require real-browser or real-terminal evidence.
6. Dependency, workflow, deployment, architecture, and security changes require owner review.
7. Commits contain no AI attribution trailers.

CI and review

Crow is the self-hosted repository-wide gate and may access the private Sporewright checkout. GitHub Actions is limited to source-read, secret-free portable lanes and pins every action to a full commit SHA. CircleCI remains a dispatch-only test orchestrator; production credentials must not be added to its project or context environment.

The current private GitHub plan cannot enforce branch protection or rulesets. CODEOWNERS therefore routes review but cannot make it mandatory. Until the hosting plan or canonical forge changes, maintainers must grant write access sparingly and require pull-request review procedurally for onboarded developers.

Infrastructure and deploys

Active infrastructure code lives in the separate infrastructure repository; the infra/ directory here is a tombstone. This repository declares Worker, service, and database bindings, but production secrets remain encrypted operator material or vendor-side secret bindings.

Cloudflare deploys use version upload followed by an explicit 100% promotion. The repository wrapper accepts only a scoped Workers token and account ID; it does not expose the Cloudflare global key or distribute deploy authority to contributors.

Continue with Development and security.