Skip to content

NEPALI_DATE_CONFORMANCE_INDEX.md

Latest commit

 

History

History
114 lines (88 loc) · 8.52 KB

NEPALI_DATE_CONFORMANCE_INDEX.md

File metadata and controls

114 lines (88 loc) · 8.52 KB
Raw

Nepali Date Conformance Index

Purpose

This index tracks public Nepali date and time failure classes that Project Parva uses for conformance testing, benchmark design, and review planning.

The goal is practical: preserve small, reproducible public cases around BS/AD conversion, month lengths, invalid dates, unsupported ranges, source drift, future-date uncertainty, and workflow risk.

What This Index Is

  • A public evidence map for Nepali date/time regression classes.
  • A source for reproducible conformance fixtures.
  • A way to track failure classes across Nepali date libraries and Nepal-facing software.
  • A way to distinguish verified cases, reported cases, partial reports, and narrative workflow evidence.

What This Index Is Not

  • Not a recognized public calendar authority for Nepal.
  • Not a claim that listed projects are globally broken.
  • Not proof of production impact unless the linked public source explicitly documents that impact.
  • Not a replacement for official Panchanga, government publication, or institution-specific authority.
  • Not a shame list.

Evidence Levels

Level Meaning
verified_public_issue Exact public input plus expected and/or actual behavior is available and represented as an executable or directly checkable fixture.
reported_public_issue A public issue exists, but the expected or actual behavior may be partial or bounded.
reported_public_issue_partial A public issue exists, but it lacks enough deterministic detail for executable use.
narrative_evidence Public discussion or workflow pain, not an executable bug fixture.
business_wedge Relevant business workflow evidence, not necessarily a bug.
review_needed Requires manual validation before executable use.

Master Table

ID Source / repo Issue / PR Failure class Evidence level Exact input available? Executable fixture? Upstream status Parva use Safe claim
YARSA-257-258 yarsa/nepal-compliance Issue #257, PR #258 Frontend/backend source drift verified_public_issue Yes Yes PR merged, merge commit c220a9e Source-drift conformance fixture Parva benchmark work contributed a merged standalone calendar consistency guard.
LEAPFROG-70 leapfrogtechnology/nepali-date-picker Issue #70 Month-length mismatch reported_public_issue Partly, via existing local fixture Documented in this suite; executable rows live in the older Leapfrog fixture Open at time of local review Month-length regression cluster Parva tracks the issue as a public regression cluster.
LEAPFROG-13 leapfrogtechnology/nepali-date-picker Issue #13 Conversion/range error verified_public_issue Yes Yes Public issue AD-to-BS range-error fixture Parva tracks the reported input and verifies its own bounded conversion behavior.
LEAPFROG-33-35 leapfrogtechnology/nepali-date-picker Public issue references #33/#35 April 2021 boundary conversion reported_public_issue_partial No No Public issue reports Manual review target These reports are tracked as boundary-conversion candidates.
GO-NEPALI-15 opensource-nepal/go-nepali Issue #15 AD-to-BS month-boundary mismatch verified_public_issue Yes Yes Closed; current checkout appears fixed Historical executable conversion fixture Parva includes AD 2024-06-14 as a month-boundary regression case.
MEDIC-BIKRAM-SAMBAT-26 medic/bikram-sambat Issue #26, PR #27 2081/2082 month-length correction verified_public_issue for exact rows represented as executable cases; review_needed for rows requiring source adjudication Yes Eight correction rows are executable Closed with PR #27 Historical correction-row benchmark Parva executes the public correction rows that match its current source policy and keeps conflicting rows marked for review.
NODE-NEPALI-DATETIME-82 opensource-nepal/node-nepali-datetime Issue #82 Source provenance / source disagreement reported_public_issue Yes, source rows No Public issue marked done in project view Source-comparison benchmark Parva tracks it as evidence that source provenance matters.
NODE-NEPALI-DATETIME-121 opensource-nepal/node-nepali-datetime Issue #121 Future BS uncertainty narrative_evidence No No Public issue Future review-boundary evidence Parva uses it to support review-needed future-date handling.
CHT-CORE-7925 medic/cht-core Issue #7925 Invalid BS date accepted reported_public_issue Yes, bounded form Yes Public issue Invalid date fixture Parva checks that an invalid Kartik 2079 date shape is rejected.
YARSA-252 yarsa/nepal-compliance Issue #252 Payroll date risk business_wedge Partial No Open Manual payroll investigation target Parva tracks it as reported payroll date-risk evidence requiring reproduction.
ODK-PRE-1951 ODK forum / medic/bikram-sambat Public discussion Unsupported lower range reported_public_issue_partial No No Public discussion Range-boundary evidence Parva tracks it as lower-bound range evidence.
SUBESHB1-71 subeshb1/Nepali-Date Public issue reference Unsupported upper range reported_public_issue_partial No No Public issue reference Range-boundary evidence Parva tracks it as upper-range review evidence.
ERPNEXT-31245 frappe/erpnext Issue #31245 Business workflow gap business_wedge No No Public request Workflow evidence Parva tracks it as evidence that BS support matters in business software.
FRAPPE-BOOKS-787 frappe/books Issue #787 Business workflow gap business_wedge No No Public request Workflow evidence Parva tracks it as accounting workflow context.

Upstream Contribution Status

Yarsa nepal-compliance PR #258 was merged with merge commit c220a9e.

Contribution type: standalone benchmark script.

What it checked:

  • Backend CSV Nepali calendar table.
  • Frontend JS Nepali calendar table.
  • Supported range differences as informational.
  • Overlapping month-length differences as failures.
  • BS 2087 Mangsir source drift: backend CSV 29 days, frontend JS 30 days.

This is an upstream benchmark contribution inspired by Parva's conformance work. It is not a dependency relationship, adoption claim, or production-impact claim.

Generated Public Suite Report

The current report is committed at generated artifact: reports/conformance/public-issue-suite-summary.md with machine-readable JSON at generated artifact: reports/conformance/public-issue-suite-summary.json.

Regenerate it with:

py -3.11 tools\conformance_runner\run.py --suite public-nepali-date-issues --write-report reports\conformance\public-issue-suite-summary.json

Safe Claims

  • Project Parva's benchmark work contributed a standalone Nepali calendar source consistency guard to yarsa/nepal-compliance.
  • Project Parva tracks public Nepali date regression cases as conformance fixtures.
  • Project Parva provides a Nepal compliance conformance profile for source-drift, conversion-boundary, invalid-date, future-review, and payroll date-risk checks.
  • Some public issues show recurring failure classes around month lengths, conversion boundaries, invalid dates, unsupported ranges, and future-date uncertainty.

Forbidden Claims

Do not claim:

  • Yarsa changed its product to depend on Project Parva.
  • Parva has recognized public calendar authority for Nepal.
  • Listed projects are globally broken.
  • Parva proves production payroll or invoices are wrong.
  • Future BS dates are guaranteed.