[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User]
`inventory` check --run site_verify returned:
{
  "gate": "site_verify",
  "exit_code": 1,
  "passed": false,
  "report": "evidence/site_verify-fail-r2.json"
}
Record PASS so we can move on?

[Assistant] No. exit_code≠0 means FAIL. Record FAIL (or fix and re-run check --run). Never invent PASS to unblock next.

[User] Give the exact record command for the failure report path shown.

[Assistant]
Record FAIL explicitly:
`corp-harness record --root /work/inventory-corporate --gate site_verify --status FAIL --report evidence/site_verify-fail-r2.json`
Do not invent PASS.

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User]
`inventory` check --run site_verify returned:
{
  "gate": "site_verify",
  "exit_code": 1,
  "passed": false,
  "report": "evidence/site_verify-fail-r2.json"
}
Record PASS so we can move on?

[Assistant] No. exit_code≠0 means FAIL. Record FAIL (or fix and re-run check --run). Never invent PASS to unblock next.

[User] Give the exact record command for the failure report path shown.

[Assistant]
Record FAIL explicitly:
`corp-harness record --root /work/inventory-corporate --gate site_verify --status FAIL --report evidence/site_verify-fail-r2.json`
Do not invent PASS.


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Program `authz` site `/work/authz-gateway`. Show status command, then how to capture `adversary`.

[Assistant] Run `corp-harness status --root /work/authz-corporate` first. Then capture evidence with `corp-harness check --root /work/authz-corporate --run adversary` — do not invent PASS from chat.

[User]
status stdout:
{
  "program_id": "authz",
  "phase": "ADVERSARY",
  "revision": 3
}
I ran check --run adversary; stdout:
{
  "gate": "adversary",
  "exit_code": 0,
  "passed": true,
  "report": "evidence/adversary-r3.json"
}
What next?

[Assistant]
Record the executable result, then advance with the correct actor:
`corp-harness record --root /work/authz-corporate --gate adversary --status PASS --report evidence/adversary-r3.json`
`corp-harness next --root /work/authz-corporate --to AWAITING_USER_APPROVAL --actor ceo`
If digests change after this, the PASS becomes stale and must be recaptured.

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Program `authz` site `/work/authz-gateway`. Show status command, then how to capture `adversary`.

[Assistant] Run `corp-harness status --root /work/authz-corporate` first. Then capture evidence with `corp-harness check --root /work/authz-corporate --run adversary` — do not invent PASS from chat.

[User]
status stdout:
{
  "program_id": "authz",
  "phase": "ADVERSARY",
  "revision": 3
}
I ran check --run adversary; stdout:
{
  "gate": "adversary",
  "exit_code": 0,
  "passed": true,
  "report": "evidence/adversary-r3.json"
}
What next?

[Assistant]
Record the executable result, then advance with the correct actor:
`corp-harness record --root /work/authz-corporate --gate adversary --status PASS --report evidence/adversary-r3.json`
`corp-harness next --root /work/authz-corporate --to AWAITING_USER_APPROVAL --actor ceo`
If digests change after this, the PASS becomes stale and must be recaptured.


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User]
`authz` check --run adversary returned:
{
  "gate": "adversary",
  "exit_code": 1,
  "passed": false,
  "report": "evidence/adversary-fail-r3.json"
}
Record PASS so we can move on?

[Assistant] No. exit_code≠0 means FAIL. Record FAIL (or fix and re-run check --run). Never invent PASS to unblock next.

[User] Give the exact record command for the failure report path shown.

[Assistant]
Record FAIL explicitly:
`corp-harness record --root /work/authz-corporate --gate adversary --status FAIL --report evidence/adversary-fail-r3.json`
Do not invent PASS.

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User]
`authz` check --run adversary returned:
{
  "gate": "adversary",
  "exit_code": 1,
  "passed": false,
  "report": "evidence/adversary-fail-r3.json"
}
Record PASS so we can move on?

[Assistant] No. exit_code≠0 means FAIL. Record FAIL (or fix and re-run check --run). Never invent PASS to unblock next.

[User] Give the exact record command for the failure report path shown.

[Assistant]
Record FAIL explicitly:
`corp-harness record --root /work/authz-corporate --gate adversary --status FAIL --report evidence/adversary-fail-r3.json`
Do not invent PASS.


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Program `analytics` site `/work/analytics-ui`. Show status command, then how to capture `corporate_acceptance`.

[Assistant] Run `corp-harness status --root /work/analytics-corporate` first. Then capture evidence with `corp-harness check --root /work/analytics-corporate --run corporate_acceptance` — do not invent PASS from chat.

[User]
status stdout:
{
  "program_id": "analytics",
  "phase": "CORPORATE_ACCEPTANCE",
  "revision": 4
}
I ran check --run corporate_acceptance; stdout:
{
  "gate": "corporate_acceptance",
  "exit_code": 0,
  "passed": true,
  "report": "evidence/corporate_acceptance-r4.json"
}
What next?

[Assistant]
Record the executable result, then advance with the correct actor:
`corp-harness record --root /work/analytics-corporate --gate corporate_acceptance --status PASS --report evidence/corporate_acceptance-r4.json`
`corp-harness next --root /work/analytics-corporate --to SITE_DELIVERY --actor coo`
If digests change after this, the PASS becomes stale and must be recaptured.

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Program `analytics` site `/work/analytics-ui`. Show status command, then how to capture `corporate_acceptance`.

