Positioning FAQ

This draft keeps the public story tight: .knowledge by Pro2Pilot is the free repo-local trust and routing layer, and Pro2Pilot Inspector is the paid visual workflow layer around it.

What is .knowledge by Pro2Pilot?

It is a free, Apache-2.0, repo-local agent-readiness layer. It gives Codex, Claude Code, OpenCode, and custom agents a shared first-read routing bundle, trust status, freshness checks, local search, wiki graph, doctor reports, metrics, PR summaries, and a baseline Visual Inspector.

Is .knowledge a hosted product?

No. The core is local-first and repo-native. Source code and tests remain the source of truth. The knowledge files help an agent route, verify, and avoid starting cold every session.

What problem does it solve?

AI coding agents often start by rediscovering the same repository structure, reading stale summaries, or opening the wrong files. .knowledge makes the first orientation step explicit: what to read first, what is trusted, what is suspect, and where repair work is waiting.

What should we avoid claiming?

Do not claim that .knowledge guarantees better agent behavior or that token savings are production benchmarks. The current proof point is an orientation layer estimate: a synthetic SaaS-shape fixture reduced first-orientation context from 14 files to 1 routing bundle and about 22% fewer estimated tokens.

What is Pro2Pilot Inspector?

Inspector is the optional paid workflow layer. It turns raw .knowledge state into a visual operating surface: trust graph filters, repair queue boards, critical-path explorer, PR impact view, policy packs, and team dashboards.

Who is the first audience?

Teams already using AI coding agents in real repositories. The best fit is a solo builder, agency, engineering team, or enterprise group that needs agent work to become reviewable across trust, freshness, evidence, and PR impact.

What language should public pages use?

Use phrases like “repo-local agent readiness”, “local trust and routing layer”, “Visual Inspector”, “repair queue”, “trust graph”, “critical-path explorer”, “PR impact view”, “policy packs”, and “team dashboards”.

What language should public pages avoid?

Avoid “orchestrator”, “agent orchestration platform”, “future Pro2Pilot platform”, and any claim that the open core is paid. Keep the commercial split clear: the local standard is open, while the visual workflow layer is paid.