Goal
Approach ENTITY as a new developer and follow START_HERE.md from a fresh clone without relying on prior project knowledge.
This is a documentation/usability audit for ENTITY v3.4.0 — Global Passport & Continuous Provenance. You do not need to change protocol code.
Try to answer
- Can you understand the five core primitives and the Global Passport concept from the linked material?
- Do the quick-start commands work as written?
- Can you find the v3.4 Global Passport schema, sealed clean-room kit, domain packages, tests and engineering-evidence ledger without guessing?
- Can you understand the difference between a core Global Passport and a domain implementation package?
- Is anything described before it is defined?
- Are any links stale, circular or unnecessarily deep?
- Is the difference between BTG-controlled qualification and independent external validation clear?
- Can you identify a useful first contributor task in under 10 minutes?
Completion evidence
Open a PR with narrowly scoped documentation corrections, or comment with a short numbered usability report identifying exact files/lines and the point of confusion.
Please preserve technical precision rather than simplifying away the authority, evidence, truth and compliance boundaries.
Goal
Approach ENTITY as a new developer and follow
START_HERE.mdfrom a fresh clone without relying on prior project knowledge.This is a documentation/usability audit for ENTITY v3.4.0 — Global Passport & Continuous Provenance. You do not need to change protocol code.
Try to answer
Completion evidence
Open a PR with narrowly scoped documentation corrections, or comment with a short numbered usability report identifying exact files/lines and the point of confusion.
Please preserve technical precision rather than simplifying away the authority, evidence, truth and compliance boundaries.