Harness Public Entrypoints Grill Log

This log records accepted decisions for refactoring the Harness wiki public surface around available Harness Intelligence entrypoints.

Context

The prior harness-wiki-refactor grill closed the first supported-flow and skill-reference pass. This session starts a new branch set for the public IA refactor requested on 2026-06-27.

Source evidence:

• apps/wiki/content/docs/harness/meta.json currently lists foundations before lifecycle-flows.
• apps/wiki/content/docs/harness/lifecycle-flows/meta.json has routed flow pages but no overview/index page.
• apps/wiki/src/lib/layout.shared.tsx still exposes header shortcuts for /docs and /adopt.
• apps/wiki/content/docs/harness/trust-and-adoption/ is a multi-page section.
• apps/wiki/content/docs/harness/validation-and-tools/ exists, but many public pages do not point readers there when validation or tool evidence matters.

Branch: Session Scope

Q1

Question: Should the 2026-06-27 public-surface refactor start as a new grilling artifact session instead of continuing the older harness-wiki-refactor dashboard?

Accepted answer:

• Yes. Treat this as a new active grill session because the scope changed from revising supported-flow pages to refactoring the public entrypoint architecture.
• Preserve the older harness-wiki-refactor artifacts as historical context.

Branch: Entrypoint Architecture

Q2

Question: Should the public Harness wiki section currently framed as supported lifecycle flows be reframed around available entrypoints?

Accepted answer:

• Yes. The public surface should explain what Harness Intelligence can actually do.
• Keep Get Started as-is.
• Remove /docs and /adopt shortcuts from the sidebar/header surface.
• Move Foundations below the entrypoint section.
• Make Foundations carry more theory signal.
• Add an overview/index page for the entrypoint section.
• Include phase flows, hybrid flows, and important atomic skills such as parallel-research and handoff.

Q5

Question: Should the public Harness entrypoint surface preserve existing URLs and mostly change labels/content, or rename the route model to /docs/harness/entrypoints with redirects from old lifecycle-flow URLs?

Accepted answer:

• Rename the route model to /docs/harness/entrypoints.
• Carry redirects from old lifecycle-flow URLs so existing links do not break.
• The new route should encode the broader model directly instead of preserving lifecycle-flows as the public mental model.

Q7

Question: Should the entrypoint overview categorize pages as Core entrypoints, Variants, Atomic skills, and Command capabilities, or should commands stay only in Get Started/CLI docs?

Accepted answer:

• Include Command capabilities in the entrypoint overview.
• Keep command mechanics in Get Started and CLI docs.
• The overview should answer what Harness Intelligence can do completely, then link out for mechanics.

Branch: Flow Semantics

Q3

Question: How should the existing lifecycle-flow pages be renamed or reframed?

Accepted answer:

• Rename Requirements To Backlog toward brainstorming, requirements, and backlog definition.
• Treat Manual Delivery Flow as the main implementation entrypoint.
• Treat AFK Phase Delivery Flow as a variant of the implementation delivery flow.
• Retitle runtime evidence toward debugging.
• Retitle current-branch review toward review.
• Retitle ClawPatch toward massive bug hunt and fixing.
• Retitle wiki maintenance toward docs update.

Q6

Question: Should AFK delivery be a child route under the implementation entrypoint, a section inside the implementation page, or a sibling page labeled as a variant?

Accepted answer:

• Make AFK delivery a child route under the implementation entrypoint.
• Use the route-level relationship to show that AFK delivery is subordinate to the main implementation entrypoint while preserving its operational detail.
• Candidate shape: /docs/harness/entrypoints/implementation/afk.

Branch: Consolidation And Discoverability

Q4

Question: Which public sections need consolidation or stronger cross-linking?

Accepted answer:

• Merge /trust-and-adoption into a single page.
• Make /validation-and-tools more discoverable through stronger links from other pages.
• Whenever a page mentions a tool, link to its wiki page when one exists.
• Whenever a page mentions a skill, link to that skill's source page in the wearedevpunks/skills GitHub repository.

Q8

Question: What are the remaining public IA, slug, redirect, consolidation, link, foundations, and implementation decisions?

Accepted answer:

• The entrypoint overview should show Core, Atomic, and Commands.
• Do not display variants as a top-level entrypoint category.
• Preserve the detailed content for each existing phase-flow page.
• First-class atomic skill entrypoints: parallel-research and handoff.
• Command capabilities in the entrypoint overview: dp update and dp report.
• Merge all existing trust/adoption child-page content into one page; no content is intentionally dropped.
• Old trust/adoption child routes disappear rather than redirect.
• Link to all relevant validation/tool pages; choose the best target per mention.
• Skill source links use https://github.com/wearedevpunks/skills/tree/main/skills/ plus the source path.
• Add more theory signal to all four current Foundations pages.
• Top-level Harness sidebar order: Entry Points, Skills, Tools, Foundations, Prompt Surface, Exec, Trust.
• Implementation tasks should be outlined by the agent.

Derived canonical entrypoint pages:

Derived route redirects:

Derived implementation task outline:

1. Move route IA: create /docs/harness/entrypoints, move flow pages, update metadata/sidebar titles, and add lifecycle-flow redirects.
2. Rewrite entrypoint overview and page titles: Core, Atomic, Commands; preserve existing phase-flow details.
3. Merge trust/adoption: combine all child-page content into one Trust page and remove child routes.
4. Link and theory pass: add validation/tool links, skill source links, and stronger theory signal across all Foundations pages.
5. Validate: run wiki type/build checks and browser smoke for moved routes plus redirects.