Plan: IP-107 Colleague Trust Gate Bundle

Initial Situation

IP-107 is blocked by IP-104. Once lifecycle codification is durable, trust-gate docs can turn that lifecycle into colleague-facing adoption proof. Current wiki has methodology foundations but not a trust gate bundle.

Solution Shape

Create a private trust-and-adoption wiki section, supporting runbook references, and a golden walkthrough artifact. Keep public narrative out of scope.

Tasks

T107-1: Create trust-and-adoption IA and onboarding path

• depends_on: [T104-4]
• location: apps/wiki/content/docs/harness, apps/wiki/content/docs/harness
• description: Add source/routed onboarding and trust-boundary pages; update harness meta/index.
• validation: Routed navigation includes trust-and-adoption section and onboarding route renders.
• status: Planned
• log:
• files edited/created:
• backlog_item_id: IP-135
• backlog_item_url: https://linear.app/devpunks/issue/IP-135/internal-onboarding-path-explains-what-to-trust-and-what-not-to-trust
• relation_mode: native
• assigned_skills: [docs-ingest-phase, parallel-research, simplify, agent-browser]
• tdd_target: A colleague can follow one route to learn purpose, misuse boundaries, and human judgment boundaries.
• review_mode: browser

T107-2: Add validation story, failure model, and criteria checklist

• depends_on: [T107-1]
• location: apps/wiki/content/docs/harness/concepts, apps/wiki/content/docs/harness/trust-and-adoption
• description: Create trust proof pages that separate automatic checks, human review, judgment, known failure modes, and adoption-ready criteria.
• validation: Checklist maps automatic/human/judgment categories and all listed failure modes.
• status: Planned
• log:
• files edited/created:
• backlog_item_id: IP-135
• backlog_item_url: https://linear.app/devpunks/issue/IP-135/internal-onboarding-path-explains-what-to-trust-and-what-not-to-trust
• relation_mode: native
• assigned_skills: [docs-ingest-phase, simplify, quality-types]
• tdd_target: The validation story explicitly says what checks prove and what they do not prove.
• review_mode: cli

T107-3: Produce golden repo walkthrough

• depends_on: [T107-2]
• location: docs/, apps/wiki/content/docs/harness/flows, apps/wiki/content/docs/harness/trust-and-adoption
• description: Add a realistic adoption walkthrough with setup/update evidence, generated-file categories, expected agent behavior, validation gates, and failure handling.
• validation: Walkthrough includes before/after scaffold evidence and links to CLI mechanics runbook without client-specific material.
• status: Planned
• log:
• files edited/created:
• backlog_item_id: IP-136
• backlog_item_url: https://linear.app/devpunks/issue/IP-136/golden-repo-walkthrough-demonstrates-harness-adoption
• relation_mode: native
• assigned_skills: [docs-ingest-phase, agent-browser, simplify, tdd]
• tdd_target: The walkthrough can be checked against a generated fixture or approved repo transcript and explains failure handling.
• review_mode: mixed

T107-4: Add support and feedback loop bundle

• depends_on: [T107-3]
• location: apps/wiki/content/docs/harness/flows, docs/runbooks, docs/README.md
• description: Connect report submission, GitHub follow-up, Linear planning boundary, and accepted fix flow into skill/wiki/baseline updates.
• validation: Support loop page links report command/guidance and distinguishes GitHub follow-up from Linear backlog.
• status: Planned
• log:
• files edited/created:
• backlog_item_id: IP-107
• backlog_item_url: https://linear.app/devpunks/issue/IP-107/create-the-colleague-trust-gate-bundle
• relation_mode: native
• assigned_skills: [docs-ingest-phase, simplify]
• tdd_target: A colleague can identify how to report friction and how maintainers turn it into durable harness changes.
• review_mode: cli

T107-5: Browser validate and close out trust gate

• depends_on: [T107-4]
• location: apps/wiki/specs/cli/IP-107-colleague-trust-gate, wiki routes
• description: Update implementation notes, issue matrix, docs ingest log, review, browser validation, and tracker evidence.
• validation: jq empty for changed meta; bun run check; bun run check-types; wiki browser smoke for trust routes.
• status: Planned
• log:
• files edited/created:
• backlog_item_id: IP-107
• backlog_item_url: https://linear.app/devpunks/issue/IP-107/create-the-colleague-trust-gate-bundle
• relation_mode: native
• assigned_skills: [review-phase, agent-browser, turborepo, simplify]
• tdd_target: IP-135/IP-136 acceptance table maps to route/browser/docs evidence.
• review_mode: browser

Dependency Graph

T104-4 -> T107-1 -> T107-2 -> T107-3 -> T107-4 -> T107-5

Validation Gates

• Gate 1: Onboarding/trust boundary exists.
• Gate 2: Validation/failure/checklist proof exists.
• Gate 3: Golden walkthrough exists.
• Gate 4: Support loop exists.
• Gate 5: Routes render and docs metadata validates.

Risks

• Walkthrough becomes client-specific. Mitigation: use representative fixture or sanitized generated evidence.
• Wording overclaims reliability. Mitigation: checklist and failure model center proof, limits, and support loops.

Unresolved Questions

• Golden repo source is open; default implementation should use a generated representative fixture if no approved real repo exists.