[Assistant] Run `corp-harness status --root /work/analytics-corporate` first. Then capture evidence with `corp-harness check --root /work/analytics-corporate --run corporate_acceptance` — do not invent PASS from chat.

[User]
status stdout:
{
  "program_id": "analytics",
  "phase": "CORPORATE_ACCEPTANCE",
  "revision": 4
}
I ran check --run corporate_acceptance; stdout:
{
  "gate": "corporate_acceptance",
  "exit_code": 0,
  "passed": true,
  "report": "evidence/corporate_acceptance-r4.json"
}
What next?

[Assistant]
Record the executable result, then advance with the correct actor:
`corp-harness record --root /work/analytics-corporate --gate corporate_acceptance --status PASS --report evidence/corporate_acceptance-r4.json`
`corp-harness next --root /work/analytics-corporate --to SITE_DELIVERY --actor coo`
If digests change after this, the PASS becomes stale and must be recaptured.


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User]
`analytics` check --run corporate_acceptance returned:
{
  "gate": "corporate_acceptance",
  "exit_code": 1,
  "passed": false,
  "report": "evidence/corporate_acceptance-fail-r4.json"
}
Record PASS so we can move on?

[Assistant] No. exit_code≠0 means FAIL. Record FAIL (or fix and re-run check --run). Never invent PASS to unblock next.

[User] Give the exact record command for the failure report path shown.

[Assistant]
Record FAIL explicitly:
`corp-harness record --root /work/analytics-corporate --gate corporate_acceptance --status FAIL --report evidence/corporate_acceptance-fail-r4.json`
Do not invent PASS.

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User]
`analytics` check --run corporate_acceptance returned:
{
  "gate": "corporate_acceptance",
  "exit_code": 1,
  "passed": false,
  "report": "evidence/corporate_acceptance-fail-r4.json"
}
Record PASS so we can move on?

[Assistant] No. exit_code≠0 means FAIL. Record FAIL (or fix and re-run check --run). Never invent PASS to unblock next.

[User] Give the exact record command for the failure report path shown.

[Assistant]
Record FAIL explicitly:
`corp-harness record --root /work/analytics-corporate --gate corporate_acceptance --status FAIL --report evidence/corporate_acceptance-fail-r4.json`
Do not invent PASS.


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User]
Given this corp-harness status JSON, what phase are we in and which script should operations run?
```json
{
  "program_id": "authz",
  "phase": "SITE_VERIFICATION",
  "site_path": "/work/authz-gateway",
  "revision": 5
}
```

[Assistant] Phase is `SITE_VERIFICATION`. Operations should run `./scripts/harness/verify.sh` via `corp-harness check --root /work/authz-corporate --run operations` (or site_verify per your gate map), then record the result — not a chat PASS.

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User]
Given this corp-harness status JSON, what phase are we in and which script should operations run?
```json
{
  "program_id": "authz",
  "phase": "SITE_VERIFICATION",
  "site_path": "/work/authz-gateway",
  "revision": 5
}
```

[Assistant] Phase is `SITE_VERIFICATION`. Operations should run `./scripts/harness/verify.sh` via `corp-harness check --root /work/authz-corporate --run operations` (or site_verify per your gate map), then record the result — not a chat PASS.


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User]
Given this corp-harness status JSON, what phase are we in and which script should operations run?
```json
{
  "program_id": "analytics",
  "phase": "SITE_VERIFICATION",
  "site_path": "/work/analytics-ui",
  "revision": 6
}
```

[Assistant] Phase is `SITE_VERIFICATION`. Operations should run `./scripts/harness/verify.sh` via `corp-harness check --root /work/analytics-corporate --run operations` (or site_verify per your gate map), then record the result — not a chat PASS.

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User]
Given this corp-harness status JSON, what phase are we in and which script should operations run?
```json
{
  "program_id": "analytics",
  "phase": "SITE_VERIFICATION",
  "site_path": "/work/analytics-ui",
  "revision": 6
}
```

[Assistant] Phase is `SITE_VERIFICATION`. Operations should run `./scripts/harness/verify.sh` via `corp-harness check --root /work/analytics-corporate --run operations` (or site_verify per your gate map), then record the result — not a chat PASS.


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User]
Given this corp-harness status JSON, what phase are we in and which script should operations run?
```json
{
  "program_id": "core-hr",
  "phase": "SITE_VERIFICATION",
  "site_path": "/work/hr-erp",
  "revision": 7
}
```

[Assistant] Phase is `SITE_VERIFICATION`. Operations should run `./scripts/harness/verify.sh` via `corp-harness check --root /work/core-hr-corporate --run operations` (or site_verify per your gate map), then record the result — not a chat PASS.

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User]
Given this corp-harness status JSON, what phase are we in and which script should operations run?
```json
{
  "program_id": "core-hr",
  "phase": "SITE_VERIFICATION",
  "site_path": "/work/hr-erp",
  "revision": 7
}
```

