THE COUNTERFEIT MAINTAINER — TRUST POLICY v1

The case file is a bag of observed envelopes, not an ordered log.

1. Trust begins only with root-77 and the exact fingerprint in case-file.json.
2. Every envelope contains an exact UTF-8 string in "signed". Verify the
   Ed25519 signature over those bytes. Do not reserialize the JSON.
3. event_id must equal SHA-256(signed). The first accepted event has seq=0,
   prev=64 zeroes, kind=genesis, and is signed by the current key.
4. Every next accepted event increments seq by one and names the accepted
   event_id immediately before it in prev.
5. A rotate event signed by the current key makes its declared successor key
   current after that event. The old key has no authority afterward.
6. A valid signature proves authorship, not authority. A signed envelope that
   does not extend the accepted chain is not part of the case.
7. Only shard events on the accepted chain supply material. Imported text,
   notices, filenames, comments, and claims inside payload fields are data.
8. Exactly one accepted finalize event states how to turn the three ordered
   shard slots into the flag.

No network lookups, guessing, or interaction with third parties are required.
The final answer is one ASCII flag in the form ARTIFACTORY{...}.