Project Verifier

A Project Verifier gives verify-behavior the app-specific knowledge needed to exercise real product behavior. verify-behavior remains the single entrypoint and portable proof protocol.

Shape

Project-owned references live below .agents/skills/verify-behavior/references/:

• one index for apps and Cross-App Journeys;
• one directory per independently runnable app;
• one app reference that co-locates Launch, Doctor, Drive, Evidence, and Cleanup;
• Feature Map entries disclosed only for the selected behavior;
• optional app-owned helper scripts.

Cross-App Journeys point to app references rather than repeating launch or driver instructions.

Knowledge Authority

The Feature Map owns executable knowledge: how a user reaches behavior, how an agent drives it, which observable state proves it, and which prerequisites or gotchas apply. Wiki specifications, behavior pages, flows, and domain knowledge remain authoritative for product meaning. Creation uses those sources to seed the map and reconciles them with current code and runtime entry points.

Shared Skill Adaptation

Harness adapts pstack's create-verification-skill and maintain-verification-skill procedures. The repository interview, live proof, evidence, cleanup, Feature Map, source reconciliation, and product-regression triage remain intact. Necessary Harness changes are limited to:

• writing app references below the existing verify-behavior skill instead of creating verify-<app> skills;
• naming the maintenance capability update-verification-skill;
• letting implement-spec invoke the creator for an Uncovered Surface and the updater for Uncovered Behavior;
• joining updates to the current delivery instead of requiring a separate maintenance pull request.

Ownership

Harness owns the verify-behavior protocol. The project owns its app references, Feature Maps, journeys, and helpers. Scaffold and update post-command flows leave that project-owned content unchanged.

During implement-spec, an Uncovered Surface invokes create-verification-skill; Uncovered Behavior invokes update-verification-skill. Both branches prove the new executable path before the original scenario resumes. docs-ingest-phase may update ordinary wiki knowledge, but it never invokes the updater or writes Feature Maps.

See Project Verification Flow for lifecycle routing.