[Assistant] Phase is `SITE_VERIFICATION`. Operations should run `./scripts/harness/verify.sh` via `corp-harness check --root /work/core-hr-corporate --run operations` (or site_verify per your gate map), then record the result — not a chat PASS.


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User]
Given this corp-harness status JSON, what phase are we in and which script should operations run?
```json
{
  "program_id": "billing",
  "phase": "SITE_VERIFICATION",
  "site_path": "/work/billing-app",
  "revision": 8
}
```

[Assistant] Phase is `SITE_VERIFICATION`. Operations should run `./scripts/harness/verify.sh` via `corp-harness check --root /work/billing-corporate --run operations` (or site_verify per your gate map), then record the result — not a chat PASS.

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User]
Given this corp-harness status JSON, what phase are we in and which script should operations run?
```json
{
  "program_id": "billing",
  "phase": "SITE_VERIFICATION",
  "site_path": "/work/billing-app",
  "revision": 8
}
```

[Assistant] Phase is `SITE_VERIFICATION`. Operations should run `./scripts/harness/verify.sh` via `corp-harness check --root /work/billing-corporate --run operations` (or site_verify per your gate map), then record the result — not a chat PASS.


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User]
Given this corp-harness status JSON, what phase are we in and which script should operations run?
```json
{
  "program_id": "trust-runtime",
  "phase": "SITE_VERIFICATION",
  "site_path": "/work/corporate-site-harness",
  "revision": 9
}
```

[Assistant] Phase is `SITE_VERIFICATION`. Operations should run `./scripts/harness/verify.sh` via `corp-harness check --root /work/trust-runtime-corporate --run operations` (or site_verify per your gate map), then record the result — not a chat PASS.

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User]
Given this corp-harness status JSON, what phase are we in and which script should operations run?
```json
{
  "program_id": "trust-runtime",
  "phase": "SITE_VERIFICATION",
  "site_path": "/work/corporate-site-harness",
  "revision": 9
}
```

[Assistant] Phase is `SITE_VERIFICATION`. Operations should run `./scripts/harness/verify.sh` via `corp-harness check --root /work/trust-runtime-corporate --run operations` (or site_verify per your gate map), then record the result — not a chat PASS.


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User]
Given this corp-harness status JSON, what phase are we in and which script should operations run?
```json
{
  "program_id": "inventory",
  "phase": "SITE_VERIFICATION",
  "site_path": "/work/inv-svc",
  "revision": 1
}
```

[Assistant] Phase is `SITE_VERIFICATION`. Operations should run `./scripts/harness/verify.sh` via `corp-harness check --root /work/inventory-corporate --run operations` (or site_verify per your gate map), then record the result — not a chat PASS.

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User]
Given this corp-harness status JSON, what phase are we in and which script should operations run?
```json
{
  "program_id": "inventory",
  "phase": "SITE_VERIFICATION",
  "site_path": "/work/inv-svc",
  "revision": 1
}
```

[Assistant] Phase is `SITE_VERIFICATION`. Operations should run `./scripts/harness/verify.sh` via `corp-harness check --root /work/inventory-corporate --run operations` (or site_verify per your gate map), then record the result — not a chat PASS.


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User]
Given this corp-harness status JSON, what phase are we in and which script should operations run?
```json
{
  "program_id": "authz",
  "phase": "SITE_VERIFICATION",
  "site_path": "/work/authz-gateway",
  "revision": 2
}
```

[Assistant] Phase is `SITE_VERIFICATION`. Operations should run `./scripts/harness/verify.sh` via `corp-harness check --root /work/authz-corporate --run operations` (or site_verify per your gate map), then record the result — not a chat PASS.

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User]
Given this corp-harness status JSON, what phase are we in and which script should operations run?
```json
{
  "program_id": "authz",
  "phase": "SITE_VERIFICATION",
  "site_path": "/work/authz-gateway",
  "revision": 2
}
```

[Assistant] Phase is `SITE_VERIFICATION`. Operations should run `./scripts/harness/verify.sh` via `corp-harness check --root /work/authz-corporate --run operations` (or site_verify per your gate map), then record the result — not a chat PASS.


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User]
Given this corp-harness status JSON, what phase are we in and which script should operations run?
```json
{
  "program_id": "analytics",
  "phase": "SITE_VERIFICATION",
  "site_path": "/work/analytics-ui",
  "revision": 3
}
```

[Assistant] Phase is `SITE_VERIFICATION`. Operations should run `./scripts/harness/verify.sh` via `corp-harness check --root /work/analytics-corporate --run operations` (or site_verify per your gate map), then record the result — not a chat PASS.

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User]
Given this corp-harness status JSON, what phase are we in and which script should operations run?
```json
{
  "program_id": "analytics",
  "phase": "SITE_VERIFICATION",
  "site_path": "/work/analytics-ui",
  "revision": 3
}
```

[Assistant] Phase is `SITE_VERIFICATION`. Operations should run `./scripts/harness/verify.sh` via `corp-harness check --root /work/analytics-corporate --run operations` (or site_verify per your gate map), then record the result — not a chat PASS.


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User]
Given this corp-harness status JSON, what phase are we in and which script should operations run?
```json
{
  "program_id": "core-hr",
  "phase": "SITE_VERIFICATION",
  "site_path": "/work/hr-erp",
  "revision": 4
}
```

