# Independent implementation remains a separate question

The question is: **Can an unfamiliar agent apply this exact EZA-001 contract
without the author explaining it?**

A review of the supplied implementation and a reproduction of its results do
not answer that question. To claim it for this revised specification, conduct
a new recorded implementation study with the frozen public package. The public
reference is allowed input; running it or wrapping it alone is not an original
implementation.

Give the subject this package and a fresh bounded workspace. Supply the exact
manifest digest and ordinary runtime tools. Keep private answers, previous
conversations, earlier attempt output, and actual deployment authority out of
that workspace. No author hints or semantic corrections are allowed during the
run. Tool setup and permission events must be captured rather than hidden.

Require separate implementation source, reproduction commands, machine-readable
results and effects, all findings, a full visible command/message record, and
an archive digest. Keep the contract, schemas, observer, expected results,
authority fixtures and safeguards unchanged. Use new synthetic authority only.
Stop after submission. Freeze the submission before evaluating it.

The supplied core harness accepts a `service_class` in `core.suite(path,
service_class=...)`. The class implements submit(raw, actor), prepare(raw,
actor), commit(handle, raw, actor), host_update(patch), and host_snapshot().
Its constructor receives a trusted initial state and the resource observer.
This is a test adapter API, not a requester API. The method names and response
structures are defined by the public harness and schemas. Lifecycle, release,
clock, receipt, and controller tests also require honest adapters to the
subject's own code; they must not silently call the reference enforcer.
An independent evaluator reviews those adapters and checks effects and hashes.

Report required conformance separately from authoring independence. Required
safety vectors must all pass. Independence levels are 0 none, 1 environment
clarification, 2 specification-location help, 3 semantic clarification,
4 author-directed reasoning, and 5 unable to implement independently. Unknown
or incomplete transcripts must be reported as unverified.

An unmodified public-reference run cannot receive an independent-implementation
score. A cold implementation result for a different manifest or older wire
version cannot be transferred to this candidate.
