| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 1 | 1 | 1 | 33% |
| Commands | 0 | 0 | 0 | — |
| Section tags | 0 | 1 | 1 | 0% |
What each file covers
Sections
1 shared · 1 only in A · 1 only in B- − Agent Instructions
- + Project Rules
- Harness
Commands
neither file has anySection tags
0 shared · 1 only in A · 1 only in B- − agent-behaviour
- + do-not
Line diff
hoangnb24/repository-harness · AGENTS.md
@@ −1 @@
1# Agent Instructions
2
3<!-- HARNESS:BEGIN -->
4## Harness
5
6Start with the requested outcome, then use the repository as the system of
7record. Read `docs/WORKFLOW.md` and only relevant product, design, plan, code,
8and validation material.
9
10- Answers, explanations, reviews, diagnoses, plans, and status reports are
11 read-only. Inspect only what is needed and do not mutate repository or Harness
12 state.
13- For a bounded change, use an ephemeral plan: inspect the affected behavior and
14 proof, implement, and validate. No control-plane operation is required.
15- Create or update one file under `docs/plans/active/` when work spans sessions,
16 needs coordination, has meaningful dependencies, or requires recovery steps.
17 Move it to `docs/plans/completed/` only after validation.
18- Before editing, identify repository authority for each new externally
19 observable policy. If materially different choices remain open, stop before
20 edits; configurable defaults are not authority.
21- Report reusable agent friction. Change guidance, tools, runbooks, or validation
22 for that purpose only when explicitly asked to use `$improve-harness`.
23- Also pause when product intent remains ambiguous, recovery is difficult,
24 validation is weakened, or authority is insufficient.
25- Claim completion only with relevant executable or observable evidence. Report
26 the outcome, important changes, validation, and unresolved risks.
27
28SQLite intake, story, trace, scoring, audit, and proposal commands are optional
29compatibility features. Use them only when explicitly requested or required by
30an external orchestrator.
31<!-- HARNESS:END -->
32
hoangnb24/repository-harness · CLAUDE.md
@@ +1 @@
1# Project Rules
2
3<!-- HARNESS:BEGIN -->
4## Harness
5
6Claude Code does not auto-load `AGENTS.md`. Import that single canonical
7project instruction source. Keep this bare `@` line outside backticks so the
8import remains active.
9
10@AGENTS.md
11<!-- HARNESS:END -->
12
@@ −1 +1 @@
1−# Agent Instructions
1+# Project Rules
22
33 <!-- HARNESS:BEGIN -->
44 ## Harness
55
6−Start with the requested outcome, then use the repository as the system of
7−record. Read `docs/WORKFLOW.md` and only relevant product, design, plan, code,
8−and validation material.
6+Claude Code does not auto-load `AGENTS.md`. Import that single canonical
7+project instruction source. Keep this bare `@` line outside backticks so the
8+import remains active.
99
10−- Answers, explanations, reviews, diagnoses, plans, and status reports are
11− read-only. Inspect only what is needed and do not mutate repository or Harness
12− state.
13−- For a bounded change, use an ephemeral plan: inspect the affected behavior and
14− proof, implement, and validate. No control-plane operation is required.
15−- Create or update one file under `docs/plans/active/` when work spans sessions,
16− needs coordination, has meaningful dependencies, or requires recovery steps.
17− Move it to `docs/plans/completed/` only after validation.
18−- Before editing, identify repository authority for each new externally
19− observable policy. If materially different choices remain open, stop before
20− edits; configurable defaults are not authority.
21−- Report reusable agent friction. Change guidance, tools, runbooks, or validation
22− for that purpose only when explicitly asked to use `$improve-harness`.
23−- Also pause when product intent remains ambiguous, recovery is difficult,
24− validation is weakened, or authority is insufficient.
25−- Claim completion only with relevant executable or observable evidence. Report
26− the outcome, important changes, validation, and unresolved risks.
27−
28−SQLite intake, story, trace, scoring, audit, and proposal commands are optional
29−compatibility features. Use them only when explicitly requested or required by
30−an external orchestrator.
10+@AGENTS.md
3111 <!-- HARNESS:END -->
3212
