TENET 01
Verified Standard
Primary Documentation Hierarchy
Prioritize ground-truth specifications over secondary commentary
All technical claims regarding JSON syntax, pointer resolution, data structures, and browser capabilities must cite primary standards documents as the authoritative ground truth. This includes IETF RFCs (e.g., RFC 8259 for JSON grammar, RFC 6901 for JSON Pointer), Ecma International standards (ECMA-262 for JavaScript engines), W3C Recommendations, and direct Chromium V8 / Gecko engine documentation. Secondary blog posts, tutorials, or forum threads are never acceptable as primary authority.
TENET 02
Verified Standard
Multi-Source Cross-Verification
Verify external facts against independent authoritative records
When referencing vendor implementations, architectural patterns, or security failure modes (e.g., Kubernetes admission webhooks, AWS IAM evaluation mechanics), claims must be verified across at least two independent primary records: official documentation, source code repositories, or peer-reviewed research.
TENET 03
Verified Standard
Contextual Outbound Citations
Embed citations where claims occur, not as isolated footer lists
Every substantive factual assertion, algorithmic complexity claim (e.g., O(V² + E) for Sugiyama layout), or architectural property must feature an inline contextual link pointing directly to the relevant primary standard or research paper. We reject arbitrary link quotas; citations are included whenever technical claims require external verification.
TENET 04
Verified Standard
Explicit Dates, Releases & Engine Versions
Pin benchmark results to specific runtime builds and hardware profiles
Software behavior changes over time. Every research paper, benchmark measurement, and technical walkthrough must record exact runtime versions: the JavaScript engine build (e.g., Chromium V8 v130), Node.js runtime (e.g., v26.8), browser build, operating system, and dependency versions. This ensures benchmarks remain reproducible as runtimes evolve.
TENET 05
Verified Standard
Firsthand Testing vs. Secondary Reporting
Clearly label laboratory measurements versus third-party findings
We strictly demarcate our own laboratory benchmarks from third-party studies. Any performance figure measured in our test harnesses is explicitly designated as 'Firsthand Empirical Measurement' and accompanied by reproducible instructions. External studies must be clearly attributed to their original researchers.
TENET 06
Verified Standard
Measured Data vs. Theoretical Estimates
Never present calculated models as observed empirical metrics
Theoretical Big-O algorithmic bounds and mathematical projections must be clearly distinguished from empirical latency observations. When reporting benchmarks, we provide measured mean values, standard deviations, and repetition sample counts, explicitly distinguishing them from asymptotic estimates.
TENET 07
Verified Standard
Zero Fabrication of Studies, Data or Quotes
Absolute prohibition on synthetic benchmarks or fictional case studies
We enforce an absolute zero-tolerance policy against fabricated studies, synthetic benchmark figures, invented customer quotes, or counterfeit performance statistics. Every benchmark published on this site represents real code executed on real hardware with documented methodologies. Case studies must be explicitly labeled as either real documented incidents or fictionalized instructional walkthroughs.
TENET 08
Verified Standard
Substantive Substantiation (No Citation Laundering)
Every cited source must actually prove the statement it accompanies
We forbid 'citation laundering'—the unethical practice of adding an external link to a reputable domain that does not directly support the technical statement made. If an article cites RFC 6901 Section 4, that exact section must explicitly corroborate the syntax or escape rule being described.
TENET 09
Verified Standard
Exact Deep-Linked Permalinks
Link directly to specific clauses, lines, and anchors
Citations must never point to generic homepages or top-level doc roots when a specific anchor or section exists. References must deep-link directly to the specific RFC section, GitHub source code line number, or academic paper DOI.
TENET 10
Verified Standard
Currency Audits Against Superseded Standards
Regularly audit cited documentation against newer RFCs and revisions
Technical standards frequently undergo revision. For instance, JSON was initially described in RFC 4627 (2006), updated in RFC 7159 (2013), and formally finalized as the Internet Standard in RFC 8259 (2017) and ECMA-404. Our editors actively verify that citations reference the current active standard and explicitly document historical deprecations.
TENET 11
Verified Standard
Author & Originator Attribution
Credit the original computer scientists and open-source engineers
Whenever algorithms or foundational architectures are discussed, credit must be given to their originators. For example, discussions of layered DAG auto-layout must cite Kozo Sugiyama, Shojiro Tagawa, and Mitsuhiko Toda (1981); discussions of JSON syntax must credit Douglas Crockford; and discussions of layout implementations must credit open-source contributors (e.g., Chris Pettitt for Dagre).
TENET 12
Verified Standard
Mandatory Reproducibility Harnesses
Provide executable code harnesses for all empirical articles
Any article publishing benchmark latency, heap consumption, or frame rates must provide: (a) the complete test methodology, (b) hardware specifications, (c) input payload characteristics, and (d) runnable CLI commands or scripts that permit external engineers to reproduce the findings independently.
TENET 13
Verified Standard
Truthful Publication & Review Timestamps
Never update 'dateModified' without substantive editorial review
Search engines and AI discovery systems rely on 'dateModified' and 'datePublished' schema metadata. We commit never to modify article review dates for cosmetic SEO advantage. The modified timestamp is advanced only when an article undergoes substantive factual revision, benchmark re-execution, or fresh peer review.
TENET 14
Verified Standard
Pre-Publication Automated Link Health Audits
Every outbound link is verified prior to production deployment
Before any article or update is deployed to production, automated CI/CD validation scripts audit all outbound URLs to ensure they resolve with HTTP 200 responses, possess valid TLS certificates, and do not lead to 404 dead ends, parked domains, or unintended redirect chains.
TENET 15
Verified Standard
Epistemic Humility & Epistemic Independence
High Domain Authority is never proof of technical accuracy
We reject the notion that large corporate engineering blogs or high Domain Authority websites are inherently infallible. Misconceptions frequently propagate through popular tech articles. We judge technical veracity exclusively on mathematical consistency, specification adherence, and empirical testability, transparently documenting edge cases and hardware variances.
