Public Publication and Corrections Policy
BTG public-documentation policy
Publication scope: whitepapers, system explanations, participation guides, adoption research, general rights frameworks, approved public specifications, risk notices, regulator-status statements and appropriately redacted audit summaries.
Not in scope: Exchange source code, matching or settlement internals, private FarmNode algorithms, unpublished vulnerabilities, secrets, cryptographic keys, private legal agreements, raw user activity, personal records, financial records or internal infrastructure credentials.
Evidence labels
Every empirical capability claim should state whether it is proposed, implemented but unqualified, internally tested, independently tested, commercially demonstrated, or legally authorized for the relevant use. None of these labels implies a higher one. An internal signature is evidence of an attestation, not independent proof of truth.
Publication release gate
Before posting: (1) owner and copyright review, (2) privacy and security redaction, (3) technical fact-check against dated outputs, (4) legal and securities-disclosure review where relevant, (5) source citations and link tests, (6) written release approval, (7) public version and correction record. Internal draft dossiers are not automatically releasable.
Corrections and change log
Keep the prior version available through Git history; put a clear date and change summary in updated documents. Correct material errors promptly and visibly. Do not backdate approvals or overwrite recorded outcomes. For significant errors affecting financial or rights statements, suspend the disputed public statement until verification completes.
Repository segregation
Public GitHub Pages hosts only static content, manually approved public evidence and redacted/non-identifying records. It must never have direct credentials to the private Exchange or privileged access to participant vaults. Issuer listings, ticker specifications, market feeds and ledgers are engineering-owned deliverables outside this documentation programme.
Document ownership
Copyright © 2026 Blackmore Technology Group Limited. All rights reserved unless a particular document explicitly grants a different licence. Public visibility does not make the Exchange, its documentation or its algorithms open source.