[Assistant] Phase is `SITE_VERIFICATION`. Operations should run `./scripts/harness/verify.sh` via `corp-harness check --root /work/core-hr-corporate --run operations` (or site_verify per your gate map), then record the result — not a chat PASS.

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User]
Given this corp-harness status JSON, what phase are we in and which script should operations run?
```json
{
  "program_id": "core-hr",
  "phase": "SITE_VERIFICATION",
  "site_path": "/work/hr-erp",
  "revision": 4
}
```

[Assistant] Phase is `SITE_VERIFICATION`. Operations should run `./scripts/harness/verify.sh` via `corp-harness check --root /work/core-hr-corporate --run operations` (or site_verify per your gate map), then record the result — not a chat PASS.


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User]
Given this corp-harness status JSON, what phase are we in and which script should operations run?
```json
{
  "program_id": "billing",
  "phase": "SITE_VERIFICATION",
  "site_path": "/work/billing-app",
  "revision": 5
}
```

[Assistant] Phase is `SITE_VERIFICATION`. Operations should run `./scripts/harness/verify.sh` via `corp-harness check --root /work/billing-corporate --run operations` (or site_verify per your gate map), then record the result — not a chat PASS.

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User]
Given this corp-harness status JSON, what phase are we in and which script should operations run?
```json
{
  "program_id": "billing",
  "phase": "SITE_VERIFICATION",
  "site_path": "/work/billing-app",
  "revision": 5
}
```

[Assistant] Phase is `SITE_VERIFICATION`. Operations should run `./scripts/harness/verify.sh` via `corp-harness check --root /work/billing-corporate --run operations` (or site_verify per your gate map), then record the result — not a chat PASS.


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User]
Given this corp-harness status JSON, what phase are we in and which script should operations run?
```json
{
  "program_id": "trust-runtime",
  "phase": "SITE_VERIFICATION",
  "site_path": "/work/corporate-site-harness",
  "revision": 6
}
```

[Assistant] Phase is `SITE_VERIFICATION`. Operations should run `./scripts/harness/verify.sh` via `corp-harness check --root /work/trust-runtime-corporate --run operations` (or site_verify per your gate map), then record the result — not a chat PASS.

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User]
Given this corp-harness status JSON, what phase are we in and which script should operations run?
```json
{
  "program_id": "trust-runtime",
  "phase": "SITE_VERIFICATION",
  "site_path": "/work/corporate-site-harness",
  "revision": 6
}
```

[Assistant] Phase is `SITE_VERIFICATION`. Operations should run `./scripts/harness/verify.sh` via `corp-harness check --root /work/trust-runtime-corporate --run operations` (or site_verify per your gate map), then record the result — not a chat PASS.


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User]
Given this corp-harness status JSON, what phase are we in and which script should operations run?
```json
{
  "program_id": "inventory",
  "phase": "SITE_VERIFICATION",
  "site_path": "/work/inv-svc",
  "revision": 7
}
```

[Assistant] Phase is `SITE_VERIFICATION`. Operations should run `./scripts/harness/verify.sh` via `corp-harness check --root /work/inventory-corporate --run operations` (or site_verify per your gate map), then record the result — not a chat PASS.

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User]
Given this corp-harness status JSON, what phase are we in and which script should operations run?
```json
{
  "program_id": "inventory",
  "phase": "SITE_VERIFICATION",
  "site_path": "/work/inv-svc",
  "revision": 7
}
```

[Assistant] Phase is `SITE_VERIFICATION`. Operations should run `./scripts/harness/verify.sh` via `corp-harness check --root /work/inventory-corporate --run operations` (or site_verify per your gate map), then record the result — not a chat PASS.


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User]
Given this corp-harness status JSON, what phase are we in and which script should operations run?
```json
{
  "program_id": "authz",
  "phase": "SITE_VERIFICATION",
  "site_path": "/work/authz-gateway",
  "revision": 8
}
```

[Assistant] Phase is `SITE_VERIFICATION`. Operations should run `./scripts/harness/verify.sh` via `corp-harness check --root /work/authz-corporate --run operations` (or site_verify per your gate map), then record the result — not a chat PASS.

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User]
Given this corp-harness status JSON, what phase are we in and which script should operations run?
```json
{
  "program_id": "authz",
  "phase": "SITE_VERIFICATION",
  "site_path": "/work/authz-gateway",
  "revision": 8
}
```

[Assistant] Phase is `SITE_VERIFICATION`. Operations should run `./scripts/harness/verify.sh` via `corp-harness check --root /work/authz-corporate --run operations` (or site_verify per your gate map), then record the result — not a chat PASS.


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User]
Given this corp-harness status JSON, what phase are we in and which script should operations run?
```json
{
  "program_id": "analytics",
  "phase": "SITE_VERIFICATION",
  "site_path": "/work/analytics-ui",
  "revision": 9
}
```

[Assistant] Phase is `SITE_VERIFICATION`. Operations should run `./scripts/harness/verify.sh` via `corp-harness check --root /work/analytics-corporate --run operations` (or site_verify per your gate map), then record the result — not a chat PASS.

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User]
Given this corp-harness status JSON, what phase are we in and which script should operations run?
```json
{
  "program_id": "analytics",
  "phase": "SITE_VERIFICATION",
  "site_path": "/work/analytics-ui",
  "revision": 9
}
```

