# Judge Q&A

## Q1. What exactly changed from the original package?

The original package had H4/H5/H6 scaffold files but did not enforce them in the orchestrator and did not provide runtime evidence. We added executable harness scripts, Boss protocol integration, tests, trace logs, audit logs, metrics, Level 5 mechanisms, and a submission package.

## Q2. Why do you claim Level 4 is achieved?

Because the pipeline now has automated runtime gates for:

- H4 Security: prompt injection block, PII masking, secret redaction, output filtering.
- H5 Governance: risk scoring, deny-by-default, explicit approval, audit hash-chain.
- H6 AgentOps: latency, token, cost, retry, status, alerts, trace JSON.

These are tested and evidenced in `harness-test-report.md`.

## Q3. Are you claiming full production Level 5?

We claim Level 5 is demonstrated locally with verifiable controls. Full enterprise production Level 5 requires external integrations: IdP-backed approvals, WORM/signed log storage, live provider telemetry APIs, and a hosted dashboard.

## Q4. What is the strongest evidence?

Run:

```bash
cd AINative_OKR_CASAN5
bash .specify/tests/run-casan4-harness-tests.sh
```

It validates H4/H5/H6 and Level 5 evidence end-to-end.

## Q5. How do you prevent prompt injection?

`security-check.sh` blocks known prompt injection patterns, reads policy rules, masks PII, blocks critical secrets in input, and filters output. Evidence: `01-security-attack.stderr`, `security-*.json`.

## Q6. How is governance enforced?

`governance-check.sh` scores risk by action and content. High-risk actions are denied unless explicit approval variables are present. Every decision writes an audit record with `previous_record_hash` and `record_hash`; `verify-audit-chain.sh` validates the chain.

## Q7. How is AgentOps measured?

`agent-metrics.sh` records status, exit code, latency, retry count, token estimate, cost estimate, alerts, input hash, and output hash. Provider usage can be imported through `import-provider-telemetry.sh`.

## Q8. What does the central dashboard show?

`central-agentops-dashboard.html` aggregates local metrics, provider telemetry, fallback records, tool registry decisions, and registered harness projects.

## Q9. What happens if a side-effecting tool runs twice?

The Level 5 tool registry requires idempotency keys for side-effecting tools such as deploy, migration, write_code, and external_api. Without an idempotency key, deploy is denied in the test.

## Q10. What is still not production-grade?

Local files replace enterprise services. To productionize, connect the same contracts to IdP, WORM storage, hosted dashboard, live provider APIs, and real deployment rollback hooks.

## Q11. How should we score it?

Evidence-based hackathon score:

- Level 4: achieved.
- Level 5: demonstrated locally.
- Overall score: around 88.7/100.

Production-strict score:

- Level 4: strong.
- Level 5: ready for enterprise integration, not fully production-hosted.