Grilling
Harness Intelligence Grill Status
Harness Intelligence Grill Status
Current grill artifacts:
- Log:
apps/wiki/content/docs/project/grilling/harness-intelligence-grill-log.md - Status:
apps/wiki/content/docs/project/grilling/harness-intelligence-grill-status.md
Branch Dashboard
| Branch | Completion | Locked direction | Still open |
|---|---|---|---|
| Product Boundary | 100% | Harness Intelligence is the internal Devpunks AI engineering operating system: methodology, private wiki, CLI distribution, external tools, skill packs, scoped prompts, hooks, subagents, validation gates, telemetry, and feedback loops. Public expression is only the sanitized landing/sales narrative. | Closed. |
| Distribution Architecture | 100% | Behavior-preserving Turborepo migration; CLI is apps/cli; shared API definitions live in packages/contract; packages/scaffold only if scaffold contracts are shared; prefer Effect v4 HttpApi typed client for CLI/backend v1. | Closed; token storage and blob migration mechanics deferred to implementation planning. |
| Wiki and Theory | 100% | Private internal apps/wiki; harness domain owns the first concepts/flows inventory with Fumadocs subnavigation; docs-ingest-phase ingests only real future specs/implementation notes, not synthetic grill-derived specs. | Closed. |
| Trust and Adoption | 100% | Adoption requires trust gate bundle; telemetry tracks runtime usage; rollout uses central harness maintainers plus project owners; CLI-backed issue reporting feeds baseline/wiki/skill improvements. | Closed. |
| Backoffice and Project Mapping | 100% | Build a separate apps/backoffice first-party authenticated app backed by Postgres product telemetry; OTel remains system observability, not the primary product/adoption UI. V1 has a ProjectUsage aggregate that maps 1:n to observed repositories, because multiple repositories can belong to the same project. Automatic usage tracking only relies on CLI-observable machine/repo data. Canonical operator identity uses Better Auth bearer/device authorization; git name/email are observed metadata/fallback context. V1 stats track only happy-path value events. Developer usage is audit/contact context, not ranking/KPI. Reports link to GitHub. | Closed. |
| Phase Wrapper Model | 100% | Frozen inventory: requirements-phase, delivery-phase, review-phase, debugging-phase, docs-ingest-phase, resolve-debt-phase, and goalify. Phases are wrapper skills, not goal prompts; goalify is the prompt compiler for goal mode. delivery-phase wraps create-spec, create-plan, implement-spec, mandatory review, optional scoped debugging, and docs-ingest-phase, while preserving the parallel parameter. | Closed. |
| Company Communication | parked | Public landing exposes sanitized promise/evidence/operating model; private wiki remains source of truth; exact message hierarchy is parked for later apps/web planning. | Parked until apps/web planning. |
Parked Branches
- Exact public landing message hierarchy: parked until
apps/webplanning. - Public CTA, relationship to devpunks.com, and proof assets: parked until
apps/webplanning. - Better Auth token storage and Vercel Blob migration mechanics: deferred to implementation planning.
Current Question
Phase Wrapper Model closed. Frozen inventory: requirements-phase, delivery-phase, review-phase, debugging-phase, docs-ingest-phase, resolve-debt-phase, and goalify. Implementation order completed: docs-ingest rename, review, debugging, delivery, requirements, resolve-debt, goalify. docs-ingest-phase was directly renamed with references updated; no compatibility alias.
Glossary
Terms
- Phase: goal-facing wrapper skill that orchestrates one lifecycle slice through inner skills, artifacts, validation gates, entry conditions, and stop conditions. Avoid: loose step, task, stage.
- Inner skill: specialized skill invoked by a phase to perform part of the work while preserving its own contract.
- Goal loop: iterative goal-mode run that repeats one or more phases until the stated scope is complete or a concrete blocker is proven.
- Goalify: prompt-generation skill that turns requested scope, relevant phases, handoffs, examples, and repo context into a concrete goal-mode prompt.