Skip to content

History / harnessed design

Revisions

  • Rewrite the wiki greenfield: current design only, no history harnessed has no users yet, so the wiki carries no compatibility debt and should describe the current design rather than how it got here. Historical framing was actively misleading: a reader could not tell a decision that still binds from one that was reversed. harnessed-design.md — rewritten (731 lines -> 211). The old spec had drifted far past patching: it described a lib/manifests/<harness>.yaml mechanism that was never built, a gemini harness that no longer exists, a harnesses: field on recipes that is now explicitly banned, a harness: field on stacks that was removed, image-baked skills where the assembler now fans them into the profile, and hatago as its own pod container where it now runs in-process. Status markers ("proposed", "to verify") were never resolved. The new document is the why: the problem, composition as the product, runtime composition, harness independence, one MCP hub, Claude-canonical format, credentials by reference, supply chain, pnpm, state, secrets, the capability oracle, and the host CLI. codebase/ — corrected nine factual errors in the regeneration: HostBackend placed in hostrun.py when both backends live in launcher.py; omp expanded as an invented name rather than oh-my-pi; a claim that no lockfile is committed when uv.lock is tracked; a claim that CI never runs podman when live.yml sets HARNESSED_PODMAN=1 post-merge and nightly; overstated coverage gaps for svcstate.py and aoe.py; a duplicated backend.py tree entry; a wrong recipe count; and a mocking convention stated without its one exception. Re-added the launcher.py size concern the regeneration dropped. Removed as pure history: done/ (six closed planning docs), guides/beads.md (a guide for a retired tracker), and recipe-build-findings.md (an authoring log). Every reference to them was repaired rather than left dangling, including two in troubleshooting.md and the index entries in Home.md and _Sidebar.md. Also unpinned the design-doc section numbers cited from troubleshooting.md — the rewrite renumbered the document, and a pinned number rots on the next edit. Reviewed the whole diff before publishing, including the regenerated files I did not author: no credentials, no personal paths, no private hostnames or internal names. Credential mentions describe the reference-never-replicate mechanism, which is already public.

    @drmikecrowe drmikecrowe committed Aug 15, 2026
  • Document permissions: auto and fix wrong default claim permissions: was documented as prompt | yolo only; auto (the third authored value, mapping to acceptEdits — the actual unset default) was missing, and prompt was wrongly labeled the default.

    @drmikecrowe drmikecrowe committed Jul 7, 2026
  • docs: refresh codebase maps, roadmap, and retire todos/ dir - regenerate codebase/*.md (ARCHITECTURE, STRUCTURE, CONVENTIONS, INTEGRATIONS, STACK, TESTING, CONCERNS) - promote todos/ROADMAP.md -> ROADMAP.md - retire docs/todos/: resolved specs -> done/, reference research -> research/, obsolete dated dumps removed (dispositions filed as bd issues) - update Home/_Sidebar, guides (recipe-authoring, recipe-catalog, system-prompt), harnessed-design, research/*, prompts/ultra-detailed-design-review Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

    @drmikecrowe drmikecrowe committed Jul 5, 2026
  • Import docs/ from the harnessed repo (2026-07-02) Mirrors the repo's docs/ tree structure (codebase/, guides/, todos/, research/, done/, prompts/) as the initial wiki content. Source repo will reference this wiki as a git submodule at docs/. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

    @drmikecrowe drmikecrowe committed Jul 2, 2026