← Issues & Errata Registry / ISS-CAL-2026-002
Edition: English · Tiếng Việt · 繁體中文
ISSUES & ERRATA · ISS-CAL-2026-002

Saigon historical calendar conversion and pSEO chronology mismatch

Calendar basis, civil time, reproducible API cases and source-qualified Saigon chronology.

Target Paper QP-CAL-001
Review Status ● Resolved & Closed
Open Date 2026-11-17
Methodology Claim → Cross-Reference → Evidence

Status at opening: OPEN — opened 17 November 2026. Scope: QP-CAL-001, Calendar conversion API and /time/saigon/history/.

1. Reproduction

POST /api/calendar/solar-to-lunar with {day:29,month:1,year:1968,timezone:"VN",city:"saigon"} reports historical offset 8 but lunar 1/1/1968. The same core function with offset 8 returns 30/12/1967. The reverse API returns 29 January for Saigon New Year instead of 30 January.

2. Findings

CAL-H01 (High): both conversion directions use fixed UTC+7 despite a selected historical locality. CAL-H02 (High): the North's pre-1968 calendar reference offset is conflated with civil clock time. CAL-H03 (High): separate pSEO prose omits 1911, 1947 and 1955 transitions and asserts unsupported April 1945 / May 1975 chronology. CAL-H04 (Medium): 270 divergent dates describe a fixed +7/+8 computation through 12 June 1975, not independently verified calendars actually used by both populations.

3. Acceptance criteria

Separate civil time from calendar basis; expose modern and historical modes; resolve each astronomical new moon in its own era in both directions. Preserve numeric-offset core calls. Cover the 1968 New Year and the 1975 boundary in integration tests. Rewrite chronology, source qualifications and publication metadata; do not replace longitude-based LMT merely to match tzdb.

4. Evidence limits

IANA Asia is comparative evidence, not final legal authority. Vietnam's archival authority discusses the decree of 29 March 1945 and Decision 121-CP effective 1 January 1968. A transcription of Hanoi Moi, 15 June 1975 supports the 13 June date. The original newspaper image and precise clock time have not been independently checked. March 1945 chronology and complete printed-calendar reconstruction remain outside certified coverage.

5. Resolution and deployment verification — 17 November 2026

Current status: resolved, tested and verified in production; software/content findings CAL-H01–CAL-H04 are closed. The historical research limitations in section 4 remain explicit.

Civil clock metadata and calendar reference are now separate. An explicit Vietnamese locality selects historical reconstruction by default; no locality retains the modern fixed-meridian default. calendarMode: "modern" is an explicit override. Both conversion directions use the same basis and resolve each new moon in its own era. Hanoi before 1968 can report civil +7 and calendar +8 without conflating the two.

Saigon 29 January 1968 now maps to lunar 30/12/1967; inverse New Year conversion returns 30 January. The 1 April 1947 regression ensures a clock change does not retroactively move the preceding new moon. The pSEO chronology, sources, revision metadata, home introduction and locality day route were corrected. Claims about a May 1 military order, SEATO motives and 270 empirically established historical dates were withdrawn. An existing QPS build typo (parent_id versus parent.id) was corrected in the same index builder.

Staging passed 41 historical/API checks, 59,170 two-locality roundtrips over 1900–1980, the complete Calendar npm test command (including 834 boundary cases and 113 core checks), 4 pSEO tests, 8 QPS tests, TypeScript compilation and QPS index generation. Fifteen additional public HTTPS check groups passed after deployment. These are bounded verification results, not certification of every historical calendar. Per-file backup and rollback manifests were retained; no database, Nginx or operating-system timezone change was made.

Markdown