[ RESEARCH & ENGINEERING ]
Rules a compiler cannot argue with.
Most coding standards are documents people are asked to follow. Ours are checks that fail the build.
ARCHITECTURE>ENFORCEMENT>VERIFICATION>RELEASE
[ VERIFICATION ENGINEERING ]
The closed taxonomy
A closed taxonomy is a fixed list of what code is allowed to contain. Anything outside the list is a violation. The standard is named Tier-13.
No nulls
Every value has a named state. "Nothing here" is a declared case, never an empty reference.
No Booleans as control flow
Two-way flags hide the third case. States are named and every branch is handled.
No silent defaults
No Elvis operators and no empty-string stand-ins. A missing value is handled where it happens.
No deferred initialization
No lateinit, no by lazy. An object is complete when it exists.
No suppressions
Warnings are fixed, not hidden. Suppression annotations are themselves a violation.
ASCII, 100 columns
Source is plain 7-bit ASCII with a 100-column limit, so every line reads the same everywhere.
[ THREE LAYERS OF ENFORCEMENT ]
Scan, lint, gate
Scanners. 34 PowerShell audit scripts check the repository for taxonomy violations, unwired code, file-index integrity and more.
Lint rules. A custom Android Lint module reports violations live in the editor and in the build.
Architecture gates. 14 tests check the structure of the codebase itself. The gates are held to the same rules as the code they check.
SCOPE>SCAN>VERIFICATION>RESULT
| Architecture gate | Last run |
|---|---|
| architectureSuiteMustSatisfyItsOwnClosedTaxonomy | PASSED |
| daosMustRouteExecutionThroughInjectedDispatcher | PASSED |
| daosMustUseCanonicalDaoSuffix | PASSED |
| databaseScopeMustContainSingleGovernedSqliteEngine | PASSED |
| domainModelsMustRemainFrameworkAndPresentationAgnostic | PASSED |
| entityFilesMustDeclareMatchingDataClass | PASSED |
| lintRulesModuleMustSatisfyItsOwnClosedTaxonomy | PASSED |
| persistenceDataClassesMustUseEntityFilename | PASSED |
| productionArchitectureMustRemainIndependentOfGeneratedPersistence | PASSED |
| productionSourcesMustSatisfyClosedTaxonomyPurity | PASSED |
| repositoriesMustUseCanonicalRepositorySuffix | PASSED |
| serviceScopeMustUseCanonicalServiceOrBinderSuffix | PASSED |
| viewModelsMustInheritCanonicalViewModelBase | PASSED |
| viewModelsMustUseCanonicalViewModelSuffix | PASSED |
Gate names and results read from the test result file dated November 19, 2026.
[ RESEARCH AREAS ]
Where the work goes
Application security
Integrity checks, authentication gates and on-device license verification.
Android platform research
Firmware, recovery environments and system-image analysis.
Digital forensics
Sealed records and reports that show alteration.
Verification engineering
Scanners, lint rules and gates that audit a whole repository.
Deterministic architecture
Named states and exhaustive branches in place of flags and defaults.
Security hardening
Removing network access, backups and screen capture where they are not needed.
[ THIS DISCIPLINE, SHIPPED ]
RxAuditor
The codebase these rules were written for, and the one that has to pass them.