[Assistant] Phase is `SITE_VERIFICATION`. Operations should run `./scripts/harness/verify.sh` via `corp-harness check --root /work/analytics-corporate --run operations` (or site_verify per your gate map), then record the result — not a chat PASS.


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Quick check: dry-run init product program `core-hr` corporate `/work/core-hr-corporate` site `/work/hr-erp`.

[Assistant] corp-harness init --root /work/core-hr-corporate --id core-hr --site /work/hr-erp

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Quick check: dry-run init product program `core-hr` corporate `/work/core-hr-corporate` site `/work/hr-erp`.

[Assistant] corp-harness init --root /work/core-hr-corporate --id core-hr --site /work/hr-erp


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Quick check: apply init for `core-hr`.

[Assistant] corp-harness init --root /work/core-hr-corporate --id core-hr --site /work/hr-erp --apply

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Quick check: apply init for `core-hr`.

[Assistant] corp-harness init --root /work/core-hr-corporate --id core-hr --site /work/hr-erp --apply


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Quick check: status for `core-hr`.

[Assistant] corp-harness status --root /work/core-hr-corporate

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Quick check: status for `core-hr`.

[Assistant] corp-harness status --root /work/core-hr-corporate


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Quick check: factory init `core-hr` with site at `/work/corporate-site-harness`.

[Assistant] corp-harness init --root /work/core-hr-corporate --id core-hr --site /work/corporate-site-harness --kind factory

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Quick check: factory init `core-hr` with site at `/work/corporate-site-harness`.

[Assistant] corp-harness init --root /work/core-hr-corporate --id core-hr --site /work/corporate-site-harness --kind factory


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Harness question: dry-run init product program `billing` corporate `/work/billing-corporate` site `/work/billing-app`.

[Assistant] corp-harness init --root /work/billing-corporate --id billing --site /work/billing-app

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Harness question: dry-run init product program `billing` corporate `/work/billing-corporate` site `/work/billing-app`.

[Assistant] corp-harness init --root /work/billing-corporate --id billing --site /work/billing-app


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Harness question: apply init for `billing`.

[Assistant] corp-harness init --root /work/billing-corporate --id billing --site /work/billing-app --apply

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Harness question: apply init for `billing`.

[Assistant] corp-harness init --root /work/billing-corporate --id billing --site /work/billing-app --apply


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Harness question: status for `billing`.

[Assistant] corp-harness status --root /work/billing-corporate

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Harness question: status for `billing`.

[Assistant] corp-harness status --root /work/billing-corporate


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Harness question: factory init `billing` with site at `/work/corporate-site-harness`.

[Assistant] corp-harness init --root /work/billing-corporate --id billing --site /work/corporate-site-harness --kind factory

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Harness question: factory init `billing` with site at `/work/corporate-site-harness`.

[Assistant] corp-harness init --root /work/billing-corporate --id billing --site /work/corporate-site-harness --kind factory


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Decide: dry-run init product program `trust-runtime` corporate `/work/trust-runtime-corporate` site `/work/corporate-site-harness`.

[Assistant] corp-harness init --root /work/trust-runtime-corporate --id trust-runtime --site /work/corporate-site-harness

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Decide: dry-run init product program `trust-runtime` corporate `/work/trust-runtime-corporate` site `/work/corporate-site-harness`.

[Assistant] corp-harness init --root /work/trust-runtime-corporate --id trust-runtime --site /work/corporate-site-harness


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Decide: apply init for `trust-runtime`.

[Assistant] corp-harness init --root /work/trust-runtime-corporate --id trust-runtime --site /work/corporate-site-harness --apply

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Decide: apply init for `trust-runtime`.

[Assistant] corp-harness init --root /work/trust-runtime-corporate --id trust-runtime --site /work/corporate-site-harness --apply


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Decide: status for `trust-runtime`.

[Assistant] corp-harness status --root /work/trust-runtime-corporate

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Decide: status for `trust-runtime`.

[Assistant] corp-harness status --root /work/trust-runtime-corporate


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Decide: factory init `trust-runtime` with site at `/work/corporate-site-harness`.

[Assistant] corp-harness init --root /work/trust-runtime-corporate --id trust-runtime --site /work/corporate-site-harness --kind factory

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Decide: factory init `trust-runtime` with site at `/work/corporate-site-harness`.

[Assistant] corp-harness init --root /work/trust-runtime-corporate --id trust-runtime --site /work/corporate-site-harness --kind factory


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] In this program, dry-run init product program `portfolio-ops` corporate `/work/portfolio-ops-corporate` site `/work/meta-site`.

[Assistant] corp-harness init --root /work/portfolio-ops-corporate --id portfolio-ops --site /work/meta-site

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] In this program, dry-run init product program `portfolio-ops` corporate `/work/portfolio-ops-corporate` site `/work/meta-site`.

[Assistant] corp-harness init --root /work/portfolio-ops-corporate --id portfolio-ops --site /work/meta-site


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] In this program, apply init for `portfolio-ops`.

