[START HERE] 15-minute ENTITY v3.4.3 first-run audit — find the first broken, stale or ambiguous step #80

Goal

Give a new developer a 15-minute bounded way to contribute useful external evidence without first understanding all of ENTITY.

ENTITY v3.4.3 is the current supported runtime. We want an unrelated developer to follow the public path from discovery → clone → first verification and report the first thing that is broken, stale, ambiguous, platform-specific or unnecessarily difficult.

Pick your platform

If you prefer a platform-specific task, use one of these child issues:

• [GOOD FIRST ISSUE] Reproduce ENTITY v3.4.3 first-run path on Windows 11 #84 — Windows 11 first-run reproduction
• [GOOD FIRST ISSUE] Reproduce ENTITY v3.4.3 first-run path on Ubuntu/Linux #85 — Ubuntu/Linux first-run reproduction
• [GOOD FIRST ISSUE] Reproduce ENTITY v3.4.3 first-run path on macOS #86 — macOS first-run reproduction

All three use the same claim boundary: onboarding/reproducibility evidence only. A PASS on one platform does not imply another platform passes.

Time box

15 minutes. Stop at the first reproducible friction point.

A negative result is useful. You do not need to fix anything.

Start

1. Read one technical entry point:
   • Sovereign digital authority: https://blackmore-technology-group.github.io/ENTITY-DOCS/discover/sovereign-digital-authority.html
   • Data rights / provenance: https://blackmore-technology-group.github.io/ENTITY-DOCS/discover/data-rights-provenance.html
   • Protocol conformance testing: https://blackmore-technology-group.github.io/ENTITY-DOCS/discover/protocol-conformance-testing.html
   • Clean-room interoperability: https://blackmore-technology-group.github.io/ENTITY-DOCS/discover/clean-room-interoperability.html
2. Clone the current release:

git clone https://github.com/blackmore-technology-group/ENTITY.git
cd ENTITY
git checkout v3.4.3

3. Follow the README quick-start path until either:
   • the stated result works, or
   • you reach the first reproducible friction point.

Report exactly this

OS / version:
Runtime / version:
Shell:
Step attempted:
Expected result:
Actual result:
Exact error or ambiguity:
Reproducible? yes/no
Suggested wording or fix (optional):

Screenshots or logs are welcome, but redact credentials, private keys, personal data and operational sovereignty state.

What counts as a useful finding

• a command does not work as written;
• a dependency or version is missing;
• Windows, Linux or macOS behaves differently;
• the release/version boundary is unclear;
• a link is stale;
• a protocol term is ambiguous to a first-time reader;
• a test result cannot be reproduced;
• the documentation assumes knowledge it did not provide;
• a security or authority boundary appears contradictory.

Claim boundary

Passing this audit is only onboarding/reproducibility evidence. It is not a security audit, legal certification or independent implementation of ENTITY.

If the first-run path works cleanly, report that too with your environment. That is useful external evidence.

For deeper work after this task, use the umbrella external verification challenge: #55.