Skip to main content
Reader Edition 1.1 is the English explanation of AccelMars Gateway’s Final Design 1.0. It reorganizes the knowledge in the original 46-document technical reference into a connected guide, with examples, diagrams and plain-language definitions. The source design edition was issued on 13 October 2026. Its recorded implementation evidence is current to 12 October 2026, not to the date on which you open this page.

​
What changed

The reading structure starts with purpose, then architecture, request journeys and the controls that make those journeys safe. Internal document codes, checksum tables and repetitive provenance blocks no longer sit inside the main explanation. Examples are identified as illustrative. Diagrams show responsibilities and permitted conceptual sequences; they are not screenshots of a deployed system or new service definitions. The editorial scope includes all original reader topics. Related or duplicated pages have been combined, while a dedicated timeout explanation has been added from the engineering source. The exact coverage map is retained with the controlled source package.

​
What did not change

The Engineering Design of Record remains the source for technical contracts and accepted decisions. Reader Edition 1.1 does not change retry limits, ownership, output rules, financial requirements or the selected disaster profile. The original source collections and historical failed or partial evidence are preserved. Publication does not execute a provider request, database migration, financial operation or independent engineering test. The source’s own authority distinctions also remain: a Gateway-scoped decision is not automatically a newly ratified company-wide rule.

​
Three dates tell three different stories

A design decision has an adoption date and scope. Code has a source and dependency version. A test or deployment has an execution date, environment and result. A new document publication does not merge those dates. In particular, the local streaming and caller experiments cannot be presented as one tested production release just because both are described in the same guide. Use Implementation status for the dated evidence and known limits.

​
How explanation is kept accurate

The editorial source package records which engineering and reference sources support each topic. It distinguishes source-derived facts, explanatory synthesis and synthetic examples. Where an older explanatory sentence conflicts with a more specific final handoff, the conflict is recorded rather than silently turned into a new rule. A genuine unresolved design contradiction requires its existing owner; it is not the editor’s opportunity to choose whichever story reads better. Exact source identifiers remain in the internal audit material, not in the middle of a reader’s first explanation. Removing that visual clutter does not remove traceability.

​
One source for future publications

The English reader source is maintained as a controlled edition on Google Drive. Mintlify is its reading and publication surface, not an independently evolving second design. Future Vietnamese or other-language editions should be derived from that source, adapting presentation while preserving the technical meaning. No translation is claimed to exist merely because the pipeline allows one. Reader feedback can improve explanations and navigation. A new implementation receipt updates the dated evidence it actually supports. A changed technical rule requires a controlled design amendment, not an unmarked wording change. Return to Gateway, explained or choose a reading path.