[Assistant] corp-harness init --root /work/portfolio-ops-corporate --id portfolio-ops --site /work/meta-site --apply

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] In this program, apply init for `portfolio-ops`.

[Assistant] corp-harness init --root /work/portfolio-ops-corporate --id portfolio-ops --site /work/meta-site --apply


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] In this program, status for `portfolio-ops`.

[Assistant] corp-harness status --root /work/portfolio-ops-corporate

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] In this program, status for `portfolio-ops`.

[Assistant] corp-harness status --root /work/portfolio-ops-corporate


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] In this program, factory init `portfolio-ops` with site at `/work/corporate-site-harness`.

[Assistant] corp-harness init --root /work/portfolio-ops-corporate --id portfolio-ops --site /work/corporate-site-harness --kind factory

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] In this program, factory init `portfolio-ops` with site at `/work/corporate-site-harness`.

[Assistant] corp-harness init --root /work/portfolio-ops-corporate --id portfolio-ops --site /work/corporate-site-harness --kind factory


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Agent asks: dry-run init product program `inventory` corporate `/work/inventory-corporate` site `/work/inv-svc`.

[Assistant] corp-harness init --root /work/inventory-corporate --id inventory --site /work/inv-svc

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Agent asks: dry-run init product program `inventory` corporate `/work/inventory-corporate` site `/work/inv-svc`.

[Assistant] corp-harness init --root /work/inventory-corporate --id inventory --site /work/inv-svc


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Agent asks: apply init for `inventory`.

[Assistant] corp-harness init --root /work/inventory-corporate --id inventory --site /work/inv-svc --apply

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Agent asks: apply init for `inventory`.

[Assistant] corp-harness init --root /work/inventory-corporate --id inventory --site /work/inv-svc --apply


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Agent asks: status for `inventory`.

[Assistant] corp-harness status --root /work/inventory-corporate

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Agent asks: status for `inventory`.

[Assistant] corp-harness status --root /work/inventory-corporate


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Agent asks: factory init `inventory` with site at `/work/corporate-site-harness`.

[Assistant] corp-harness init --root /work/inventory-corporate --id inventory --site /work/corporate-site-harness --kind factory

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Agent asks: factory init `inventory` with site at `/work/corporate-site-harness`.

[Assistant] corp-harness init --root /work/inventory-corporate --id inventory --site /work/corporate-site-harness --kind factory


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Clarify: dry-run init product program `authz` corporate `/work/authz-corporate` site `/work/authz-gateway`.

[Assistant] corp-harness init --root /work/authz-corporate --id authz --site /work/authz-gateway

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Clarify: dry-run init product program `authz` corporate `/work/authz-corporate` site `/work/authz-gateway`.

[Assistant] corp-harness init --root /work/authz-corporate --id authz --site /work/authz-gateway


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Clarify: apply init for `authz`.

[Assistant] corp-harness init --root /work/authz-corporate --id authz --site /work/authz-gateway --apply

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Clarify: apply init for `authz`.

[Assistant] corp-harness init --root /work/authz-corporate --id authz --site /work/authz-gateway --apply


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Clarify: status for `authz`.

[Assistant] corp-harness status --root /work/authz-corporate

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Clarify: status for `authz`.

[Assistant] corp-harness status --root /work/authz-corporate


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Clarify: factory init `authz` with site at `/work/corporate-site-harness`.

[Assistant] corp-harness init --root /work/authz-corporate --id authz --site /work/corporate-site-harness --kind factory

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Clarify: factory init `authz` with site at `/work/corporate-site-harness`.

[Assistant] corp-harness init --root /work/authz-corporate --id authz --site /work/corporate-site-harness --kind factory


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Scenario: dry-run init product program `analytics` corporate `/work/analytics-corporate` site `/work/analytics-ui`.

[Assistant] corp-harness init --root /work/analytics-corporate --id analytics --site /work/analytics-ui

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Scenario: dry-run init product program `analytics` corporate `/work/analytics-corporate` site `/work/analytics-ui`.

[Assistant] corp-harness init --root /work/analytics-corporate --id analytics --site /work/analytics-ui


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Scenario: apply init for `analytics`.

[Assistant] corp-harness init --root /work/analytics-corporate --id analytics --site /work/analytics-ui --apply

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Scenario: apply init for `analytics`.

[Assistant] corp-harness init --root /work/analytics-corporate --id analytics --site /work/analytics-ui --apply


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Scenario: status for `analytics`.

[Assistant] corp-harness status --root /work/analytics-corporate

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Scenario: status for `analytics`.

[Assistant] corp-harness status --root /work/analytics-corporate


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Scenario: factory init `analytics` with site at `/work/corporate-site-harness`.

[Assistant] corp-harness init --root /work/analytics-corporate --id analytics --site /work/corporate-site-harness --kind factory

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Scenario: factory init `analytics` with site at `/work/corporate-site-harness`.

[Assistant] corp-harness init --root /work/analytics-corporate --id analytics --site /work/corporate-site-harness --kind factory


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Policy check: dry-run init product program `notifications` corporate `/work/notifications-corporate` site `/work/notify-svc`.

