This directory collects public technical writing that explains ENTITY's architecture, threat boundaries and engineering decisions in a form that can be reviewed independently of marketing material.
These papers are informative unless a document explicitly states that it is normative. Normative requirements remain controlled by the applicable protocol, schema, manifest, governance and requirements documents.
A technical paper should:
- identify whether it is normative or informative;
- identify the release/version it describes;
- distinguish implemented behavior from proposed behavior;
- distinguish BTG-controlled evidence from independent external evidence;
- state important limitations and unresolved questions;
- link to reproducible public material where possible;
- avoid silently redefining frozen protocol semantics.
Architecture decisions are maintained separately under docs/architecture. ADRs record decisions and their rationale; technical papers explain broader concepts, boundaries or analysis.
If a paper becomes outdated, the preferred approach is to mark it superseded or publish a revision rather than silently changing historical claims in a way that makes the original evidence impossible to reconstruct.