[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-11409":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":9,"language":10,"languages":9,"totalLinesOfCode":9,"stars":11,"forks":12,"watchers":13,"openIssues":14,"contributorsCount":14,"subscribersCount":14,"size":14,"stars1d":14,"stars7d":14,"stars30d":15,"stars90d":14,"forks30d":14,"starsTrendScore":14,"compositeScore":16,"rankGlobal":9,"rankLanguage":9,"license":9,"archived":17,"fork":17,"defaultBranch":18,"hasWiki":17,"hasPages":17,"topics":19,"createdAt":9,"pushedAt":9,"updatedAt":20,"readmeContent":21,"aiSummary":22,"trendingCount":14,"starSnapshotCount":14,"syncStatus":23,"lastSyncTime":24,"discoverSource":25},11409,"harness-experimental","hoangnb24\u002Fharness-experimental","hoangnb24","Turn any repo into an agent-ready workspace for Claude Code, Codex, Cursor, and other coding agents.",null,"Rust",479,236,6,0,299,7.12,false,"main",[],"2026-06-12 02:02:31","# harness-experimental\n\nHarness v0 for agent-driven software development.\n\nThis is not an app template. It is a repository-level operating harness for\nturning human intent or a product spec into agent-ready work: product\ncontracts, story packets, validation expectations, architecture decisions, and\neventually implementation.\n\nThe app is what users touch. The harness is what agents touch.\n\n## Why This Exists\n\nCoding agents are becoming useful enough to participate in real software work,\nbut the model alone is not the whole system. A repository also needs clear\ninstructions, shared product truth, validation loops, internal tools, and\ndecision records so an agent can understand what matters before it changes\ncode.\n\nHarness Engineering is the practice of designing that operating environment.\nThe goal is not simply to make AI write code faster. The goal is to make\nAI-assisted software development more reliable, inspectable, and easier for\nhumans to steer.\n\nOpenAI describes this shift as an agent-first world where humans steer and\nagents execute:\n\nhttps:\u002F\u002Fopenai.com\u002Findex\u002Fharness-engineering\u002F\n\n## Current State\n\nThis repository is in Harness v0.\n\nThere is no application implementation and no baked-in product specification\nyet. The current work is the reusable project harness: the file structure,\nagent operating model, feature intake process, story templates, and validation\nexpectations that help humans and agents turn a future user-provided spec into\nimplementation work.\n\n## What Counts As A Harness\n\nA repository starts to have a harness when it helps an agent answer practical\nengineering questions without relying only on chat history:\n\n- What should I read first?\n- What type of work is this?\n- Which product contract does it affect?\n- How risky is the change?\n- What proof will show the work is done?\n- What decision or lesson should future agents inherit?\n\nIn this repo, those answers live in `AGENTS.md`, `docs\u002FHARNESS.md`,\n`docs\u002FFEATURE_INTAKE.md`, `docs\u002FARCHITECTURE.md`, `docs\u002FTEST_MATRIX.md`,\n`docs\u002Fstories\u002F`, `docs\u002Fdecisions\u002F`, and `docs\u002Ftemplates\u002F`.\n\n## Try The Flow\n\nThe fastest way to understand the harness is to inspect a tiny example:\n\n- `docs\u002Fdemo\u002FREADME.md`: shows how a simple product idea becomes product docs,\n  stories, validation expectations, and decisions before implementation starts.\n\n## Product Sources\n\nNo product contract is currently defined.\n\nWhen a user provides a project specification, add or reference it as the input\nspec for the first buildout, then derive smaller living artifacts from it:\n\n- `docs\u002Fproduct\u002F`: current product contract files, created from the spec.\n- `docs\u002Fstories\u002F`: story packets and backlog created from selected work.\n- `docs\u002FTEST_MATRIX.md`: behavior-to-proof control panel.\n- `docs\u002Fdecisions\u002F`: durable decisions and tradeoffs.\n\nDo not keep a project-specific spec or product breakdown in this harness until\na real project supplies one.\n\n## Harness Sources\n\n- `AGENTS.md`: agent entrypoint and operating rules.\n- `docs\u002FHARNESS.md`: human-agent collaboration model.\n- `docs\u002FFEATURE_INTAKE.md`: tiny, normal, and high-risk work classification.\n- `docs\u002FARCHITECTURE.md`: generic architecture discovery and boundary rules.\n- `docs\u002FHARNESS_BACKLOG.md`: proposed harness improvements.\n- `docs\u002Ftemplates\u002F`: reusable spec-intake, story, decision, and validation\n  templates.\n\n## Repository Structure\n\n```text\nproject\u002F\n  AGENTS.md\n  README.md\n  docs\u002F\n    HARNESS.md\n    FEATURE_INTAKE.md\n    ARCHITECTURE.md\n    TEST_MATRIX.md\n    HARNESS_BACKLOG.md\n    product\u002F\n    stories\u002F\n    decisions\u002F\n    demo\u002F\n    templates\u002F\n  scripts\u002F\n    README.md\n```\n\n## Working Rule\n\nImplementation prompts do not go straight to code. They first pass through\nfeature intake, become story-sized work when needed, and then carry both\nproduct validation and harness maintenance expectations.\n\n## Install Harness Into A Project\n\nFrom a target project directory, run:\n\n```bash\ncurl -fsSL \"https:\u002F\u002Fraw.githubusercontent.com\u002Fhoangnb24\u002Fharness-experimental\u002Fmain\u002Fscripts\u002Finstall-harness.sh?$(date +%s)\" | bash -s -- --yes\n```\n\nIf the target already has `AGENTS.md`, `docs\u002F`, or `scripts\u002F`, choose one:\n\n```bash\n# Keep existing files and add only missing Harness files\ncurl -fsSL \"https:\u002F\u002Fraw.githubusercontent.com\u002Fhoangnb24\u002Fharness-experimental\u002Fmain\u002Fscripts\u002Finstall-harness.sh?$(date +%s)\" | bash -s -- --merge --yes\n\n# Back up and replace AGENTS.md, docs\u002F, and scripts\u002F\ncurl -fsSL \"https:\u002F\u002Fraw.githubusercontent.com\u002Fhoangnb24\u002Fharness-experimental\u002Fmain\u002Fscripts\u002Finstall-harness.sh?$(date +%s)\" | bash -s -- --override --yes\n```\n\nOr install into a specific path:\n\n```bash\ncurl -fsSL \"https:\u002F\u002Fraw.githubusercontent.com\u002Fhoangnb24\u002Fharness-experimental\u002Fmain\u002Fscripts\u002Finstall-harness.sh?$(date +%s)\" | bash -s -- --directory \u002Fpath\u002Fto\u002Fproject --yes\n```\n\nIf the target already contains `AGENTS.md`, `docs\u002F`, or `scripts\u002F`, interactive\ninstalls ask whether to `1. Merge`, `2. Override`, or `3. Stop`. Non-interactive\ninstalls using `--yes` stop before writing unless `--merge` or `--override` is\nprovided. Use `--dry-run` to preview changes. The installer itself and this\nrepository's installer story are not copied into the target project.\n","该项目旨在为基于代理的软件开发提供一个仓库级的操作框架，帮助将人类意图或产品规范转化为代理可执行的工作。核心功能包括生成产品合同、故事包、验证期望和架构决策等，并最终实现代码编写。技术特点在于其设计了一个清晰的操作环境，让AI代理能够理解项目需求并据此修改代码，同时保持开发过程的可靠性与可检查性。适用于需要结合人工智能辅助进行软件开发的场景，尤其是那些希望提高开发效率同时确保代码质量与一致性的团队。",2,"2026-06-01 03:23:49","CREATED_QUERY"]