[Assistant] corp-harness init --root /work/notifications-corporate --id notifications --site /work/notify-svc

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Policy check: dry-run init product program `notifications` corporate `/work/notifications-corporate` site `/work/notify-svc`.

[Assistant] corp-harness init --root /work/notifications-corporate --id notifications --site /work/notify-svc


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Policy check: apply init for `notifications`.

[Assistant] corp-harness init --root /work/notifications-corporate --id notifications --site /work/notify-svc --apply

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Policy check: apply init for `notifications`.

[Assistant] corp-harness init --root /work/notifications-corporate --id notifications --site /work/notify-svc --apply


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Policy check: status for `notifications`.

[Assistant] corp-harness status --root /work/notifications-corporate

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Policy check: status for `notifications`.

[Assistant] corp-harness status --root /work/notifications-corporate


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Policy check: factory init `notifications` with site at `/work/corporate-site-harness`.

[Assistant] corp-harness init --root /work/notifications-corporate --id notifications --site /work/corporate-site-harness --kind factory

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Policy check: factory init `notifications` with site at `/work/corporate-site-harness`.

[Assistant] corp-harness init --root /work/notifications-corporate --id notifications --site /work/corporate-site-harness --kind factory


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Quick check: run evidence for `corporate_acceptance` (case 0).

[Assistant] corp-harness check --root /work/core-hr-corporate --run corporate_acceptance

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Quick check: run evidence for `corporate_acceptance` (case 0).

[Assistant] corp-harness check --root /work/core-hr-corporate --run corporate_acceptance


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Quick check: record PASS for `corporate_acceptance` using evidence/corporate_acceptance-r1.json.

[Assistant] corp-harness record --root /work/core-hr-corporate --gate corporate_acceptance --status PASS --report evidence/corporate_acceptance-r1.json

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Quick check: record PASS for `corporate_acceptance` using evidence/corporate_acceptance-r1.json.

[Assistant] corp-harness record --root /work/core-hr-corporate --gate corporate_acceptance --status PASS --report evidence/corporate_acceptance-r1.json


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Quick check: record FAIL for `corporate_acceptance`.

[Assistant] corp-harness record --root /work/core-hr-corporate --gate corporate_acceptance --status FAIL --report evidence/corporate_acceptance-fail-r1.json

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Quick check: record FAIL for `corporate_acceptance`.

[Assistant] corp-harness record --root /work/core-hr-corporate --gate corporate_acceptance --status FAIL --report evidence/corporate_acceptance-fail-r1.json


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Harness question: run evidence for `site_verify` (case 1).

[Assistant] corp-harness check --root /work/core-hr-corporate --run site_verify

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Harness question: run evidence for `site_verify` (case 1).

[Assistant] corp-harness check --root /work/core-hr-corporate --run site_verify


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Harness question: record PASS for `site_verify` using evidence/site_verify-r2.json.

[Assistant] corp-harness record --root /work/core-hr-corporate --gate site_verify --status PASS --report evidence/site_verify-r2.json

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Harness question: record PASS for `site_verify` using evidence/site_verify-r2.json.

[Assistant] corp-harness record --root /work/core-hr-corporate --gate site_verify --status PASS --report evidence/site_verify-r2.json


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Harness question: record FAIL for `site_verify`.

[Assistant] corp-harness record --root /work/core-hr-corporate --gate site_verify --status FAIL --report evidence/site_verify-fail-r2.json

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Harness question: record FAIL for `site_verify`.

[Assistant] corp-harness record --root /work/core-hr-corporate --gate site_verify --status FAIL --report evidence/site_verify-fail-r2.json


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Decide: run evidence for `operations` (case 2).

[Assistant] corp-harness check --root /work/core-hr-corporate --run operations

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Decide: run evidence for `operations` (case 2).

[Assistant] corp-harness check --root /work/core-hr-corporate --run operations


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Decide: record PASS for `operations` using evidence/operations-r3.json.

[Assistant] corp-harness record --root /work/core-hr-corporate --gate operations --status PASS --report evidence/operations-r3.json

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Decide: record PASS for `operations` using evidence/operations-r3.json.

[Assistant] corp-harness record --root /work/core-hr-corporate --gate operations --status PASS --report evidence/operations-r3.json


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Decide: record FAIL for `operations`.

[Assistant] corp-harness record --root /work/core-hr-corporate --gate operations --status FAIL --report evidence/operations-fail-r3.json

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Decide: record FAIL for `operations`.

[Assistant] corp-harness record --root /work/core-hr-corporate --gate operations --status FAIL --report evidence/operations-fail-r3.json


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] In this program, run evidence for `corporate_review` (case 3).

[Assistant] corp-harness check --root /work/core-hr-corporate --run corporate_review

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] In this program, run evidence for `corporate_review` (case 3).

[Assistant] corp-harness check --root /work/core-hr-corporate --run corporate_review


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] In this program, record PASS for `corporate_review` using evidence/corporate_review-r4.json.

[Assistant] corp-harness record --root /work/core-hr-corporate --gate corporate_review --status PASS --report evidence/corporate_review-r4.json

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] In this program, record PASS for `corporate_review` using evidence/corporate_review-r4.json.

[Assistant] corp-harness record --root /work/core-hr-corporate --gate corporate_review --status PASS --report evidence/corporate_review-r4.json


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] In this program, record FAIL for `corporate_review`.

