# August Hackathon review-response note

Date: 2026-08-24

This note responds to the initial review feedback for `EvoWitness`.

## 1. Core commit author and repository owner

The submitted repository is owned by `CJR-ai-nb` and the Mooncakes package namespace is `CJR-ai-nb/evowitness`.

The first submitted repository displayed inconsistent Git author metadata from the preparation workflow, which made the single-participant ownership unclear. This was not acceptable for review. The resubmission corrects Git author configuration and documents the single-participant relationship in [`docs/AUTHORSHIP.md`](AUTHORSHIP.md).

Conservative action taken:

- ensure repository owner, Git author, Mooncakes namespace, README and application materials consistently name `CJR-ai-nb`;
- state that AI assistance was used only as allowed tooling, not as another human participant;
- keep project scope, license and source provenance explicit for review.

## 2. Functional overlap with moon-data-contract

The first submission used broad wording such as "data-contract evolution analyzer", which overlaps with `lyjttio/moon-data-contract`.

The 2026-08-24 re-check shows `moon-data-contract` already covers contract modeling, runtime validation, schema evolution audit, registry/generation, governance, migration/rollback planning, policy gates and Markdown/JSON/JUnit/HTML evidence export.

Conservative action taken:

- package metadata now describes EvoWitness as a "minimal compatibility counterexample witness generator";
- README and proposal now state that EvoWitness is not a schema registry, data-contract governance platform, release gate, JUnit/HTML governance reporter, migration execution tool or external ticket automation product;
- `docs/UNIQUENESS.md` and `docs/RESEARCH.md` now explicitly document the relation to `moon-data-contract`;
- witness-local validation/policy/checklist helpers are described as secondary support for generated witnesses, not as independent governance features.

## 3. Final narrowed boundary

EvoWitness has one acceptance-facing boundary:

> Given two small Evo Contract snippets, determine whether their accepted JSON value sets differ and emit a minimal source-valid/target-invalid payload as replayable evidence.

This is different from managing a data-contract lifecycle. The project focuses on constructive counterexamples, witness re-verification and replay-friendly evidence packs.

## 4. Verification commands

The repository is expected to pass:

```bash
moon fmt --check
moon check --deny-warn
moon build
moon test --deny-warn
moon run examples/checkout
moon run cmd/evowitness -- demo json
moon publish --dry-run
```

Effective production MoonBit source scale after excluding tests, generated interfaces, comments and blank lines is about 4,011 lines.