Repository navigation
site: distinguish historical field evidence from current stable verification - #366
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 93b65acca9
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "reporting": [ | ||
| "https://github.com/masarray/ARIEC61850/pull/36" | ||
| ], |
There was a problem hiding this comment.
The new registry maps the profile's reporting: conditional status to PR #36, but the rendered profile describes that same PR only as read-only RCB-option evidence and explicitly states that it does not establish live report delivery (landing/templates/compatibility.html:71, with the same wording on the Indonesian page). This makes machine-readable consumers see service-level reporting evidence that the human-facing evidence boundary disclaims; either link a record demonstrating the conditional reporting workflow or stop mapping this record to reporting.
AGENTS.md reference: AGENTS.md:L153-L153
Useful? React with 👍 / 👎.
| for profile in field_evidence.get("profiles", []): | ||
| if not isinstance(profile, dict): | ||
| continue | ||
| profile_id = str(profile.get("id", "")) | ||
| for marker in (f'data-evidence-trace="{profile_id}"', f'data-service-records="{profile_id}"'): | ||
| if marker not in matrix_text: errors.append(f"{page}: missing rendered profile trace {marker}") |
There was a problem hiding this comment.
The rendered validator now iterates each registry profile but never compares its evidenceDate with that profile's HTML; both templates still hard-code 2026-07 and the summary hard-codes July 2026. Consequently, correcting an evidence month in device-evidence.json passes the new schema checks while publishing the old date, even though the page says the registry contains the same historical dates. Validate the date inside each profile block or render it from the authoritative registry.
AGENTS.md reference: AGENTS.md:L27-L33
Useful? React with 👍 / 👎.
R6.2 — Evidence Freshness & Traceability
Builds on R6.1 proof navigation in #365.
Rollback checkpoint
checkpoint/site-r6.1-proof-surfaces-2026-09-22→42e144bd519788a09ec091fd4d6f72664ed82137.Evidence semantics
device-evidence.jsonto schema v2 with explicit historical evidence provenance.testedArsasVersionandlastRetestnull where no public evidence establishes them.latest.json, not from an inferred backfill.not-testedservice statuses to linked public engineering records and label those PRs as implementation/engineering history, not raw relay captures or physical retest.EN/ID UI
Regression protection
Source, rendered-site and adoption/field-proof validators enforce schema, service-to-link parity, declared unknowns and current stable token rendering. A future registry version/retest change must be reflected visibly rather than silently updating a JSON value.
Scope
8 website/validator files only. No new page or runtime/engine behavior change. No retroactive compatibility claim, conformance claim, or assertion of new physical-relay testing.