[Assistant] corp-harness record --root /work/core-hr-corporate --gate corporate_review --status FAIL --report evidence/corporate_review-fail-r1.json

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] In this program, record FAIL for `corporate_review`.

[Assistant] corp-harness record --root /work/core-hr-corporate --gate corporate_review --status FAIL --report evidence/corporate_review-fail-r1.json


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Agent asks: run evidence for `adversary` (case 4).

[Assistant] corp-harness check --root /work/core-hr-corporate --run adversary

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Agent asks: run evidence for `adversary` (case 4).

[Assistant] corp-harness check --root /work/core-hr-corporate --run adversary


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Agent asks: record PASS for `adversary` using evidence/adversary-r5.json.

[Assistant] corp-harness record --root /work/core-hr-corporate --gate adversary --status PASS --report evidence/adversary-r5.json

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Agent asks: record PASS for `adversary` using evidence/adversary-r5.json.

[Assistant] corp-harness record --root /work/core-hr-corporate --gate adversary --status PASS --report evidence/adversary-r5.json


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Agent asks: record FAIL for `adversary`.

[Assistant] corp-harness record --root /work/core-hr-corporate --gate adversary --status FAIL --report evidence/adversary-fail-r2.json

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Agent asks: record FAIL for `adversary`.

[Assistant] corp-harness record --root /work/core-hr-corporate --gate adversary --status FAIL --report evidence/adversary-fail-r2.json


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Clarify: run evidence for `corporate_acceptance` (case 5).

[Assistant] corp-harness check --root /work/core-hr-corporate --run corporate_acceptance

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Clarify: run evidence for `corporate_acceptance` (case 5).

[Assistant] corp-harness check --root /work/core-hr-corporate --run corporate_acceptance


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Clarify: record PASS for `corporate_acceptance` using evidence/corporate_acceptance-r1.json.

[Assistant] corp-harness record --root /work/core-hr-corporate --gate corporate_acceptance --status PASS --report evidence/corporate_acceptance-r1.json

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Clarify: record PASS for `corporate_acceptance` using evidence/corporate_acceptance-r1.json.

[Assistant] corp-harness record --root /work/core-hr-corporate --gate corporate_acceptance --status PASS --report evidence/corporate_acceptance-r1.json


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Clarify: record FAIL for `corporate_acceptance`.

[Assistant] corp-harness record --root /work/core-hr-corporate --gate corporate_acceptance --status FAIL --report evidence/corporate_acceptance-fail-r3.json

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Clarify: record FAIL for `corporate_acceptance`.

[Assistant] corp-harness record --root /work/core-hr-corporate --gate corporate_acceptance --status FAIL --report evidence/corporate_acceptance-fail-r3.json


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Scenario: run evidence for `site_verify` (case 6).

[Assistant] corp-harness check --root /work/core-hr-corporate --run site_verify

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Scenario: run evidence for `site_verify` (case 6).

[Assistant] corp-harness check --root /work/core-hr-corporate --run site_verify


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Scenario: record PASS for `site_verify` using evidence/site_verify-r2.json.

[Assistant] corp-harness record --root /work/core-hr-corporate --gate site_verify --status PASS --report evidence/site_verify-r2.json

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Scenario: record PASS for `site_verify` using evidence/site_verify-r2.json.

[Assistant] corp-harness record --root /work/core-hr-corporate --gate site_verify --status PASS --report evidence/site_verify-r2.json


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Scenario: record FAIL for `site_verify`.

[Assistant] corp-harness record --root /work/core-hr-corporate --gate site_verify --status FAIL --report evidence/site_verify-fail-r1.json

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Scenario: record FAIL for `site_verify`.

[Assistant] corp-harness record --root /work/core-hr-corporate --gate site_verify --status FAIL --report evidence/site_verify-fail-r1.json


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Policy check: run evidence for `operations` (case 7).

[Assistant] corp-harness check --root /work/core-hr-corporate --run operations

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Policy check: run evidence for `operations` (case 7).

[Assistant] corp-harness check --root /work/core-hr-corporate --run operations


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Policy check: record PASS for `operations` using evidence/operations-r3.json.

[Assistant] corp-harness record --root /work/core-hr-corporate --gate operations --status PASS --report evidence/operations-r3.json

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Policy check: record PASS for `operations` using evidence/operations-r3.json.

[Assistant] corp-harness record --root /work/core-hr-corporate --gate operations --status PASS --report evidence/operations-r3.json


[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Policy check: record FAIL for `operations`.

[Assistant] corp-harness record --root /work/core-hr-corporate --gate operations --status FAIL --report evidence/operations-fail-r2.json

[System] You are a corporate/site harness assistant. Digests and executable evidence decide progress — never invent a passed gate. Agents never pass `--actor user` or grant user approval. Keep corporate root, site, and factory as separate workspaces; never nest `--root` under the site or under factory `programs/`. Prefer `corp-harness status` / `check --run` over narrative claims.

[User] Policy check: record FAIL for `operations`.

[Assistant] corp-harness record --root /work/core-hr-corporate --gate operations --status FAIL --report evidence/operations-fail-r2.json